diff --git a/.github/actions-scripts/msft-create-translation-batch-pr.js b/.github/actions-scripts/msft-create-translation-batch-pr.js new file mode 100755 index 0000000000..1ea57c342d --- /dev/null +++ b/.github/actions-scripts/msft-create-translation-batch-pr.js @@ -0,0 +1,142 @@ +#!/usr/bin/env node + +import fs from 'fs' +import github from '@actions/github' + +const OPTIONS = Object.fromEntries( + ['BASE', 'BODY_FILE', 'GITHUB_TOKEN', 'HEAD', 'LANGUAGE', 'TITLE', 'GITHUB_REPOSITORY'].map( + (envVarName) => { + const envVarValue = process.env[envVarName] + if (!envVarValue) { + throw new Error(`You must supply a ${envVarName} environment variable`) + } + return [envVarName, envVarValue] + } + ) +) + +if (!process.env.GITHUB_REPOSITORY) { + throw new Error('GITHUB_REPOSITORY environment variable not set') +} + +const RETRY_STATUSES = [ + 422, // Retry the operation if the PR already exists + 502, // Retry the operation if the API responds with a `502 Bad Gateway` error. +] +const RETRY_ATTEMPTS = 3 +const { + // One of the default environment variables provided by Actions. + GITHUB_REPOSITORY, + + // These are passed in from the step in the workflow file. + TITLE, + BASE, + HEAD, + LANGUAGE, + BODY_FILE, + GITHUB_TOKEN, +} = OPTIONS +const [OWNER, REPO] = GITHUB_REPOSITORY.split('/') + +const octokit = github.getOctokit(GITHUB_TOKEN) + +/** + * @param {object} config Configuration options for finding the PR. + * @returns {Promise} The PR number. + */ +async function findPullRequestNumber(config) { + // Get a list of PRs and see if one already exists. + const { data: listOfPullRequests } = await octokit.rest.pulls.list({ + owner: config.owner, + repo: config.repo, + head: `${config.owner}:${config.head}`, + }) + + return listOfPullRequests[0]?.number +} + +/** + * When this file was first created, we only introduced support for creating a pull request for some translation batch. + * However, some of our first workflow runs failed during the pull request creation due to a timeout error. + * There have been cases where, despite the timeout error, the pull request gets created _anyway_. + * To accommodate this reality, we created this function to look for an existing pull request before a new one is created. + * Although the "find" check is redundant in the first "cycle", it's designed this way to recursively call the function again via its retry mechanism should that be necessary. + * + * @param {object} config Configuration options for creating the pull request. + * @returns {Promise} The PR number. + */ +async function findOrCreatePullRequest(config) { + const found = await findPullRequestNumber(config) + + if (found) { + return found + } + + try { + const { data: pullRequest } = await octokit.rest.pulls.create({ + owner: config.owner, + repo: config.repo, + base: config.base, + head: config.head, + title: config.title, + body: config.body, + draft: false, + }) + + return pullRequest.number + } catch (error) { + if (!error.response || !config.retryCount) { + throw error + } + + if (!config.retryStatuses.includes(error.response.status)) { + throw error + } + + console.error(`Error creating pull request: ${error.message}`) + console.warn(`Retrying in 5 seconds...`) + await new Promise((resolve) => setTimeout(resolve, 5000)) + + config.retryCount -= 1 + + return findOrCreatePullRequest(config) + } +} + +/** + * @param {object} config Configuration options for labeling the PR + * @returns {Promise} + */ +// async function labelPullRequest(config) { +// await octokit.rest.issues.update({ +// owner: config.owner, +// repo: config.repo, +// issue_number: config.issue_number, +// labels: config.labels, +// }) +// } + +async function main() { + const options = { + title: TITLE, + base: BASE, + head: HEAD, + body: fs.readFileSync(BODY_FILE, 'utf8'), + labels: ['translation-batch', `translation-batch-${LANGUAGE}`], + owner: OWNER, + repo: REPO, + retryStatuses: RETRY_STATUSES, + retryCount: RETRY_ATTEMPTS, + } + + options.issue_number = await findOrCreatePullRequest(options) + const pr = `${GITHUB_REPOSITORY}#${options.issue_number}` + console.log(`Created PR ${pr}`) + + // metadata parameters aren't currently available in `github.rest.pulls.create`, + // but they are in `github.rest.issues.update`. + // await labelPullRequest(options) + // console.log(`Updated ${pr} with these labels: ${options.labels.join(', ')}`) +} + +main() diff --git a/.github/workflows/autoupdate-branch.yml b/.github/workflows/autoupdate-branch.yml index 281ad5363c..1a6c0baa5a 100644 --- a/.github/workflows/autoupdate-branch.yml +++ b/.github/workflows/autoupdate-branch.yml @@ -45,7 +45,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/azure-preview-env-deploy.yml b/.github/workflows/azure-preview-env-deploy.yml index 85b5595b2d..72d580c009 100644 --- a/.github/workflows/azure-preview-env-deploy.yml +++ b/.github/workflows/azure-preview-env-deploy.yml @@ -210,6 +210,3 @@ jobs: dockerRegistryUrl="${{ secrets.NONPROD_REGISTRY_SERVER }}" dockerRegistryUsername="${{ env.NONPROD_REGISTRY_USERNAME }}" dockerRegistryPassword="${{ secrets.NONPROD_REGISTRY_PASSWORD }}" - # 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-prod-build-deploy.yml b/.github/workflows/azure-prod-build-deploy.yml index 2ee8931ccf..e43529dce6 100644 --- a/.github/workflows/azure-prod-build-deploy.yml +++ b/.github/workflows/azure-prod-build-deploy.yml @@ -62,7 +62,7 @@ jobs: - name: Setup node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Clone docs-early-access diff --git a/.github/workflows/azure-staging-build-deploy.yml b/.github/workflows/azure-staging-build-deploy.yml new file mode 100644 index 0000000000..47059ba334 --- /dev/null +++ b/.github/workflows/azure-staging-build-deploy.yml @@ -0,0 +1,31 @@ +name: Azure Staging - Build and Deploy + +# **What it does**: Builds and deploys a branch/PR to staging +# **Why we have it**: To enable us to deploy a branch/PR to staging whenever necessary +# **Who does it impact**: All contributors. + +on: + 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 + deployments: write + +jobs: + azure-staging-build-and-deploy: + if: ${{ github.repository == 'github/docs-internal' }} + runs-on: ubuntu-latest + + steps: + - name: 'No-op' + run: | + echo "No-op" diff --git a/.github/workflows/browser-test.yml b/.github/workflows/browser-test.yml index 60b728d8e4..8e052579b7 100644 --- a/.github/workflows/browser-test.yml +++ b/.github/workflows/browser-test.yml @@ -42,7 +42,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/check-all-english-links.yml b/.github/workflows/check-all-english-links.yml index cc163d320e..ffb3b2a7bd 100644 --- a/.github/workflows/check-all-english-links.yml +++ b/.github/workflows/check-all-english-links.yml @@ -30,17 +30,34 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - - name: npm ci + + - name: Install dependencies run: npm ci + - name: Cache nextjs build uses: actions/cache@48af2dc4a9e8278b89d7fa154b955c30c6aaab09 with: path: .next/cache key: ${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }} - - name: npm run build + + - name: Build server run: npm run build + + - name: Start server in the background + env: + NODE_ENV: production + PORT: 4000 + DISABLE_OVERLOAD_PROTECTION: true + DISABLE_RENDER_CACHING: true + # We don't want or need the changelog entries in this context. + CHANGELOG_DISABLED: true + run: | + node server.mjs & + sleep 5 + curl --retry-connrefused --retry 3 -I http://localhost:4000/ + - name: Run script run: | script/check-english-links.js > broken_links.md @@ -53,6 +70,16 @@ jobs: # # https://docs.github.com/actions/reference/context-and-expression-syntax-for-github-actions#job-status-check-functions + - if: ${{ failure() }} + name: Debug broken_links.md + run: | + ls -lh broken_links.md + wc -l broken_links.md + - uses: actions/upload-artifact@6673cd052c4cd6fcf4b4e6e60ea986c889389535 + if: ${{ failure() }} + with: + name: broken_links + path: ./broken_links.md - if: ${{ failure() }} name: Get title for issue id: check @@ -63,7 +90,6 @@ jobs: uses: peter-evans/create-issue-from-file@b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e with: token: ${{ env.GITHUB_TOKEN }} - title: ${{ steps.check.outputs.title }} content-filepath: ./broken_links.md repository: ${{ env.REPORT_REPOSITORY }} diff --git a/.github/workflows/check-broken-links-github-github.yml b/.github/workflows/check-broken-links-github-github.yml index 020039f105..a0561737f7 100644 --- a/.github/workflows/check-broken-links-github-github.yml +++ b/.github/workflows/check-broken-links-github-github.yml @@ -44,7 +44,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install Node.js dependencies @@ -57,6 +57,8 @@ jobs: env: NODE_ENV: production PORT: 4000 + DISABLE_OVERLOAD_PROTECTION: true + DISABLE_RENDER_CACHING: true run: | node server.mjs & diff --git a/.github/workflows/code-lint.yml b/.github/workflows/code-lint.yml index 1aa9279a2a..2215aee697 100644 --- a/.github/workflows/code-lint.yml +++ b/.github/workflows/code-lint.yml @@ -39,7 +39,7 @@ jobs: - name: Setup node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/content-changes-table-comment.yml b/.github/workflows/content-changes-table-comment.yml index 08ded81b73..01ec4d1fcf 100644 --- a/.github/workflows/content-changes-table-comment.yml +++ b/.github/workflows/content-changes-table-comment.yml @@ -59,7 +59,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install temporary dependencies diff --git a/.github/workflows/create-translation-batch-pr.yml b/.github/workflows/create-translation-batch-pr.yml index a836bca6ad..7aa85eed4f 100644 --- a/.github/workflows/create-translation-batch-pr.yml +++ b/.github/workflows/create-translation-batch-pr.yml @@ -118,7 +118,7 @@ jobs: - name: 'Setup node' uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x - run: npm ci diff --git a/.github/workflows/crowdin-cleanup.yml b/.github/workflows/crowdin-cleanup.yml index 377c9e4bac..2912c1cdff 100644 --- a/.github/workflows/crowdin-cleanup.yml +++ b/.github/workflows/crowdin-cleanup.yml @@ -31,7 +31,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/docs-review-collect.yml b/.github/workflows/docs-review-collect.yml index 821a86108c..cb8883b79b 100644 --- a/.github/workflows/docs-review-collect.yml +++ b/.github/workflows/docs-review-collect.yml @@ -25,7 +25,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/enterprise-dates.yml b/.github/workflows/enterprise-dates.yml index b970978fa2..330a0ae1ef 100644 --- a/.github/workflows/enterprise-dates.yml +++ b/.github/workflows/enterprise-dates.yml @@ -41,7 +41,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install Node.js dependencies diff --git a/.github/workflows/enterprise-release-sync-search-index.yml b/.github/workflows/enterprise-release-sync-search-index.yml index e053c74f1c..5b7cd035dc 100644 --- a/.github/workflows/enterprise-release-sync-search-index.yml +++ b/.github/workflows/enterprise-release-sync-search-index.yml @@ -52,7 +52,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/link-check-all.yml b/.github/workflows/link-check-all.yml index 23817594c8..8e273bede3 100644 --- a/.github/workflows/link-check-all.yml +++ b/.github/workflows/link-check-all.yml @@ -32,7 +32,7 @@ jobs: - name: Setup node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install diff --git a/.github/workflows/msft-create-translation-batch-pr.yml b/.github/workflows/msft-create-translation-batch-pr.yml new file mode 100644 index 0000000000..a50bf0f8f7 --- /dev/null +++ b/.github/workflows/msft-create-translation-batch-pr.yml @@ -0,0 +1,204 @@ +name: Create translation Batch Pull Request + +# **What it does**: +# - Creates one pull request per language after running a series of automated checks, +# removing translations that are broken in any known way +# **Why we have it**: +# - To deploy translations +# **Who does it impact**: It automates what would otherwise be manual work, +# helping docs engineering focus on higher value work + +on: + workflow_dispatch: + # TODO: bring schedule back in + # schedule: + # - cron: '02 17 * * *' # Once a day at 17:02 UTC / 9:02 PST + +permissions: + contents: write + +jobs: + create-translation-batch: + name: Create translation batch + if: github.repository == 'github/docs-internal' + runs-on: ubuntu-latest + # A sync's average run time is ~3.2 hours. + # This sets a maximum execution time of 300 minutes (5 hours) to prevent the workflow from running longer than necessary. + timeout-minutes: 300 + strategy: + fail-fast: false + max-parallel: 1 + matrix: + include: + # TODO: replace language_repos with actual repos once created + # - language: pt + # crowdin_language: pt-BR + # language_dir: translations/pt-BR + # language_repo: github/docs-translations-pt-br + + - language: es + crowdin_language: es-ES + language_dir: translations/es-ES + language_repo: github/docs-localization-test-es-es + + # - language: cn + # crowdin_language: zh-CN + # language_dir: translations/zh-CN + # language_repo: github/docs-translations-zh-cn + + # - language: ja + # crowdin_language: ja + # language_dir: translations/ja-JP + # language_repo: github/docs-translations-ja-jp + + # TODO: replace the branch name + steps: + - name: Set branch name + id: set-branch + run: | + echo "::set-output name=BRANCH_NAME::msft-translation-batch-${{ matrix.language }}-$(date +%Y-%m-%d__%H-%M)" + + - run: git config --global user.name "docubot" + - run: git config --global user.email "67483024+docubot@users.noreply.github.com" + + - name: Checkout the docs-internal repo + uses: actions/checkout@dcd71f646680f2efd8db4afa5ad64fdcba30e748 + with: + fetch-depth: 0 + lfs: true + + - name: Create a branch for the current language + run: git checkout -b ${{ steps.set-branch.outputs.BRANCH_NAME }} + + - name: Remove unwanted git hooks + run: rm .git/hooks/post-checkout + + - name: Remove all language translations + run: | + git rm -rf --quiet ${{ matrix.language_dir }}/content + git rm -rf --quiet ${{ matrix.language_dir }}/data + + - name: Checkout the language-specific repo + uses: actions/checkout@dcd71f646680f2efd8db4afa5ad64fdcba30e748 + with: + repository: ${{ matrix.language_repo }} + token: ${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }} + path: ${{ matrix.language_dir }} + + - name: Remove .git from the language-specific repo + run: rm -rf ${{ matrix.language_dir }}/.git + + # TODO: Rename this step + - name: Commit crowdin sync + run: | + git add ${{ matrix.language_dir }} + git commit -m "Add crowdin translations" || echo "Nothing to commit" + + - name: 'Setup node' + uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 + with: + node-version: 16.15.x + + - run: npm ci + + # step 6 in docs-engineering/crowdin.md + - name: Homogenize frontmatter + run: | + node script/i18n/homogenize-frontmatter.js + git add ${{ matrix.language_dir }} && git commit -m "Run script/i18n/homogenize-frontmatter.js" || echo "Nothing to commit" + + # step 7 in docs-engineering/crowdin.md + - name: Fix translation errors + run: | + node script/i18n/fix-translation-errors.js + git add ${{ matrix.language_dir }} && git commit -m "Run script/i18n/fix-translation-errors.js" || echo "Nothing to commit" + + # step 8a in docs-engineering/crowdin.md + - name: Check parsing + run: | + node script/i18n/lint-translation-files.js --check parsing | tee -a /tmp/batch.log | cat + git add ${{ matrix.language_dir }} && git commit -m "Run script/i18n/lint-translation-files.js --check parsing" || echo "Nothing to commit" + + # step 8b in docs-engineering/crowdin.md + - name: Check rendering + run: | + node script/i18n/lint-translation-files.js --check rendering | tee -a /tmp/batch.log | cat + git add ${{ matrix.language_dir }} && git commit -m "Run script/i18n/lint-translation-files.js --check rendering" || echo "Nothing to commit" + + - name: Reset files with broken liquid tags + run: | + node script/i18n/reset-files-with-broken-liquid-tags.js --language=${{ matrix.language }} | tee -a /tmp/batch.log | cat + git add ${{ matrix.language_dir }} && git commit -m "run script/i18n/reset-files-with-broken-liquid-tags.js --language=${{ matrix.language }}" || echo "Nothing to commit" + + # step 5 in docs-engineering/crowdin.md using script from docs-internal#22709 + - name: Reset known broken files + run: | + node script/i18n/reset-known-broken-translation-files.js | tee -a /tmp/batch.log | cat + git add ${{ matrix.language_dir }} && git commit -m "run script/i18n/reset-known-broken-translation-files.js" || echo "Nothing to commit" + env: + GITHUB_TOKEN: ${{ secrets.DOCUBOT_REPO_PAT }} + + - name: Check in CSV report + run: | + mkdir -p translations/log + csvFile=translations/log/${{ matrix.language }}-resets.csv + script/i18n/report-reset-files.js --report-type=csv --language=${{ matrix.language }} --log-file=/tmp/batch.log > $csvFile + git add -f $csvFile && git commit -m "Check in ${{ matrix.language }} CSV report" || echo "Nothing to commit" + + - name: Write the reported files that were reset to /tmp/pr-body.txt + run: script/i18n/report-reset-files.js --report-type=pull-request-body --language=${{ matrix.language }} --log-file=/tmp/batch.log > /tmp/pr-body.txt + + - name: Push filtered translations + run: git push origin ${{ steps.set-branch.outputs.BRANCH_NAME }} + + # TODO: bring this step back + # - name: Close existing stale batches + # uses: lee-dohm/close-matching-issues@e9e43aad2fa6f06a058cedfd8fb975fd93b56d8f + # with: + # token: ${{ secrets.OCTOMERGER_PAT_WITH_REPO_AND_WORKFLOW_SCOPE }} + # query: 'type:pr label:translation-batch-${{ matrix.language }}' + + # TODO: bring labels back into the PR script + - name: Create translation batch pull request + env: + GITHUB_TOKEN: ${{ secrets.DOCUBOT_REPO_PAT }} + TITLE: '[DO NOT MERGE] Msft: New translation batch for ${{ matrix.language }}' + BASE: 'main' + HEAD: ${{ steps.set-branch.outputs.BRANCH_NAME }} + LANGUAGE: ${{ matrix.language }} + BODY_FILE: '/tmp/pr-body.txt' + run: .github/actions-scripts/msft-create-translation-batch-pr.js + + # TODO: bring back these steps + # - name: Approve PR + # if: github.ref_name == 'main' + # env: + # GITHUB_TOKEN: ${{ secrets.OCTOMERGER_PAT_WITH_REPO_AND_WORKFLOW_SCOPE }} + # run: gh pr review --approve || echo "Nothing to approve" + + # - name: Set auto-merge + # if: github.ref_name == 'main' + # env: + # GITHUB_TOKEN: ${{ secrets.OCTOMERGER_PAT_WITH_REPO_AND_WORKFLOW_SCOPE }} + # run: gh pr merge ${{ steps.set-branch.outputs.BRANCH_NAME }} --auto --squash || echo "Nothing to merge" + + # # When the maximum execution time is reached for this job, Actions cancels the workflow run. + # # This emits a notification for the first responder to triage. + # - name: Send Slack notification if workflow is cancelled + # uses: someimportantcompany/github-actions-slack-message@f8d28715e7b8a4717047d23f48c39827cacad340 + # if: cancelled() + # with: + # channel: ${{ secrets.DOCS_ALERTS_SLACK_CHANNEL_ID }} + # bot-token: ${{ secrets.SLACK_DOCS_BOT_TOKEN }} + # color: failure + # text: 'The new translation batch for ${{ matrix.language }} was cancelled.' + + # # Emit a notification for the first responder to triage if the workflow failed. + # - 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: 'The new translation batch for ${{ matrix.language }} failed.' diff --git a/.github/workflows/open-enterprise-issue.yml b/.github/workflows/open-enterprise-issue.yml index 17229bf0d0..174ac7a438 100644 --- a/.github/workflows/open-enterprise-issue.yml +++ b/.github/workflows/open-enterprise-issue.yml @@ -24,7 +24,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/openapi-decorate.yml b/.github/workflows/openapi-decorate.yml index f7d85db1c4..e803204c0c 100644 --- a/.github/workflows/openapi-decorate.yml +++ b/.github/workflows/openapi-decorate.yml @@ -44,7 +44,7 @@ jobs: - name: Setup node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/openapi-schema-check.yml b/.github/workflows/openapi-schema-check.yml index 68bcf982af..12a59b3db8 100644 --- a/.github/workflows/openapi-schema-check.yml +++ b/.github/workflows/openapi-schema-check.yml @@ -44,7 +44,7 @@ jobs: - name: Setup node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/orphaned-assets-check.yml b/.github/workflows/orphaned-assets-check.yml index 275dec0c53..b546f867de 100644 --- a/.github/workflows/orphaned-assets-check.yml +++ b/.github/workflows/orphaned-assets-check.yml @@ -27,7 +27,7 @@ jobs: - name: Setup node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install diff --git a/.github/workflows/os-ready-for-review.yml b/.github/workflows/os-ready-for-review.yml index c1036f0430..5c336a47e7 100644 --- a/.github/workflows/os-ready-for-review.yml +++ b/.github/workflows/os-ready-for-review.yml @@ -49,7 +49,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/pa11y.yml b/.github/workflows/pa11y.yml index 918d1f9e47..b8b4961b61 100644 --- a/.github/workflows/pa11y.yml +++ b/.github/workflows/pa11y.yml @@ -23,7 +23,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/package-lock-lint.yml b/.github/workflows/package-lock-lint.yml index 5c652e8412..ed400d05bf 100644 --- a/.github/workflows/package-lock-lint.yml +++ b/.github/workflows/package-lock-lint.yml @@ -29,7 +29,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x - name: Run check run: | diff --git a/.github/workflows/ready-for-doc-review.yml b/.github/workflows/ready-for-doc-review.yml index 049aba3ef0..4fa906cdb6 100644 --- a/.github/workflows/ready-for-doc-review.yml +++ b/.github/workflows/ready-for-doc-review.yml @@ -25,7 +25,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/remove-unused-assets.yml b/.github/workflows/remove-unused-assets.yml index 1b70808363..e966727b9a 100644 --- a/.github/workflows/remove-unused-assets.yml +++ b/.github/workflows/remove-unused-assets.yml @@ -29,7 +29,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: npm ci run: npm ci diff --git a/.github/workflows/repo-sync.yml b/.github/workflows/repo-sync.yml index b6f95a5090..1d4910a640 100644 --- a/.github/workflows/repo-sync.yml +++ b/.github/workflows/repo-sync.yml @@ -104,7 +104,7 @@ jobs: - name: Setup node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies run: npm ci diff --git a/.github/workflows/sync-search-indices.yml b/.github/workflows/sync-search-indices.yml index 0e9a235ea8..d2f3237335 100644 --- a/.github/workflows/sync-search-indices.yml +++ b/.github/workflows/sync-search-indices.yml @@ -58,7 +58,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/sync-search-pr.yml b/.github/workflows/sync-search-pr.yml index a582e44b43..eb867b341c 100644 --- a/.github/workflows/sync-search-pr.yml +++ b/.github/workflows/sync-search-pr.yml @@ -31,7 +31,7 @@ jobs: - name: Setup node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index 0fc88729c8..cc146ee909 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -125,7 +125,7 @@ jobs: - name: Setup node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/triage-unallowed-internal-changes.yml b/.github/workflows/triage-unallowed-internal-changes.yml index 308e6f75d7..498866d74e 100644 --- a/.github/workflows/triage-unallowed-internal-changes.yml +++ b/.github/workflows/triage-unallowed-internal-changes.yml @@ -61,7 +61,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install dependencies diff --git a/.github/workflows/update-graphql-files.yml b/.github/workflows/update-graphql-files.yml index c545d1c6dc..900dfe74f4 100644 --- a/.github/workflows/update-graphql-files.yml +++ b/.github/workflows/update-graphql-files.yml @@ -36,7 +36,7 @@ jobs: - name: Setup Node uses: actions/setup-node@1f8c6b94b26d0feae1e387ca63ccbdc44d27b561 with: - node-version: 16.14.x + node-version: 16.15.x cache: npm - name: Install Node.js dependencies run: npm ci diff --git a/Dockerfile b/Dockerfile index c4b3447df0..93f63c17f4 100644 --- a/Dockerfile +++ b/Dockerfile @@ -3,7 +3,7 @@ # -------------------------------------------------------------------------------- # BASE IMAGE # -------------------------------------------------------------------------------- -FROM node:16.13.2-alpine@sha256:f21f35732964a96306a84a8c4b5a829f6d3a0c5163237ff4b6b8b34f8d70064b as base +FROM node:16.15.0-alpine@sha256:1a9a71ea86aad332aa7740316d4111ee1bd4e890df47d3b5eff3e5bded3b3d10 as base # This directory is owned by the node user ARG APP_HOME=/home/node/app diff --git a/assets/images/help/enterprises/cancel-enterprise-member-invitation.png b/assets/images/help/enterprises/cancel-enterprise-member-invitation.png new file mode 100644 index 0000000000..0eb6bd94c3 Binary files /dev/null and b/assets/images/help/enterprises/cancel-enterprise-member-invitation.png differ diff --git a/assets/images/help/repository/PR-bypass-requirements-with-apps.png b/assets/images/help/repository/PR-bypass-requirements-with-apps.png new file mode 100644 index 0000000000..8403bbe8d3 Binary files /dev/null and b/assets/images/help/repository/PR-bypass-requirements-with-apps.png differ diff --git a/assets/images/help/repository/PR-review-required-dismissals-with-apps.png b/assets/images/help/repository/PR-review-required-dismissals-with-apps.png new file mode 100644 index 0000000000..bd2f52119c Binary files /dev/null and b/assets/images/help/repository/PR-review-required-dismissals-with-apps.png differ diff --git a/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png b/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png new file mode 100644 index 0000000000..06518339cf Binary files /dev/null and b/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png differ diff --git a/assets/images/help/repository/review-calls-to-vulnerable-functions.png b/assets/images/help/repository/review-calls-to-vulnerable-functions.png index 3b7ff3172d..399920b7ef 100644 Binary files a/assets/images/help/repository/review-calls-to-vulnerable-functions.png and b/assets/images/help/repository/review-calls-to-vulnerable-functions.png differ diff --git a/assets/images/help/writing/dollar-sign-inline-math-expression.png b/assets/images/help/writing/dollar-sign-inline-math-expression.png new file mode 100644 index 0000000000..847c172106 Binary files /dev/null and b/assets/images/help/writing/dollar-sign-inline-math-expression.png differ diff --git a/assets/images/help/writing/dollar-sign-within-math-expression.png b/assets/images/help/writing/dollar-sign-within-math-expression.png new file mode 100644 index 0000000000..bdd23ab429 Binary files /dev/null and b/assets/images/help/writing/dollar-sign-within-math-expression.png differ diff --git a/assets/images/help/writing/inline-math-markdown-rendering.png b/assets/images/help/writing/inline-math-markdown-rendering.png new file mode 100644 index 0000000000..ba32bc74d5 Binary files /dev/null and b/assets/images/help/writing/inline-math-markdown-rendering.png differ diff --git a/assets/images/help/writing/math-expression-as-a-block-rendering.png b/assets/images/help/writing/math-expression-as-a-block-rendering.png new file mode 100644 index 0000000000..b1892ec7a5 Binary files /dev/null and b/assets/images/help/writing/math-expression-as-a-block-rendering.png differ diff --git a/components/article/ArticlePage.tsx b/components/article/ArticlePage.tsx index 7ce139d096..64870ad3ad 100644 --- a/components/article/ArticlePage.tsx +++ b/components/article/ArticlePage.tsx @@ -22,12 +22,6 @@ const ClientSideHighlightJS = dynamic(() => import('./ClientSideHighlightJS'), { // Mapping of a "normal" article to it's interactive counterpart const interactiveAlternatives: Record = { - '/actions/automating-builds-and-tests/building-and-testing-nodejs': { - href: '/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python?langId=nodejs', - }, - '/actions/automating-builds-and-tests/building-and-testing-python': { - href: '/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python?langId=python', - }, '/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces': { href: '/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces?langId=nodejs', diff --git a/components/context/MainContext.tsx b/components/context/MainContext.tsx index 3783e1e094..59755e4797 100644 --- a/components/context/MainContext.tsx +++ b/components/context/MainContext.tsx @@ -107,6 +107,7 @@ export type MainContextT = { fullTitle?: string introPlainText?: string hidden: boolean + noEarlyAccessBanner: boolean permalinks?: Array<{ languageCode: string relativePath: string @@ -171,6 +172,7 @@ export const getMainContext = (req: any, res: any): MainContextT => { ]) ), hidden: req.context.page.hidden || false, + noEarlyAccessBanner: req.context.page.noEarlyAccessBanner || false, }, enterpriseServerReleases: pick(req.context.enterpriseServerReleases, [ 'isOldestReleaseDeprecated', diff --git a/components/context/PlaygroundContext.tsx b/components/context/PlaygroundContext.tsx index 67a7a2c787..f2753d8555 100644 --- a/components/context/PlaygroundContext.tsx +++ b/components/context/PlaygroundContext.tsx @@ -2,16 +2,12 @@ import React, { createContext, useContext, useState } from 'react' import { CodeLanguage, PlaygroundArticleT } from 'components/playground/types' import { useRouter } from 'next/router' -import actionsJsArticle from 'components/playground/content/actions/guides/building-and-testing-nodejs-or-python/nodejs' -import actionsPyArticle from 'components/playground/content/actions/guides/building-and-testing-nodejs-or-python/python' import codespacesJsArticle from 'components/playground/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces/nodejs' import codespacesPyArticle from 'components/playground/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces/python' import codespacesNetArticle from 'components/playground/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces/dotnet' import codespacesJavaArticle from 'components/playground/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces/java' const articles = [ - actionsJsArticle, - actionsPyArticle, codespacesJsArticle, codespacesPyArticle, codespacesJavaArticle, diff --git a/components/page-header/HeaderNotifications.tsx b/components/page-header/HeaderNotifications.tsx index b677cff4be..4b696bc5f6 100644 --- a/components/page-header/HeaderNotifications.tsx +++ b/components/page-header/HeaderNotifications.tsx @@ -21,7 +21,7 @@ type Notif = { export const HeaderNotifications = () => { const router = useRouter() const { currentVersion } = useVersion() - const { relativePath, allVersions, data, userLanguage, currentPathWithoutLanguage } = + const { relativePath, allVersions, data, userLanguage, currentPathWithoutLanguage, page } = useMainContext() const { languages } = useLanguages() const { t } = useTranslation('header') @@ -69,7 +69,7 @@ export const HeaderNotifications = () => { ...translationNotices, ...releaseNotices, // ONEOFF EARLY ACCESS NOTICE - (relativePath || '').includes('early-access/') + (relativePath || '').includes('early-access/') && !page.noEarlyAccessBanner ? { type: NotificationType.EARLY_ACCESS, content: t('notices.early_access'), diff --git a/components/playground/content/actions/guides/building-and-testing-nodejs-or-python/nodejs.tsx b/components/playground/content/actions/guides/building-and-testing-nodejs-or-python/nodejs.tsx deleted file mode 100644 index 13f4b5de6f..0000000000 --- a/components/playground/content/actions/guides/building-and-testing-nodejs-or-python/nodejs.tsx +++ /dev/null @@ -1,536 +0,0 @@ -import dedent from 'ts-dedent' -import { PlaygroundArticleT } from 'components/playground/types' - -const article: PlaygroundArticleT = { - title: 'Building and testing Node.js', - shortTitle: 'Build & test Node.js', - topics: ['CI', 'Node', 'JavaScript'], - type: 'tutorial', - slug: '/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python', - originalArticle: '/actions/automating-builds-and-tests/building-and-testing-nodejs', - codeLanguageId: 'nodejs', - intro: dedent` - This guide shows you how to create a continuous integration (CI) workflow that builds and tests Node.js code. If your CI tests pass, you may want to deploy your code or publish a package. - `, - prerequisites: dedent` - We recommend that you have a basic understanding of Node.js, YAML, workflow configuration options, and how to create a workflow file. For more information, see: - - - [Learn GitHub Actions](/actions/learn-github-actions) - - [Getting started with Node.js](https://nodejs.org/en/docs/guides/getting-started-guide/) - `, - contentBlocks: [ - { - codeBlock: { - id: '0', - }, - type: 'default', - title: 'Using the Node.js starter workflow', - content: dedent` - GitHub provides a Node.js starter workflow that will work for most Node.js projects. This guide includes npm and Yarn examples that you can use to customize the starter workflow. For more information, see the [Node.js starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml). - - To get started quickly, add the starter workflow to the \`.github/workflows\` directory of your repository. The example workflow assumes that the default branch for your repository is \`main\`. - `, - }, - { - codeBlock: { - id: '0', - highlight: 12, - }, - type: 'default', - title: 'Running on a different operating system', - content: dedent` - The starter workflow configures jobs to run on Linux, using the GitHub-hosted \`ubuntu-latest\` runners. You can change the \`runs-on\` key to run your jobs on a different operating system. For example, you can use the GitHub-hosted Windows runners. - - \`\`\`yaml - runs-on: windows-latest - \`\`\` - - Or, you can run on the GitHub-hosted macOS runners. - - \`\`\`yaml - runs-on: macos-latest - \`\`\` - - You can also run jobs in Docker containers, or you can provide a self-hosted runner that runs on your own infrastructure. For more information, see "[Workflow syntax for GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)." - `, - }, - { - codeBlock: { - id: '0', - highlight: [14, 23], - }, - type: 'default', - title: 'Specifying the Node.js version', - content: dedent` - The easiest way to specify a Node.js version is by using the \`setup-node\` action provided by GitHub. For more information see, [\`setup-node\`](https://github.com/actions/setup-node/). - - The \`setup-node\` action takes a Node.js version as an input and configures that version on the runner. The \`setup-node\` action finds a specific version of Node.js from the tools cache on each runner and adds the necessary binaries to \`PATH\`, which persists for the rest of the job. Using the \`setup-node\` action is the recommended way of using Node.js with GitHub Actions because it ensures consistent behavior across different runners and different versions of Node.js. If you are using a self-hosted runner, you must install Node.js and add it to \`PATH\`. - - The starter workflow includes a matrix strategy that builds and tests your code with four Node.js versions: 10.x, 12.x, 14.x, and 15.x. The 'x' is a wildcard character that matches the latest minor and patch release available for a version. Each version of Node.js specified in the \`node-version\` array creates a job that runs the same steps. - - Each job can access the value defined in the matrix \`node-version\` array using the \`matrix\` context. The \`setup-node\` action uses the context as the \`node-version\` input. The \`setup-node\` action configures each job with a different Node.js version before building and testing code. For more information about matrix strategies and contexts, see "[Workflow syntax for GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" and "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions)." - `, - }, - { - codeBlock: { - id: '1', - highlight: 16, - }, - type: 'sub-section', - content: dedent` - Alternatively, you can build and test with exact Node.js versions. - `, - }, - { - codeBlock: { - id: '2', - highlight: 19, - }, - type: 'sub-section', - content: dedent` - Or, you can build and test using a single version of Node.js too. - - If you don't specify a Node.js version, GitHub uses the environment's default Node.js version. - For more information, see "[Specifications for GitHub-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". - `, - }, - { - codeBlock: { - id: '3', - highlight: 21, - }, - type: 'default', - title: 'Installing dependencies', - content: dedent` - GitHub-hosted runners have npm and Yarn dependency managers installed. You can use npm and Yarn to install dependencies in your workflow before building and testing your code. The Windows and Linux GitHub-hosted runners also have Grunt, Gulp, and Bower installed. - - When using GitHub-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)." - `, - }, - { - codeBlock: { - id: '4', - highlight: 21, - }, - type: 'sub-section', - title: 'Example using npm', - content: dedent` - This example installs the dependencies defined in the *package.json* file. For more information, see [\`npm install\`](https://docs.npmjs.com/cli/install). - `, - }, - { - codeBlock: { - id: '2', - highlight: 21, - }, - type: 'sub-section-2', - content: dedent` - Using \`npm ci\` installs the versions in the *package-lock.json* or *npm-shrinkwrap.json* file and prevents updates to the lock file. Using \`npm ci\` is generally faster than running \`npm install\`. For more information, see [\`npm ci\`](https://docs.npmjs.com/cli/ci.html) and "[Introducing \`npm ci\` for faster, more reliable builds](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable)." - `, - }, - { - codeBlock: { - id: '5', - highlight: [21, 23], - }, - type: 'sub-section', - title: 'Example using Yarn', - content: dedent` - This example installs the dependencies defined in the *package.json* file. For more information, see [\`yarn install\`](https://yarnpkg.com/en/docs/cli/install). - `, - }, - { - codeBlock: { - id: '6', - highlight: 21, - }, - type: 'sub-section-2', - content: dedent` - Alternatively, you can pass \`--frozen-lockfile\` to install the versions in the *yarn.lock* file and prevent updates to the *yarn.lock* file. - `, - }, - { - codeBlock: { - id: '7', - }, - type: 'sub-section', - title: 'Example using a private registry and creating the .npmrc file', - content: dedent` - You can use the \`setup-node\` action to create a local *.npmrc* file on the runner that configures the default registry and scope. The \`setup-node\` action also accepts an authentication token as input, used to access private registries or publish node packages. For more information, see [\`setup-node\`](https://github.com/actions/setup-node/). - - To authenticate to your private registry, you'll need to store your npm authentication token as a secret. For example, create a repository secret called \`NPM_TOKEN\`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." - - In this example, the secret \`NPM_TOKEN\` stores the npm authentication token. The \`setup-node\` action configures the *.npmrc* file to read the npm authentication token from the \`NODE_AUTH_TOKEN\` environment variable. When using the \`setup-node\` action to create an *.npmrc* file, you must set the \`NODE_AUTH_TOKEN\` environment variable with the secret that contains your npm authentication token. - - Before installing dependencies, use the \`setup-node\` action to create the *.npmrc* file. The action has two input parameters. The \`node-version\` parameter sets the Node.js version, and the \`registry-url\` parameter sets the default registry. If your package registry uses scopes, you must use the \`scope\` parameter. For more information, see [\`npm-scope\`](https://docs.npmjs.com/misc/scope). - - This example creates an *.npmrc* file with the following contents: - - \`\`\`ini - //registry.npmjs.org/:_authToken=\${NODE_AUTH_TOKEN} - @octocat:registry=https://registry.npmjs.org/ - always-auth=true - \`\`\` - `, - }, - { - codeBlock: { - id: '8', - }, - type: 'sub-section', - title: 'Example caching dependencies', - content: dedent` - - When using GitHub-hosted runners, you can cache and restore the dependencies using the [\`setup-node\` action](https://github.com/actions/setup-node). To cache dependencies with the \`setup-node\` action, you must have a \`package-lock.json\`, \`yarn.lock\`, or \`pnpm-lock.yaml\` file in the root of the repository. - - If you have a custom requirement or need finer controls for caching, you can use the [\`cache\` action](https://github.com/marketplace/actions/cache). For more information, see [Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows) and the [\`cache\` action](https://github.com/marketplace/actions/cache). - - `, - }, - { - codeBlock: { - id: '9', - highlight: [21, 22], - }, - type: 'default', - title: 'Building and testing your code', - content: dedent` - You can use the same commands that you use locally to build and test your code. For example, if you run \`npm run build\` to run build steps defined in your *package.json* file and \`npm test\` to run your test suite, you would add those commands in your workflow file. - `, - }, - { - codeBlock: { - id: '9', - }, - type: 'default', - title: 'Packaging workflow data as artifacts', - content: dedent` - You can save artifacts from your build and test steps to view after a job completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." - `, - }, - { - codeBlock: { - id: '9', - }, - type: 'default', - title: 'Publishing to package registries', - content: dedent` - You can configure your workflow to publish your Node.js package to a package registry after your CI tests pass. For more information about publishing to npm and GitHub Packages, see "[Publishing Node.js packages](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)." - `, - }, - ], - codeBlocks: { - '0': { - fileName: '.github/workflows/example.yml', - language: 'yaml', - code: dedent` - name: Node.js CI - - on: - push: - branches: [ main ] - pull_request: - branches: [ main ] - - jobs: - build: - - runs-on: ubuntu-latest - - strategy: - matrix: - node-version: [10.x, 12.x, 14.x, 15.x] - - steps: - - uses: actions/checkout@v3 - - name: Use Node.js \${{ matrix.node-version }} - uses: actions/setup-node@v3 - with: - node-version: \${{ matrix.node-version }} - - name: Install dependencies - run: npm ci - - run: npm run build --if-present - - run: npm test - `, - }, - '1': { - fileName: '.github/workflows/example.yml', - language: 'yaml', - code: dedent` - name: Node.js CI - - on: - push: - branches: [ main ] - pull_request: - branches: [ main ] - - jobs: - build: - - runs-on: ubuntu-latest - - strategy: - matrix: - node-version: [8.16.2, 10.17.0] - - steps: - - uses: actions/checkout@v3 - - name: Use Node.js \${{ matrix.node-version }} - uses: actions/setup-node@v3 - with: - node-version: \${{ matrix.node-version }} - - name: Install dependencies - run: npm ci - - run: npm run build --if-present - - run: npm test - `, - }, - '2': { - fileName: '.github/workflows/example.yml', - language: 'yaml', - code: dedent` - name: Node.js CI - - on: - push: - branches: [ main ] - pull_request: - branches: [ main ] - - jobs: - build: - - runs-on: ubuntu-latest - - steps: - - uses: actions/checkout@v3 - - name: Use Node.js - uses: actions/setup-node@v3 - with: - node-version: '12.x' - - name: Install dependencies - run: npm ci - - run: npm run build --if-present - - run: npm test - `, - }, - '3': { - fileName: '.github/workflows/example.yml', - language: 'yaml', - code: dedent` - name: Node.js CI - - on: - push: - branches: [ main ] - pull_request: - branches: [ main ] - - jobs: - build: - - runs-on: ubuntu-latest - - steps: - - uses: actions/checkout@v3 - - name: Use Node.js - uses: actions/setup-node@v3 - with: - node-version: '12.x' - - name: Install dependencies - run: npm install - - run: npm run build --if-present - - run: npm test - `, - }, - '4': { - fileName: '.github/workflows/example.yml', - language: 'yaml', - code: dedent` - name: Node.js CI - - on: - push: - branches: [ main ] - pull_request: - branches: [ main ] - - jobs: - build: - - runs-on: ubuntu-latest - - steps: - - uses: actions/checkout@v3 - - name: Use Node.js - uses: actions/setup-node@v3 - with: - node-version: '12.x' - - name: Install dependencies - run: npm install - - run: npm run build --if-present - - run: npm test - `, - }, - '5': { - fileName: '.github/workflows/example.yml', - language: 'yaml', - code: dedent` - name: Node.js CI - - on: - push: - branches: [ main ] - pull_request: - branches: [ main ] - - jobs: - build: - - runs-on: ubuntu-latest - - steps: - - uses: actions/checkout@v3 - - name: Use Node.js - uses: actions/setup-node@v3 - with: - node-version: '12.x' - - name: Install dependencies - run: yarn - - run: yarn run build - - run: yarn run test - `, - }, - '6': { - fileName: '.github/workflows/example.yml', - language: 'yaml', - code: dedent` - name: Node.js CI - - on: - push: - branches: [ main ] - pull_request: - branches: [ main ] - - jobs: - build: - - runs-on: ubuntu-latest - - steps: - - uses: actions/checkout@v3 - - name: Use Node.js - uses: actions/setup-node@v3 - with: - node-version: '12.x' - - name: Install dependencies - run: yarn --frozen-lockfile - - run: yarn run build - - run: yarn run test - `, - }, - '7': [ - { - fileName: '.github/workflows/example.yml', - language: 'yaml', - code: dedent` - name: Node.js CI - - on: - push: - branches: [ main ] - pull_request: - branches: [ main ] - - jobs: - build: - - runs-on: ubuntu-latest - - steps: - - uses: actions/checkout@v3 - - name: Use Node.js - uses: actions/setup-node@v3 - with: - always-auth: true - node-version: '12.x' - registry-url: https://registry.npmjs.org - scope: '@octocat' - - name: Install dependencies - run: npm ci - env: - NODE_AUTH_TOKEN: \${{secrets.NPM_TOKEN}} - `, - }, - { - fileName: '.npmrc', - language: 'ini', - code: dedent` - //registry.npmjs.org/:_authToken=\${NODE_AUTH_TOKEN} - @octocat:registry=https://registry.npmjs.org/ - always-auth=true - `, - }, - ], - '8': { - fileName: '.github/workflows/example.yml', - language: 'yaml', - code: dedent` - name: Node.js CI - - on: - push: - branches: [ main ] - pull_request: - branches: [ main ] - - jobs: - build: - - runs-on: ubuntu-latest - - steps: - - uses: actions/checkout@v3 - - name: Use Node.js - uses: actions/setup-node@v3 - with: - node-version: '12.x' - cache: 'npm' - - name: Install dependencies - run: npm ci - `, - }, - '9': { - fileName: '.github/workflows/example.yml', - language: 'yaml', - code: dedent` - name: Node.js CI - - on: - push: - branches: [ main ] - pull_request: - branches: [ main ] - - jobs: - build: - - runs-on: ubuntu-latest - - steps: - - uses: actions/checkout@v3 - - name: Use Node.js - uses: actions/setup-node@v3 - with: - node-version: '12.x' - - run: npm install - - run: npm run build --if-present - - run: npm test - `, - }, - }, -} - -export default article diff --git a/components/playground/content/actions/guides/building-and-testing-nodejs-or-python/python.tsx b/components/playground/content/actions/guides/building-and-testing-nodejs-or-python/python.tsx deleted file mode 100644 index b9f1a04976..0000000000 --- a/components/playground/content/actions/guides/building-and-testing-nodejs-or-python/python.tsx +++ /dev/null @@ -1,564 +0,0 @@ -import dedent from 'ts-dedent' -import { PlaygroundArticleT } from 'components/playground/types' - -const article: PlaygroundArticleT = { - title: 'Building and testing Python', - shortTitle: 'Build & test Python', - topics: ['CI', 'Python'], - type: 'tutorial', - slug: '/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python', - originalArticle: '/actions/automating-builds-and-tests/building-and-testing-python', - codeLanguageId: 'py', - intro: dedent` - This guide shows you how to build, test, and publish a Python package. - - GitHub-hosted runners have a tools cache with pre-installed software, which includes Python and PyPy. You don't have to install anything! For a full list of up-to-date software and the pre-installed versions of Python and PyPy, see "[Specifications for GitHub-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". - `, - prerequisites: dedent` - You should be familiar with YAML and the syntax for GitHub Actions. For more information, see "[Learn GitHub-Actions](/actions/learn-github-actions)." - - We recommend that you have a basic understanding of Python, PyPy, and pip. For more information, see: - - [Getting started with Python](https://www.python.org/about/gettingstarted/) - - [PyPy](https://pypy.org/) - - [Pip package manager](https://pypi.org/project/pip/) - `, - contentBlocks: [ - { - type: 'default', - codeBlock: { - id: '0', - }, - title: 'Using the Python starter workflow', - content: dedent` - GitHub provides a Python starter workflow that should work for most Python projects. This guide includes examples that you can use to customize the starter workflow. For more information, see the [Python starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml). - - To get started quickly, add the starter workflow to the \`.github/workflows\` directory of your repository. - `, - }, - { - type: 'default', - codeBlock: { - id: '0', - }, - title: 'Specifying a Python version', - content: dedent` - To use a pre-installed version of Python or PyPy on a GitHub-hosted runner, use the \`setup-python\` action. This action finds a specific version of Python or PyPy from the tools cache on each runner and adds the necessary binaries to \`PATH\`, which persists for the rest of the job. If a specific version of Python is not pre-installed in the tools cache, the \`setup-python\` action will download and set up the appropriate version from the [\`python-versions\`](https://github.com/actions/python-versions) repository. - - Using the \`setup-python\` action is the recommended way of using Python with GitHub Actions because it ensures consistent behavior across different runners and different versions of Python. If you are using a self-hosted runner, you must install Python and add it to \`PATH\`. For more information, see the [\`setup-python\` action](https://github.com/marketplace/actions/setup-python). - - The table below describes the locations for the tools cache in each GitHub-hosted runner. - - || Ubuntu | Mac | Windows | - |------|-------|------|----------| - |**Tool Cache Directory** |\`/opt/hostedtoolcache/*\`|\`/Users/runner/hostedtoolcache/*\`|\`C:\hostedtoolcache\windows\*\`| - |**Python Tool Cache**|\`/opt/hostedtoolcache/Python/*\`|\`/Users/runner/hostedtoolcache/Python/*\`|\`C:\hostedtoolcache\windows\Python\*\`| - |**PyPy Tool Cache**|\`/opt/hostedtoolcache/PyPy/*\`|\`/Users/runner/hostedtoolcache/PyPy/*\`|\`C:\hostedtoolcache\windows\PyPy\*\`| - - If you are using a self-hosted runner, you can configure the runner to use the \`setup-python\` action to manage your dependencies. For more information, see [using setup-python with a self-hosted runner](https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner) in the \`setup-python\` README. - - GitHub supports semantic versioning syntax. For more information, see "[Using semantic versioning](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept)" and the "[Semantic versioning specification](https://semver.org/)." - `, - }, - { - type: 'sub-section', - codeBlock: { - id: '1', - }, - title: 'Using multiple Python versions', - content: dedent` - This example uses a matrix to run the job on multiple Python versions: 2.7, 3.6, 3.7, 3.8, and 3.9. For more information about matrix strategies and contexts, see "[Workflow syntax for GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix)" and "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions)." - `, - }, - { - type: 'sub-section', - codeBlock: { - id: '2', - }, - title: 'Using a specific Python version', - content: dedent` - You can configure a specific version of python. For example, 3.8. Alternatively, you can use semantic version syntax to get the latest minor release. This example uses the latest minor release of Python 3. - `, - }, - { - type: 'sub-section', - codeBlock: { - id: '3', - }, - title: 'Excluding a version', - content: dedent` - If you specify a version of Python that is not available, \`setup-python\` fails with an error such as: \`##[error]Version 3.4 with arch x64 not found\`. The error message includes the available versions. - - You can also use the \`exclude\` keyword in your workflow if there is a configuration of Python that you do not wish to run. For more information, see "[Workflow syntax for GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy)." - `, - }, - { - type: 'sub-section', - codeBlock: { - id: '3', - }, - title: 'Using the default Python version', - content: dedent` - We recommend using \`setup-python\` to configure the version of Python used in your workflows because it helps make your dependencies explicit. If you don't use \`setup-python\`, the default version of Python set in \`PATH\` is used in any shell when you call \`python\`. The default version of Python varies between GitHub-hosted runners, which may cause unexpected changes or use an older version than expected. - - | GitHub-hosted runner | Description | - |----|----| - | Ubuntu | Ubuntu runners have multiple versions of system Python installed under \`/usr/bin/python\` and \`/usr/bin/python3\`. The Python versions that come packaged with Ubuntu are in addition to the versions that GitHub installs in the tools cache. | - | Windows | Excluding the versions of Python that are in the tools cache, Windows does not ship with an equivalent version of system Python. To maintain consistent behavior with other runners and to allow Python to be used out-of-the-box without the \`setup-python\` action, GitHub adds a few versions from the tools cache to \`PATH\`.| - | macOS | The macOS runners have more than one version of system Python installed, in addition to the versions that are part of the tools cache. The system Python versions are located in the \`/usr/local/Cellar/python/*\` directory. | - `, - }, - { - type: 'default', - codeBlock: { - id: '4', - }, - title: 'Installing dependencies', - content: dedent` - GitHub-hosted runners have the pip package manager installed. You can use pip to install dependencies from the PyPI package registry before building and testing your code. This example installs or upgrades the \`pip\` package installer and the \`setuptools\` and \`wheel\` packages. - - When using GitHub-hosted runners, you can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows)." - `, - }, - { - type: 'sub-section', - codeBlock: { - id: '5', - }, - title: 'Requirements file', - content: dedent` - After you update \`pip\`, a typical next step is to install dependencies from *requirements.txt*. - `, - }, - { - type: 'sub-section', - codeBlock: { - id: '6', - }, - title: 'Caching Dependencies', - content: dedent` - - When using GitHub-hosted runners, you can cache and restore the dependencies using the [\`setup-python\` action](https://github.com/actions/setup-python). By default, the \`setup-python\` action searches for the dependency file (\`requirements.txt\` for pip or \`Pipfile.lock\` for pipenv) in the whole repository. - - If you have a custom requirement or need finer controls for caching, you can use the [\`cache\` action](https://github.com/marketplace/actions/cache). Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example shown here, depending on the operating system you use. For more information, see [Caching dependencies to speed up workflows](/actions/guides/caching-dependencies-to-speed-up-workflows) and the [\`cache\` action](https://github.com/marketplace/actions/cache). - - `, - }, - { - type: 'default', - codeBlock: { - id: '7', - }, - title: 'Testing your code', - content: dedent` - You can use the same commands that you use locally to build and test your code. - `, - }, - { - type: 'sub-section', - codeBlock: { - id: '7', - }, - title: 'Testing with pytest and pytest-cov', - content: dedent` - This example installs or upgrades \`pytest\` and \`pytest-cov\`. Tests are then run and output in JUnit format while code coverage results are output in Cobertura. For more information, see [JUnit](https://junit.org/junit5/) and [Cobertura](https://cobertura.github.io/cobertura/). - `, - }, - { - type: 'sub-section', - codeBlock: { - id: '8', - }, - title: 'Using Flake8 to lint code', - content: dedent` - This example installs or upgrades \`flake8\` and uses it to lint all files. For more information, see [Flake8](http://flake8.pycqa.org/en/latest/). - `, - }, - { - type: 'sub-section', - codeBlock: { - id: '9', - }, - title: 'Running tests with tox', - content: dedent` - With GitHub Actions, you can run tests with tox and spread the work across multiple jobs. You'll need to invoke tox using the \`-e py\` option to choose the version of Python in your \`PATH\`, rather than specifying a specific version. For more information, see [tox](https://tox.readthedocs.io/en/latest/). - `, - }, - { - type: 'default', - codeBlock: { - id: '10', - }, - title: 'Packaging workflow data as artifacts', - content: dedent` - You can upload artifacts to view after a workflow completes. For example, you may need to save log files, core dumps, test results, or screenshots. For more information, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." - - This example demonstrates how you can use the \`upload-artifact\` action to archive test results from running \`pytest\`. For more information, see the [\`upload-artifact\` action](https://github.com/actions/upload-artifact). - `, - }, - { - type: 'default', - codeBlock: { - id: '11', - }, - title: 'Publishing to package registries', - content: dedent` - You can configure your workflow to publish your Python package to a package registry once your CI tests pass. This example demonstrates how you can use GitHub Actions to upload your package to PyPI each time you [publish a release](/github/administering-a-repository/managing-releases-in-a-repository). - - For this example, you will need to create two [PyPI API tokens](https://pypi.org/help/#apitoken). You can use secrets to store the access tokens or credentials needed to publish your package. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." - - For more information about the starter workflow, see [\`python-publish\`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml). - `, - }, - ], - codeBlocks: { - '0': { - language: 'yaml', - fileName: '.github/workflows/example.yml', - code: dedent` - name: Python package - - on: [push] - - jobs: - build: - - runs-on: ubuntu-latest - strategy: - matrix: - python-version: ["3.6", "3.7", "3.8", "3.9"] - - steps: - - uses: actions/checkout@v3 - - name: Set up Python \${{ matrix.python-version }} - uses: actions/setup-python@v3 - with: - python-version: \${{ matrix.python-version }} - - name: Install dependencies - run: | - python -m pip install --upgrade pip - pip install flake8 pytest - if [ -f requirements.txt ]; then pip install -r requirements.txt; fi - - name: Lint with flake8 - run: | - # stop the build if there are Python syntax errors or undefined names - flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics - # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide - flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics - - name: Test with pytest - run: | - pytest - `, - }, - '1': { - language: 'yaml', - fileName: '.github/workflows/example.yml', - code: dedent` - name: Python package - - on: [push] - - jobs: - build: - - runs-on: ubuntu-latest - strategy: - # You can use PyPy versions in python-version. - # For example, pypy2 and pypy3 - matrix: - python-version: ["2.7", "3.6", "3.7", "3.8", "3.9"] - - steps: - - uses: actions/checkout@v3 - - name: Set up Python \${{ matrix.python-version }} - uses: actions/setup-python@v3 - with: - python-version: \${{ matrix.python-version }} - # You can test your matrix by printing the current Python version - - name: Display Python version - run: python -c "import sys; print(sys.version)" - `, - }, - '2': { - language: 'yaml', - fileName: '.github/workflows/example.yml', - code: dedent` - name: Python package - - on: [push] - - jobs: - build: - - runs-on: ubuntu-latest - - steps: - - uses: actions/checkout@v3 - - name: Set up Python 3.x - uses: actions/setup-python@v3 - with: - # Semantic version range syntax or exact version of a Python version - python-version: '3.x' - # Optional - x64 or x86 architecture, defaults to x64 - architecture: 'x64' - # You can test your matrix by printing the current Python version - - name: Display Python version - run: python -c "import sys; print(sys.version)" - `, - }, - '3': { - language: 'yaml', - fileName: '.github/workflows/example.yml', - code: dedent` - name: Python package - - on: [push] - - jobs: - build: - - runs-on: \${{ matrix.os }} - strategy: - matrix: - os: [ubuntu-latest, macos-latest, windows-latest] - python-version: ["3.6", "3.7", "3.8", "3.9", pypy2, pypy3] - exclude: - - os: macos-latest - python-version: "3.6" - - os: windows-latest - python-version: "3.6" - `, - }, - '4': { - language: 'yaml', - fileName: '.github/workflows/example.yml', - code: dedent` - name: Python package - - on: [push] - - jobs: - build: - - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v3 - - name: Set up Python - uses: actions/setup-python@v3 - with: - python-version: '3.x' - - name: Install dependencies - run: python -m pip install --upgrade pip setuptools wheel - `, - }, - '5': { - language: 'yaml', - fileName: '.github/workflows/example.yml', - code: dedent` - name: Python package - - on: [push] - - jobs: - build: - - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v3 - - name: Set up Python - uses: actions/setup-python@v3 - with: - python-version: '3.x' - - name: Install dependencies - run: | - python -m pip install --upgrade pip - pip install -r requirements.txt - `, - }, - '6': { - language: 'yaml', - fileName: '.github/workflows/example.yml', - code: dedent` - name: Python package - - on: [push] - - jobs: - build: - - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v3 - - name: Setup Python - uses: actions/setup-python@v3 - with: - python-version: '3.x' - cache: 'pip' - - name: Install dependencies - run: pip install -r requirements.txt - `, - }, - '7': { - language: 'yaml', - fileName: '.github/workflows/example.yml', - code: dedent` - name: Python package - - on: [push] - - jobs: - build: - - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v3 - - name: Set up Python - uses: actions/setup-python@v3 - with: - python-version: '3.x' - - name: Install dependencies - run: | - python -m pip install --upgrade pip - pip install -r requirements.txt - - name: Test with pytest - run: | - pip install pytest - pip install pytest-cov - pytest tests.py --doctest-modules --junitxml=junit/test-results.xml --cov=com --cov-report=xml --cov-report=html - `, - }, - '8': { - language: 'yaml', - fileName: '.github/workflows/example.yml', - code: dedent` - name: Python package - - on: [push] - - jobs: - build: - - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v3 - - name: Set up Python - uses: actions/setup-python@v3 - with: - python-version: '3.x' - - name: Install dependencies - run: | - python -m pip install --upgrade pip - pip install -r requirements.txt - - name: Lint with flake8 - run: | - pip install flake8 - flake8 . - `, - }, - '9': { - language: 'yaml', - fileName: '.github/workflows/example.yml', - code: dedent` - name: Python package - - on: [push] - - jobs: - build: - - runs-on: ubuntu-latest - strategy: - matrix: - python: ["3.7", "3.8", "3.9"] - - steps: - - uses: actions/checkout@v3 - - name: Setup Python - uses: actions/setup-python@v3 - with: - python-version: \${{ matrix.python }} - - name: Install Tox and any other packages - run: pip install tox - - name: Run Tox - # Run tox using the version of Python in \`PATH\` - run: tox -e py - `, - }, - '10': { - language: 'yaml', - fileName: '.github/workflows/example.yml', - code: dedent` - name: Python package - - on: [push] - - jobs: - build: - - runs-on: ubuntu-latest - strategy: - matrix: - python-version: ["3.6", "3.7", "3.8", "3.9"] - - steps: - - uses: actions/checkout@v3 - - name: Setup Python # Set Python version - uses: actions/setup-python@v3 - with: - python-version: \${{ matrix.python-version }} - # Install pip and pytest - - name: Install dependencies - run: | - python -m pip install --upgrade pip - pip install pytest - - name: Test with pytest - run: pytest tests.py --doctest-modules --junitxml=junit/test-results-\${{ matrix.python-version }}.xml - - name: Upload pytest test results - uses: actions/upload-artifact@v3 - with: - name: pytest-results-\${{ matrix.python-version }} - path: junit/test-results-\${{ matrix.python-version }}.xml - # Use always() to always run this step to publish test results when there are test failures - if: \${{ always() }} - `, - }, - '11': { - language: 'yaml', - fileName: '.github/workflows/example.yml', - code: dedent` - # This workflow uses actions that are not certified by GitHub. - # They are provided by a third-party and are governed by - # separate terms of service, privacy policy, and support - # documentation. - - name: Upload Python Package - - on: - release: - types: [published] - - jobs: - deploy: - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v3 - - name: Set up Python - uses: actions/setup-python@v3 - with: - python-version: '3.x' - - name: Install dependencies - run: | - python -m pip install --upgrade pip - pip install build - - name: Build package - run: python -m build - - name: Publish package - uses: pypa/gh-action-pypi-publish@27b31702a0e7fc50959f5ad993c78deac1bdfc29 - with: - user: __token__ - password: \${{ secrets.PYPI_API_TOKEN }} - `, - }, - }, -} - -export default article diff --git a/components/rest/RestPreviewNotice.tsx b/components/rest/RestPreviewNotice.tsx index 5364f56e4b..9cbcc2ec75 100644 --- a/components/rest/RestPreviewNotice.tsx +++ b/components/rest/RestPreviewNotice.tsx @@ -10,7 +10,7 @@ export function RestPreviewNotice({ slug, previews }: Props) { return ( <>

- + {previews.length > 1 ? `${t('rest.reference.preview_notices')}` : `${t('rest.reference.preview_notice')}`} diff --git a/content/account-and-profile/index.md b/content/account-and-profile/index.md index 2c63ecf2ea..df425fc73e 100644 --- a/content/account-and-profile/index.md +++ b/content/account-and-profile/index.md @@ -37,7 +37,7 @@ topics: - Profiles - Notifications children: - - /setting-up-and-managing-your-github-user-account + - /setting-up-and-managing-your-personal-account-on-github - /setting-up-and-managing-your-github-profile - /managing-subscriptions-and-notifications-on-github --- diff --git a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md index 8bf7e159fe..9f48a72b7c 100644 --- a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md @@ -129,8 +129,8 @@ Email notifications from {% data variables.product.product_location %} contain t | --- | --- | | `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. | | `To` field | This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} | -| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
  • `assign`: You were assigned to an issue or pull request.
  • `author`: You created an issue or pull request.
  • `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
  • `comment`: You commented on an issue or pull request.
  • `manual`: There was an update to an issue or pull request you manually subscribed to.
  • `mention`: You were mentioned on an issue or pull request.
  • `push`: Someone committed to a pull request you're subscribed to.
  • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
    • {% endif %}
  • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
  • `subscribed`: There was an update in a repository you're watching.
  • `team_mention`: A team you belong to was mentioned on an issue or pull request.
  • `your_activity`: You opened, commented on, or closed an issue or pull request.
| -| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
  • `assign`: You were assigned to an issue or pull request.
  • `author`: You created an issue or pull request.
  • `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
  • `comment`: You commented on an issue or pull request.
  • `manual`: There was an update to an issue or pull request you manually subscribed to.
  • `mention`: You were mentioned on an issue or pull request.
  • `push`: Someone committed to a pull request you're subscribed to.
  • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • {% ifversion fpt or ghes or ghae or ghec %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
    • {% endif %}
  • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
  • `subscribed`: There was an update in a repository you're watching.
  • `team_mention`: A team you belong to was mentioned on an issue or pull request.
  • `your_activity`: You opened, commented on, or closed an issue or pull request.
| +| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae or ghec %} | `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
  • `low`
  • `moderate`
  • `high`
  • `critical`
For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %} ## Choosing your notification settings @@ -139,7 +139,7 @@ Email notifications from {% data variables.product.product_location %} contain t {% data reusables.notifications-v2.manage-notifications %} 3. On the notifications settings page, choose how you receive notifications when: - There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)." - - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} + - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae or ghec %} - There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% endif %} {% ifversion fpt or ghec %} - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5668 %} - There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."{% endif %} @@ -194,7 +194,7 @@ If you are a member of more than one organization, you can configure each one to 5. Select one of your verified email addresses, then click **Save**. ![Switching your per-org email address](/assets/images/help/notifications/notifications_switching_org_email.gif) -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## {% data variables.product.prodname_dependabot_alerts %} notification options {% data reusables.notifications.vulnerable-dependency-notification-enable %} diff --git a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md index bac654275e..7f2de60a8c 100644 --- a/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md +++ b/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md @@ -112,13 +112,13 @@ To filter notifications for specific activity on {% data variables.product.produ - `is:gist` - `is:issue-or-pull-request` - `is:release` -- `is:repository-invitation`{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +- `is:repository-invitation`{% ifversion fpt or ghes or ghae or ghec %} - `is:repository-vulnerability-alert`{% endif %}{% ifversion fpt or ghec %} - `is:repository-advisory`{% endif %} - `is:team-discussion`{% ifversion fpt or ghec %} - `is:discussion`{% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." {% endif %} @@ -142,7 +142,7 @@ To filter notifications by why you've received an update, you can use the `reaso | `reason:invitation` | When you're invited to a team, organization, or repository. | `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to. | `reason:mention` | You were directly @mentioned. -| `reason:review-requested` | You or a team you're on have been requested to review a pull request.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| `reason:review-requested` | You or a team you're on have been requested to review a pull request.{% ifversion fpt or ghes or ghae or ghec %} | `reason:security-alert` | When a security alert is issued for a repository.{% endif %} | `reason:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged. | `reason:team-mention` | When a team you're a member of is @mentioned. @@ -161,7 +161,7 @@ For example, to see notifications from the octo-org organization, use `org:octo- {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## {% data variables.product.prodname_dependabot %} custom filters {% ifversion fpt or ghec or ghes > 3.2 %} @@ -173,7 +173,7 @@ If you use {% data variables.product.prodname_dependabot %} to keep your depende For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." {% endif %} -{% ifversion ghes < 3.3 or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae %} If you use {% data variables.product.prodname_dependabot %} to tell you about vulnerable dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}: - `is:repository_vulnerability_alert` diff --git a/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md b/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md index 78f74ca3f7..c00c16fcab 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md @@ -91,10 +91,7 @@ The contribution activity section includes a detailed timeline of your work, inc ![Contribution activity time filter](/assets/images/help/profile/contributions_activity_time_filter.png) -{% ifversion fpt or ghes or ghae or ghec %} - ## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %} If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and your enterprise owner enables {% data variables.product.prodname_unified_contributions %}, you can send enterprise contribution counts from to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)." -{% endif %} diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md deleted file mode 100644 index 4913ddd731..0000000000 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md +++ /dev/null @@ -1,92 +0,0 @@ ---- -title: Changing your GitHub username -intro: 'You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %} if your instance uses built-in authentication{% endif %}.' -redirect_from: - - /articles/how-to-change-your-username - - /articles/changing-your-github-user-name - - /articles/renaming-a-user - - /articles/what-happens-when-i-change-my-username - - /articles/changing-your-github-username - - /github/setting-up-and-managing-your-github-user-account/changing-your-github-username - - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username -versions: - fpt: '*' - ghes: '*' - ghec: '*' -topics: - - Accounts -shortTitle: Change your username ---- - -{% ifversion ghec or ghes %} - -{% note %} - -{% ifversion ghec %} - -**Note**: Members of an {% data variables.product.prodname_emu_enterprise %} cannot change usernames. Your enterprise's IdP administrator controls your username for {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." - -{% elsif ghes %} - -**Note**: If you sign into {% data variables.product.product_location %} with LDAP credentials or single sign-on (SSO), only your local administrator can change your username. For more information about authentication methods for {% data variables.product.product_name %}, see "[Authenticating users for {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)." - -{% endif %} - -{% endnote %} - -{% endif %} - -## About username changes - -You can change your username to another username that is not currently in use.{% ifversion fpt or ghec %} If the username you want is not available, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you find a similar username that's still available. - -If you hold a trademark for the username, you can find more information about making a trademark complaint on our [Trademark Policy](/free-pro-team@latest/github/site-policy/github-trademark-policy) page. - -If you do not hold a trademark for the name, you can choose another username or keep your current username. {% data variables.contact.github_support %} cannot release the unavailable username for you. For more information, see "[Changing your username](#changing-your-username)."{% endif %} - -After changing your username, your old username becomes available for anyone else to claim. Most references to your repositories under the old username automatically change to the new username. However, some links to your profile won't automatically redirect. - -{% data variables.product.product_name %} cannot set up redirects for: -- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) using your old username -- Links to [gists](/articles/creating-gists) that include your old username - -{% ifversion fpt or ghec %} - -If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot make changes to your username. {% data reusables.enterprise-accounts.emu-more-info-account %} - -{% endif %} - -## Repository references - -After you change your username, {% data variables.product.product_name %} will automatically redirect references to your repositories. -- Web links to your existing repositories will continue to work. This can take a few minutes to complete after you make the change. -- Command line pushes from your local repository clones to the old remote tracking URLs will continue to work. - -If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working. Because of this possibility, we recommend you update all existing remote repository URLs after changing your username. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)." - -## Links to your previous profile page - -After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your account on {% data variables.product.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}. - -## Your Git commits - -{% ifversion fpt or ghec %}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. For more information on setting your email address, see "[Setting your commit email address](/articles/setting-your-commit-email-address)." - -## Changing your username - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.account_settings %} -3. In the "Change username" section, click **Change username**. - ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %} -4. Read the warnings about changing your username. If you still want to change your username, click **I understand, let's change my username**. - ![Change Username warning button](/assets/images/help/settings/settings-change-username-warning-button.png) -5. Type a new username. - ![New username field](/assets/images/help/settings/settings-change-username-enter-new-username.png) -6. If the username you've chosen is available, click **Change my username**. If the username you've chosen is unavailable, you can try a different username or one of the suggestions you see. - ![Change Username warning button](/assets/images/help/settings/settings-change-my-username-button.png) -{% endif %} - -## Further reading - -- "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"{% ifversion fpt or ghec %} -- "[{% data variables.product.prodname_dotcom %} Username Policy](/free-pro-team@latest/github/site-policy/github-username-policy)"{% endif %} diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md similarity index 50% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md index 77bec09074..5a437e284b 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md @@ -1,10 +1,11 @@ --- -title: GitHub ユーザアカウントの設定と管理 -intro: 'You can manage settings in your GitHub personal account including email preferences, collaborator access for personal repositories, and organization memberships.' +title: Setting up and managing your personal account on GitHub +intro: 'You can manage settings for your personal account on {% data variables.product.prodname_dotcom %}, including email preferences, collaborator access for personal repositories, and organization memberships.' shortTitle: Personal accounts redirect_from: - /categories/setting-up-and-managing-your-github-user-account - /github/setting-up-and-managing-your-github-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account versions: fpt: '*' ghes: '*' @@ -13,7 +14,7 @@ versions: topics: - Accounts children: - - /managing-user-account-settings + - /managing-personal-account-settings - /managing-email-preferences - /managing-access-to-your-personal-repositories - /managing-your-membership-in-organizations diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md similarity index 80% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md index 26c50a8387..acd5024984 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md @@ -6,6 +6,7 @@ redirect_from: - /categories/managing-repository-collaborators - /articles/managing-access-to-your-personal-repositories - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' @@ -19,7 +20,7 @@ children: - /inviting-collaborators-to-a-personal-repository - /removing-a-collaborator-from-a-personal-repository - /removing-yourself-from-a-collaborators-repository - - /maintaining-ownership-continuity-of-your-user-accounts-repositories + - /maintaining-ownership-continuity-of-your-personal-accounts-repositories shortTitle: Access to your repositories --- 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-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md similarity index 96% rename from 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 rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index a62bd18c7a..bad96d321a 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-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md @@ -7,6 +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 + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md similarity index 89% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md index c9a30f220a..61c197248d 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md @@ -1,5 +1,5 @@ --- -title: Maintaining ownership continuity of your user account's repositories +title: Maintaining ownership continuity of your personal account's repositories intro: You can invite someone to manage your user owned repositories if you are not able to. versions: fpt: '*' @@ -10,6 +10,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories shortTitle: Ownership continuity --- ## About successors 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md similarity index 93% rename from 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 rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md index 46a1815b00..e3f43e6d75 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md @@ -10,6 +10,7 @@ redirect_from: - /articles/removing-a-collaborator-from-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md similarity index 90% rename from 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 rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md index b96f880a0c..016d7f01c9 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md @@ -9,6 +9,7 @@ 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 + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md similarity index 91% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md index bf63417856..3b5045f83d 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -5,6 +5,7 @@ redirect_from: - /articles/adding-an-email-address-to-your-github-account - /github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md similarity index 91% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md index 5f3b29272a..b7e112578d 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/blocking-command-line-pushes-that-expose-your-personal-email-address - /github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address versions: fpt: '*' ghec: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md similarity index 92% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md index 107b10430d..de0e77b85f 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/changing-your-primary-email-address - /github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md similarity index 91% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md index 6f5986b82c..af6670e2c7 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md @@ -5,6 +5,7 @@ redirect_from: - /categories/managing-email-preferences - /articles/managing-email-preferences - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md similarity index 92% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md index 0ff79646f6..3f75314c01 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md @@ -5,6 +5,7 @@ redirect_from: - /articles/managing-marketing-emails-from-github - /github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github versions: fpt: '*' ghec: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md similarity index 95% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md index 1be333af6e..2d25c0f3c9 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md @@ -7,6 +7,7 @@ redirect_from: - /articles/remembering-your-github-username-or-email - /github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md similarity index 90% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md index 40c0447783..f2ac3e2cd6 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/setting-a-backup-email-address - /github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md similarity index 98% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md index 8ba96d0130..b40af318da 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md @@ -12,6 +12,7 @@ redirect_from: - /articles/setting-your-commit-email-address - /github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md similarity index 95% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md index 30ef5eb5d3..1c4ca8bae2 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md @@ -5,6 +5,7 @@ redirect_from: - /articles/types-of-emails-github-sends - /github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends versions: fpt: '*' ghec: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md similarity index 97% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md index c0c7c3bb13..d1cde5e951 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md @@ -6,6 +6,7 @@ redirect_from: - /articles/about-your-personal-dashboard - /github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard intro: 'You can visit your personal dashboard to keep track of issues and pull requests you''re working on or following, navigate to your top repositories and team pages, stay updated on recent activities in organizations and repositories you''re subscribed to, and explore recommended repositories.' versions: fpt: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md similarity index 94% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md index f7d00a0f0a..d667d9f306 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md @@ -5,6 +5,7 @@ redirect_from: - /articles/best-practices-for-leaving-your-company - /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company versions: fpt: '*' ghec: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md similarity index 98% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md index 4913ddd731..84367ad293 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md @@ -9,6 +9,7 @@ redirect_from: - /articles/changing-your-github-username - /github/setting-up-and-managing-your-github-user-account/changing-your-github-username - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md similarity index 97% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md index 59d90651f0..aabac76580 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md @@ -6,6 +6,7 @@ redirect_from: - /articles/converting-a-user-into-an-organization - /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization intro: You can convert your personal account into an organization. This allows more granular permissions for repositories that belong to the organization. versions: fpt: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md similarity index 95% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md index f5591683eb..ba6efc34ce 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md @@ -1,11 +1,12 @@ --- -title: Deleting your user account +title: Deleting your personal account intro: 'You can delete your personal account on {% data variables.product.product_name %} at any time.' redirect_from: - /articles/deleting-a-user-account - /articles/deleting-your-user-account - /github/setting-up-and-managing-your-github-user-account/deleting-your-user-account - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md similarity index 68% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md index f6f5bb8f12..1cf21d4dcc 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md @@ -6,6 +6,7 @@ redirect_from: - /categories/user-accounts - /articles/managing-user-account-settings - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings versions: fpt: '*' ghes: '*' @@ -18,15 +19,15 @@ children: - /managing-your-theme-settings - /managing-your-tab-size-rendering-preference - /changing-your-github-username - - /merging-multiple-user-accounts + - /merging-multiple-personal-accounts - /converting-a-user-into-an-organization - - /deleting-your-user-account - - /permission-levels-for-a-user-account-repository - - /permission-levels-for-user-owned-project-boards + - /deleting-your-personal-account + - /permission-levels-for-a-personal-account-repository + - /permission-levels-for-a-project-board-owned-by-a-personal-account - /managing-accessibility-settings - /managing-the-default-branch-name-for-your-repositories - - /managing-security-and-analysis-settings-for-your-user-account - - /managing-access-to-your-user-accounts-project-boards + - /managing-security-and-analysis-settings-for-your-personal-account + - /managing-access-to-your-personal-accounts-project-boards - /integrating-jira-with-your-personal-projects - /best-practices-for-leaving-your-company - /what-does-the-available-for-hire-checkbox-do diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md similarity index 91% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md index 7a5bbd5c3d..9f6aa49e71 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md @@ -5,6 +5,7 @@ redirect_from: - /articles/integrating-jira-with-your-personal-projects - /github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects versions: ghes: '*' ghae: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md similarity index 91% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md index e41dec9831..dd9ac13ed8 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md @@ -1,5 +1,5 @@ --- -title: Managing access to your user account's project boards +title: Managing access to your personal account's project boards intro: 'As a project board owner, you can add or remove a collaborator and customize their permissions to a project board.' redirect_from: - /articles/managing-project-boards-in-your-repository-or-organization @@ -7,6 +7,7 @@ redirect_from: - /articles/managing-access-to-your-user-accounts-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md similarity index 89% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md index 77b50d2f18..e23ff42f4b 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md @@ -3,6 +3,8 @@ title: Managing accessibility settings intro: 'You can disable character key shortcuts on {% data variables.product.prodname_dotcom %} in your accessibility settings.' versions: feature: keyboard-shortcut-accessibility-setting +redirect_from: + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings --- ## About accessibility settings diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md similarity index 94% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md index b64c8c5285..7435da65f5 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md @@ -1,5 +1,5 @@ --- -title: Managing security and analysis settings for your user account +title: Managing security and analysis settings for your personal account intro: 'You can control features that secure and analyze the code in your projects on {% data variables.product.prodname_dotcom %}.' versions: fpt: '*' @@ -10,6 +10,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account shortTitle: Manage security & analysis --- ## About management of security and analysis settings diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md similarity index 100% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md similarity index 82% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md index 17103b8a96..487c25246c 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md @@ -9,6 +9,8 @@ versions: topics: - Accounts shortTitle: Managing your tab size +redirect_from: + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference --- 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. 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-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md similarity index 67% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md index 4a21753a14..f7d40079c5 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-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md @@ -11,6 +11,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings shortTitle: Manage theme settings --- @@ -18,7 +19,7 @@ For choice and flexibility in how and when you use {% data variables.product.pro You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes. +{% ifversion fpt or ghes > 3.2 or ghae or ghec %}If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% endif %}{% ifversion fpt or ghae or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes. {% endif %} @@ -31,10 +32,10 @@ You may want to use a dark theme to reduce power consumption on certain devices, 1. Click the theme you'd like to use. - If you chose a single theme, click a theme. - {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} + {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} - If you chose to follow your system settings, click a day theme and a night theme. - {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} + {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} {% ifversion fpt or ghec %} - If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %} diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md similarity index 88% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md index ebfa80dd2b..b5ad8525d3 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md @@ -1,5 +1,5 @@ --- -title: Merging multiple user accounts +title: Merging multiple personal accounts intro: 'If you have separate accounts for work and personal use, you can merge the accounts.' redirect_from: - /articles/can-i-merge-two-accounts @@ -7,6 +7,7 @@ redirect_from: - /articles/merging-multiple-user-accounts - /github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts versions: fpt: '*' ghec: '*' @@ -38,7 +39,7 @@ shortTitle: Merge multiple personal accounts 1. [Transfer any repositories](/articles/how-to-transfer-a-repository) from the account you want to delete to the account you want to keep. Issues, pull requests, and wikis are transferred as well. Verify the repositories exist on the account you want to keep. 2. [Update the remote URLs](/github/getting-started-with-github/managing-remote-repositories) in any local clones of the repositories that were moved. -3. [Delete the account](/articles/deleting-your-user-account) you no longer want to use. +3. [Delete the account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account) you no longer want to use. 4. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. For more information, see "[Why are my contributions not showing up on my profile?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)" ## Further reading diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md similarity index 97% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md index 7c611a4533..1e02205d74 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md @@ -1,10 +1,11 @@ --- -title: Permission levels for a user account repository +title: Permission levels for a personal account repository intro: 'A repository owned by a personal account has two permission levels: the repository owner and collaborators.' redirect_from: - /articles/permission-levels-for-a-user-account-repository - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository versions: fpt: '*' ghes: '*' @@ -12,7 +13,7 @@ versions: ghec: '*' topics: - Accounts -shortTitle: Permission user repositories +shortTitle: Repository permissions --- ## About permissions levels for a personal account repository @@ -43,7 +44,7 @@ The repository owner has full control of the repository. In addition to the acti | Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.1 or ghec or ghae %} | Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |{% endif %} | Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | -| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae or ghec %} | Control access to {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies | "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %} | Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | | Manage data use for a private repository | "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %} diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md similarity index 91% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md index ac912b72cb..8dd270c64d 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md @@ -1,10 +1,11 @@ --- -title: Permission levels for user-owned project boards +title: Permission levels for a project board owned by a personal account intro: 'A project board owned by a personal account has two permission levels: the project board owner and collaborators.' redirect_from: - /articles/permission-levels-for-user-owned-project-boards - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards versions: fpt: '*' ghes: '*' @@ -12,7 +13,7 @@ versions: ghec: '*' topics: - Accounts -shortTitle: Permission user project boards +shortTitle: Project board permissions --- ## Permissions overview diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md similarity index 90% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md index 49eb312823..58c62f9aca 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md @@ -5,6 +5,7 @@ redirect_from: - /articles/what-does-the-available-for-hire-checkbox-do - /github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do versions: fpt: '*' ghec: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md similarity index 95% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md index e4db7678d8..5856d842dc 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md @@ -5,6 +5,7 @@ redirect_from: - /articles/about-organization-membership - /github/setting-up-and-managing-your-github-user-account/about-organization-membership - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md similarity index 86% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md index 19a261a7af..044cf2aa3b 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md @@ -8,6 +8,7 @@ redirect_from: - /articles/accessing-an-organization - /github/setting-up-and-managing-your-github-user-account/accessing-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md similarity index 87% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md index c3329ce8e8..018b9f202b 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md @@ -4,6 +4,7 @@ intro: 'If you''re a member of an organization, you can publicize or hide your m redirect_from: - /articles/managing-your-membership-in-organizations - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md similarity index 96% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md index 93c8fbef3b..a672498d23 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md @@ -9,6 +9,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders shortTitle: Manage scheduled reminders --- ## About scheduled reminders for users diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md similarity index 90% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md index 844bc47605..3a52ffc81f 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md @@ -6,6 +6,7 @@ redirect_from: - /articles/publicizing-or-hiding-organization-membership - /github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md similarity index 91% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md index 8bf93a7f10..333584aeb3 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md @@ -6,6 +6,7 @@ redirect_from: - /articles/removing-yourself-from-an-organization - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization versions: fpt: '*' ghes: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md similarity index 92% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md index 5d3583395d..b053a1ecd1 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md @@ -7,6 +7,7 @@ redirect_from: - /articles/requesting-organization-approval-for-oauth-apps - /github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps versions: fpt: '*' ghec: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md similarity index 96% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md rename to content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md index 829b49f6ef..3b65211275 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md +++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md @@ -7,6 +7,7 @@ redirect_from: - /articles/viewing-peoples-roles-in-an-organization - /github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization versions: fpt: '*' ghes: '*' diff --git a/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md b/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md deleted file mode 100644 index e22a423999..0000000000 --- a/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Building and testing Node.js or Python -shortTitle: Build & test Node.js or Python -intro: You can create a continuous integration (CI) workflow to build and test your project. Use the language selector to show examples for your language of choice. -redirect_from: - - /actions/guides/building-and-testing-nodejs-or-python -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: tutorial -topics: - - CI ---- - - - diff --git a/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index 027cbd2b0c..48ecc1c776 100644 --- a/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -11,13 +11,11 @@ versions: ghae: '*' ghec: '*' type: tutorial -hidden: true topics: - CI - Node - JavaScript shortTitle: Build & test Node.js -hasExperimentalAlternative: true --- {% data reusables.actions.enterprise-beta %} diff --git a/content/actions/automating-builds-and-tests/building-and-testing-python.md b/content/actions/automating-builds-and-tests/building-and-testing-python.md index 471d777543..aec534eeba 100644 --- a/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -11,12 +11,10 @@ versions: ghae: '*' ghec: '*' type: tutorial -hidden: true topics: - CI - Python shortTitle: Build & test Python -hasExperimentalAlternative: true --- {% data reusables.actions.enterprise-beta %} @@ -246,7 +244,7 @@ steps: - run: pip test ``` -By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip or `Pipfile.lock` for pipenv) in the whole repository. For more information, see "[Caching packages dependencies](https://github.com/actions/setup-python#caching-packages-dependencies)" in the `setup-python` README. +By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip, `Pipfile.lock` for pipenv or `poetry.lock` for poetry) in the whole repository. For more information, see "[Caching packages dependencies](https://github.com/actions/setup-python#caching-packages-dependencies)" in the `setup-python` README. If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example above, depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip) in the `cache` action repository. diff --git a/content/actions/automating-builds-and-tests/index.md b/content/actions/automating-builds-and-tests/index.md index 7a40d05f77..9eac55efbe 100644 --- a/content/actions/automating-builds-and-tests/index.md +++ b/content/actions/automating-builds-and-tests/index.md @@ -14,13 +14,14 @@ redirect_from: - /actions/language-and-framework-guides/github-actions-for-java - /actions/language-and-framework-guides/github-actions-for-javascript-and-typescript - /actions/language-and-framework-guides/github-actions-for-python + - /actions/guides/building-and-testing-nodejs-or-python + - /actions/automating-builds-and-tests/building-and-testing-nodejs-or-python children: - /about-continuous-integration - /building-and-testing-java-with-ant - /building-and-testing-java-with-gradle - /building-and-testing-java-with-maven - /building-and-testing-net - - /building-and-testing-nodejs-or-python - /building-and-testing-nodejs - /building-and-testing-powershell - /building-and-testing-python diff --git a/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 8f2111c6b5..00b85ef504 100644 --- a/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -88,6 +88,8 @@ For example, if a workflow defined the `numOctocats` and `octocatEyeColor` input **Optional** Output parameters allow you to declare data that an action sets. Actions that run later in a workflow can use the output data set in previously run actions. For example, if you had an action that performed the addition of two inputs (x + y = z), the action could output the sum (z) for other actions to use as an input. +{% data reusables.actions.output-limitations %} + If you don't declare an output in your action metadata file, you can still set outputs and use them in a workflow. For more information on setting outputs in an action, see "[Workflow commands for {% 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 @@ -110,6 +112,8 @@ outputs: **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. +{% data reusables.actions.output-limitations %} + ### Example: Declaring outputs for composite actions {% raw %} @@ -223,7 +227,7 @@ For example, this `cleanup.js` will only run on Linux-based runners: ### `runs.steps` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Required** The steps that you plan to run in this action. These can be either `run` steps or `uses` steps. {% else %} **Required** The steps that you plan to run in this action. @@ -231,7 +235,7 @@ For example, this `cleanup.js` will only run on Linux-based runners: #### `runs.steps[*].run` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Optional** The command you want to run. This can be inline or a script in your action repository: {% else %} **Required** The command you want to run. This can be inline or a script in your action repository: @@ -261,7 +265,7 @@ For more information, see "[`github context`](/actions/reference/context-and-exp #### `runs.steps[*].shell` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Optional** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set. {% else %} **Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set. @@ -314,7 +318,7 @@ steps: **Optional** Specifies the working directory where the command is run. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} #### `runs.steps[*].uses` **Optional** Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a [published Docker container image](https://hub.docker.com/). diff --git a/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/content/actions/deployment/about-deployments/deploying-with-github-actions.md index f84c550826..281b69f1cc 100644 --- a/content/actions/deployment/about-deployments/deploying-with-github-actions.md +++ b/content/actions/deployment/about-deployments/deploying-with-github-actions.md @@ -156,7 +156,7 @@ You can also build an app that uses deployment and deployment status webhooks to ## Choosing a runner -You can run your deployment workflow on {% data variables.product.company_short %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.company_short %}-hosted runners can come from a [wide range of network addresses](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be communicate with your internal services or resources. To overcome this, you can host your own runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)." +You can run your deployment workflow on {% data variables.product.company_short %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.company_short %}-hosted runners can come from a [wide range of network addresses](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be able to communicate with your internal services or resources. To overcome this, you can host your own runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)." {% endif %} diff --git a/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md index 6c31e3a591..0920c98805 100644 --- a/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md +++ b/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md @@ -136,4 +136,4 @@ The following resources may also be useful: * The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action. * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository. -* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using VS Code with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice). +* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using {% data variables.product.prodname_vscode %} with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice). diff --git a/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index c1e1ea2515..3c82ac9aa4 100644 --- a/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -69,7 +69,7 @@ You can use any machine as a self-hosted runner as long at it meets these requir * 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. -{% ifversion fpt or ghes > 3.2 or ghec or ghae-issue-4462 %} +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## Autoscaling your self-hosted runners You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." diff --git a/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md index 5967079516..31a5c4f94c 100644 --- a/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md +++ b/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md @@ -5,7 +5,7 @@ versions: fpt: '*' ghec: '*' ghes: '>3.2' - ghae: 'issue-4462' + ghae: '*' type: overview --- diff --git a/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md index 73b089eec8..24de0031a4 100644 --- a/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -209,7 +209,8 @@ The concurrent jobs and workflow execution times in {% data variables.product.pr ### Using different languages in {% data variables.product.prodname_actions %} When working with different languages in {% data variables.product.prodname_actions %}, you can create a step in your job to set up your language dependencies. For more information about working with a particular language, see the specific guide: - - [Building and testing Node.js or Python](/actions/guides/building-and-testing-nodejs-or-python) + - [Building and testing Node.js](/actions/guides/building-and-testing-nodejs) + - [Building and testing Python](/actions/guides/building-and-testing-python) - [Building and testing PowerShell](/actions/guides/building-and-testing-powershell) - [Building and testing Java with Maven](/actions/guides/building-and-testing-java-with-maven) - [Building and testing Java with Gradle](/actions/guides/building-and-testing-java-with-gradle) diff --git a/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md index 42e77fad7e..343987cd96 100644 --- a/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md +++ b/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md @@ -37,7 +37,7 @@ To cache dependencies for a job, you can use {% data variables.product.prodname_ setup-node - pip, pipenv + pip, pipenv, poetry setup-python diff --git a/content/actions/using-workflows/events-that-trigger-workflows.md b/content/actions/using-workflows/events-that-trigger-workflows.md index c22e7fba65..d1e539534b 100644 --- a/content/actions/using-workflows/events-that-trigger-workflows.md +++ b/content/actions/using-workflows/events-that-trigger-workflows.md @@ -24,7 +24,7 @@ Workflow triggers are events that cause a workflow to run. For more information Some events have multiple activity types. For these events, you can specify which activity types will trigger a workflow run. For more information about what each activity type means, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)." Note that not all webhook events trigger workflows. -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4968 %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae %} ### `branch_protection_rule` | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` | @@ -1051,7 +1051,7 @@ on: {% endnote %} -Runs your workflow when release activity in your repository occurs. For information about the release APIs, see "[Release](/graphql/reference/objects#release)" in the GraphQL API documentation or "[Releases](/rest/reference/repos#releases)" in the REST API documentation. +Runs your workflow when release activity in your repository occurs. For information about the release APIs, see "[Release](/graphql/reference/objects#release)" in the GraphQL API documentation or "[Releases](/rest/reference/releases)" in the REST API documentation. For example, you can run a workflow when a release has been `published`. 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 3ce31cf10a..17344ed75f 100644 --- a/content/actions/using-workflows/workflow-commands-for-github-actions.md +++ b/content/actions/using-workflows/workflow-commands-for-github-actions.md @@ -102,7 +102,7 @@ The following table shows which toolkit functions are available within a workflo | Toolkit function | Equivalent workflow command | | ----------------- | ------------- | | `core.addPath` | Accessible using environment file `GITHUB_PATH` | -| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `core.notice` | `notice` |{% endif %} | `core.error` | `error` | | `core.endGroup` | `endgroup` | @@ -175,7 +175,7 @@ Write-Output "::debug::Set the Octocat variable" {% endpowershell %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ## Setting a notice message diff --git a/content/admin/code-security/index.md b/content/admin/code-security/index.md index ae196fb959..970c4013fb 100644 --- a/content/admin/code-security/index.md +++ b/content/admin/code-security/index.md @@ -1,11 +1,11 @@ --- title: Managing code security for your enterprise shortTitle: Manage code security -intro: "You can build security into your developers' workflow with features that keep secrets and vulnerabilities out of your codebase, and that maintain your software supply chain." +intro: 'You can build security into your developers'' workflow with features that keep secrets and vulnerabilities out of your codebase, and that maintain your software supply chain.' versions: ghes: '*' ghec: '*' - ghae: issue-4864 + ghae: '*' topics: - Enterprise children: diff --git a/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md index 55f6a3e42e..6aa1399182 100644 --- a/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md +++ b/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md @@ -5,7 +5,7 @@ shortTitle: About supply chain security permissions: '' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise diff --git a/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md b/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md index a8306a5513..af38e49caf 100644 --- a/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md +++ b/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md @@ -1,10 +1,10 @@ --- title: Managing supply chain security for your enterprise shortTitle: Supply chain security -intro: "You can visualize, maintain, and secure the dependencies in your developers' software supply chain." +intro: 'You can visualize, maintain, and secure the dependencies in your developers'' software supply chain.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' topics: - Enterprise children: diff --git a/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md b/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md index 953517b46c..17ea3bbd95 100644 --- a/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md +++ b/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md @@ -5,7 +5,7 @@ shortTitle: View vulnerability data permissions: 'Site administrators can view vulnerability data on {% data variables.product.product_location %}.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise diff --git a/content/admin/configuration/configuring-github-connect/about-github-connect.md b/content/admin/configuration/configuring-github-connect/about-github-connect.md index 6f1210f301..54d17c56d4 100644 --- a/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -12,7 +12,7 @@ topics: ## About {% data variables.product.prodname_github_connect %} -{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae-issue-4864 %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}. +{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}. {% data variables.product.prodname_github_connect %} does not open {% data variables.product.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)." @@ -28,7 +28,7 @@ After you configure the connection between {% data variables.product.product_loc Feature | Description | More information | ------- | ----------- | ---------------- |{% ifversion ghes %} -Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae-issue-4864 %} +Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} {% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% if server-statistics %} {% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} @@ -64,7 +64,7 @@ Additional data is transmitted if you enable individual features of {% data vari Feature | Data | Which way does the data flow? | Where is the data used? | ------- | ---- | --------- | ------ |{% ifversion ghes %} -Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %} +Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot_alerts %} | Vulnerability alerts | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %} {% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository

If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} {% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% if server-statistics %} diff --git a/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md index f2561e091c..f09cd71b31 100644 --- a/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md +++ b/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -15,7 +15,7 @@ redirect_from: permissions: 'Enterprise owners can enable {% data variables.product.prodname_dependabot %}.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise @@ -64,6 +64,8 @@ After you enable {% data variables.product.prodname_dependabot_alerts %}, you ca {% endnote %} +By default, {% data variables.product.prodname_actions %} runners used by {% data variables.product.prodname_dependabot %} need access to the internet, to download updated packages from upstream package managers. For {% data variables.product.prodname_dependabot_updates %} powered by {% data variables.product.prodname_github_connect %}, internet access provides your runners with a token that allows access to dependencies and advisories hosted on {% data variables.product.prodname_dotcom_the_website %}. + With {% data variables.product.prodname_dependabot_updates %}, {% data variables.product.company_short %} automatically creates pull requests to update dependencies in two ways. - **{% data variables.product.prodname_dependabot_version_updates %}**: Users add a {% data variables.product.prodname_dependabot %} configuration file to the repository to enable {% data variables.product.prodname_dependabot %} to create pull requests when a new version of a tracked dependency is released. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)." @@ -121,6 +123,11 @@ Before you enable {% data variables.product.prodname_dependabot_updates %}, you ![Screenshot of the dropdown menu to enable updating vulnerable dependencies](/assets/images/enterprise/site-admin-settings/dependabot-updates-button.png) -{% elsif ghes > 3.2 %} -When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Managing self-hosted runners for {% data variables.product.prodname_dependabot_updates %} on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)." +{% endif %} +{% ifversion ghes > 3.2 %} + +When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Managing self-hosted runners for {% data variables.product.prodname_dependabot_updates %} on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)." + +If you need enhanced security, we recommend configuring {% data variables.product.prodname_dependabot %} to use private registries. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_dependabot %}](/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot)." + {% endif %} 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 bbd29e52aa..3335f4cc4d 100644 --- a/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -673,6 +673,12 @@ This utility manually repackages a repository network to optimize pack storage. You can add the optional `--prune` argument to remove unreachable Git objects that aren't referenced from a branch, tag, or any other ref. This is particularly useful for immediately removing [previously expunged sensitive information](/enterprise/user/articles/remove-sensitive-data/). +{% warning %} + +**Warning**: Before using the `--prune` argument to remove unreachable Git objects, put {% data variables.product.product_location %} into maintenance mode, or ensure the repository is offline. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)." + +{% endwarning %} + ```shell ghe-repo-gc username/reponame ``` diff --git a/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md b/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md index b071b281ac..00fe89ba84 100644 --- a/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md +++ b/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md @@ -33,12 +33,13 @@ Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will ins ## Configuring a repository cache -1. During the beta, you must enable the feature flag for repository caching on your primary {% data variables.product.prodname_ghe_server %} appliance. +{% ifversion ghes = 3.3 %} +1. On your primary {% data variables.product.prodname_ghe_server %} appliance, enable the feature flag for repository caching. ``` $ ghe-config cluster.cache-enabled true ``` - +{%- endif %} 1. Set up a new {% data variables.product.prodname_ghe_server %} appliance on your desired platform. This appliance will be your repository cache. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)." {% data reusables.enterprise_installation.replica-steps %} 1. Connect to the repository cache's IP address using SSH. @@ -46,7 +47,13 @@ Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will ins ```shell $ ssh -p 122 admin@REPLICA IP ``` - +{%- ifversion ghes = 3.3 %} +1. On your cache replica, enable the feature flag for repository caching. + + ``` + $ ghe-config cluster.cache-enabled true + ``` +{%- endif %} {% data reusables.enterprise_installation.generate-replication-key-pair %} {% data reusables.enterprise_installation.add-ssh-key-to-primary %} 1. To verify the connection to the primary and enable replica mode for the repository cache, run `ghe-repl-setup` again. diff --git a/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md b/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md index 83d8dda6b5..a4a2896b60 100644 --- a/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md +++ b/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md @@ -17,7 +17,7 @@ topics: --- SNMP is a common standard for monitoring devices over a network. We strongly recommend enabling SNMP so you can monitor the health of {% data variables.product.product_location %} and know when to add more memory, storage, or processor power to the host machine. -{% data variables.product.prodname_enterprise %} has a standard SNMP installation, so you can take advantage of the [many plugins](http://www.monitoring-plugins.org/doc/man/check_snmp.html) available for Nagios or for any other monitoring system. +{% data variables.product.prodname_enterprise %} has a standard SNMP installation, so you can take advantage of the [many plugins](https://www.monitoring-plugins.org/doc/man/check_snmp.html) available for Nagios or for any other monitoring system. ## Configuring SNMP v2c @@ -72,7 +72,7 @@ If you enable SNMP v3, you can take advantage of increased user based security t #### Querying SNMP data -Both hardware and software-level information about your appliance is available with SNMP v3. Due to the lack of encryption and privacy for the `noAuthNoPriv` and `authNoPriv` security levels, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports. We include this table if you're using the `authPriv` security level. For more information, see the "[OID reference documentation](http://oidref.com/1.3.6.1.2.1.25.4)." +Both hardware and software-level information about your appliance is available with SNMP v3. Due to the lack of encryption and privacy for the `noAuthNoPriv` and `authNoPriv` security levels, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports. We include this table if you're using the `authPriv` security level. For more information, see the "[OID reference documentation](https://oidref.com/1.3.6.1.2.1.25.4)." With SNMP v2c, only hardware-level information about your appliance is available. The applications and services within {% data variables.product.prodname_enterprise %} do not have OIDs configured to report metrics. Several MIBs are available, which you can see by running `snmpwalk` on a separate workstation with SNMP support in your network: diff --git a/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index 743d214535..c70b99c442 100644 --- a/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -1,12 +1,12 @@ --- title: Getting started with self-hosted runners for your enterprise shortTitle: Self-hosted runners -intro: You can configure a runner machine for your enterprise so your developers can start automating workflows with {% data variables.product.prodname_actions %}. +intro: 'You can configure a runner machine for your enterprise so your developers can start automating workflows with {% data variables.product.prodname_actions %}.' versions: ghec: '*' ghes: '*' ghae: '*' -permissions: Enterprise owners can configure policies for {% data variables.product.prodname_actions %} and add self-hosted runners to the enterprise. +permissions: 'Enterprise owners can configure policies for {% data variables.product.prodname_actions %} and add self-hosted runners to the enterprise.' type: quick_start topics: - Actions @@ -32,7 +32,7 @@ This guide shows you how to apply a centralized management approach to self-host 1. Deploy a self-hosted runner for your enterprise 1. Create a group to manage access to the runners available to your enterprise 1. Optionally, further restrict the repositories that can use the runner -{%- ifversion ghec or ghae-issue-4462 or ghes > 3.2 %} +{%- ifversion ghec or ghae or ghes > 3.2 %} 1. Optionally, build custom tooling to automatically scale your self-hosted runners {% endif %} @@ -122,7 +122,7 @@ Optionally, organization owners can further restrict the access policy of the ru For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." -{% ifversion ghec or ghae-issue-4462 or ghes > 3.2 %} +{% ifversion ghec or ghae or ghes > 3.2 %} ## 5. Automatically scale your self-hosted runners 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 f539aeca8d..7ea2bb0b09 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 @@ -46,7 +46,7 @@ Before enabling access to all actions from {% data variables.product.prodname_do ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) 1. {% data reusables.actions.enterprise-limit-actions-use %} -{% ifversion ghes > 3.2 or ghae-issue-4815 %} +{% ifversion ghes > 3.2 or ghae %} ## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} diff --git a/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md index 1af5a98dfd..3f5f872968 100644 --- a/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md +++ b/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md @@ -33,7 +33,7 @@ If your machine has access to both systems at the same time, you can do the sync The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories. -{% ifversion ghes > 3.2 or ghae-issue-4815 %} +{% ifversion ghes > 3.2 or ghae %} {% note %} **Note:** The `actions-sync` tool is intended for use in systems where {% data variables.product.prodname_github_connect %} is not enabled. If you run the tool on a system with {% data variables.product.prodname_github_connect %} enabled, you may see the error `The repository has been retired and cannot be reused`. This indicates that a workflow has used that action directly on {% data variables.product.prodname_dotcom_the_website %} and the namespace is retired on {% data variables.product.product_location %}. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." diff --git a/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index 97e81a3546..5d4d770631 100644 --- a/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -47,7 +47,7 @@ Once {% data variables.product.prodname_github_connect %} is configured, you can 1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`. 1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}. - {% ifversion ghes > 3.2 or ghae-issue-4815 %} + {% ifversion ghes > 3.2 or ghae %} {% note %} **Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.product.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index 844392d5b5..3d666e5d33 100644 --- a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -2,7 +2,7 @@ title: Audit log events for your enterprise intro: Learn about audit log events recorded for your enterprise. shortTitle: Audit log events -permissions: Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can interact with the audit log. +permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can interact with the audit log.' miniTocMaxHeadingLevel: 4 redirect_from: - /enterprise/admin/articles/audited-actions @@ -202,7 +202,7 @@ Action | Description | `config_entry.update` | A configuration setting was edited. These events are only visible in the site admin audit log. The type of events recorded relate to:
- Enterprise settings and policies
- Organization and repository permissions and settings
- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings. {%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} ### `dependabot_alerts` category actions | Action | Description @@ -240,7 +240,7 @@ Action | Description | `dependabot_security_updates_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. {%- endif %} -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} ### `dependency_graph` category actions | Action | Description @@ -682,7 +682,7 @@ Action | Description | `org.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was removed. | `org.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was removed from an organization. | `org.remove_billing_manager` | An owner removed a billing manager from an organization. {% ifversion fpt or ghec %}For more information, see "[Removing a billing manager from your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization)"{% endif %}{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and a billing manager didn't use 2FA or disabled 2FA.{% endif %} -| `org.remove_member` | An [owner removed a member from an organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disabled 2FA{% endif %}. Also an [organization member removed themselves](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization) from an organization. +| `org.remove_member` | An [owner removed a member from an organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disabled 2FA{% endif %}. Also an [organization member removed themselves](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization) from an organization. | `org.remove_outside_collaborator` | An owner removed an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an outside collaborator didn't use 2FA or disabled 2FA{% endif %}. | `org.remove_self_hosted_runner` | A self-hosted runner was removed. For more information, see "[Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)." | `org.rename` | An organization was renamed. @@ -1145,7 +1145,7 @@ Action | Description | `repository_visibility_change.disable` | The ability for enterprise members to update a repository's visibility was disabled. Members are unable to change repository visibilities in an organization, or all organizations in an enterprise. | `repository_visibility_change.enable` | The ability for enterprise members to update a repository's visibility was enabled. Members are able to change repository visibilities in an organization, or all organizations in an enterprise. -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} ### `repository_vulnerability_alert` category actions | Action | Description diff --git a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md index 5b731dd40e..97df83b1e0 100644 --- a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md +++ b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md @@ -66,7 +66,7 @@ You can choose to disable {% data variables.product.prodname_actions %} for all 1. Under "Policies", select {% data reusables.actions.policy-label-for-select-actions-workflows %} and add your required actions{% if actions-workflow-policy %} and reusable workflows{% endif %} to the list. {% if actions-workflow-policy %} ![Add actions and reusable workflows to the allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list-with-workflows.png) - {%- elsif ghes or ghae-issue-5094 %} + {%- elsif ghes or ghae %} ![Add actions to the allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) {%- elsif ghae %} ![Add actions to the allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) diff --git a/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md index a725faf1c7..c3beae0da5 100644 --- a/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md +++ b/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md @@ -68,7 +68,15 @@ You can view more information about the person's access to your enterprise, such {% ifversion ghec %} ## Viewing pending invitations -You can see all the pending invitations to become administrators, members, or outside collaborators in your enterprise. You can filter the list in useful ways, such as by organization. You can find a specific person by searching for their username or display name. +You can see all the pending invitations to become members, administrators, or outside collaborators in your enterprise. You can filter the list in useful ways, such as by organization. You can find a specific person by searching for their username or display name. + +In the list of pending members, for any individual account, you can cancel all invitations to join organizations owned by your enterprise. This does not cancel any invitations for that same person to become an enterprise administrator or outside collaborator. + +{% note %} + +**Note:** If an invitation was provisioned via SCIM, you must cancel the invitation via your identity provider (IdP) instead of on {% data variables.product.prodname_dotcom %}. + +{% endnote %} If you use {% data variables.product.prodname_vss_ghe %}, the list of pending invitations includes all {% data variables.product.prodname_vs %} subscribers that haven't joined any of your organizations on {% data variables.product.prodname_dotcom %}, even if the subscriber does not have a pending invitation to join an organization. For more information about how to get {% data variables.product.prodname_vs %} subscribers access to {% data variables.product.prodname_enterprise %}, see "[Setting up {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)." @@ -77,7 +85,9 @@ If you use {% data variables.product.prodname_vss_ghe %}, the list of pending in 1. Under "People", click **Pending invitations**. ![Screenshot of the "Pending invitations" tab in the sidebar](/assets/images/help/enterprises/pending-invitations-tab.png) +1. Optionally, to cancel all invitations for an account to join organizations owned by your enterprise, to the right of the account, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Cancel invitation**. + ![Screenshot of the "Cancel invitation" button](/assets/images/help/enterprises/cancel-enterprise-member-invitation.png) 1. Optionally, to view pending invitations for enterprise administrators or outside collaborators, under "Pending members", click **Administrators** or **Outside collaborators**. ![Screenshot of the "Members", "Administrators", and "Outside collaborators" tabs](/assets/images/help/enterprises/pending-invitations-type-tabs.png) diff --git a/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index b0c87d6303..113e3394b5 100644 --- a/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -16,7 +16,7 @@ shortTitle: Authentication to GitHub --- ## About authentication to {% data variables.product.prodname_dotcom %} -To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. +To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. You can access your resources in {% data variables.product.product_name %} in a variety of ways: in the browser, via {% data variables.product.prodname_desktop %} or another desktop application, with the API, or via the command line. Each way of accessing {% data variables.product.product_name %} supports different modes of authentication. {%- ifversion not fpt %} @@ -27,35 +27,47 @@ You can access your resources in {% data variables.product.product_name %} in a ## Authenticating in your browser -You can authenticate to {% data variables.product.product_name %} in your browser {% ifversion ghae %}using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."{% else %}in different ways. +{% ifversion ghae %} + +You can authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)." + +{% else %} {% ifversion fpt or ghec %} -- If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} - If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also be required to enable two-factor authentication. +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} + +If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also use two-factor authentication and SAML single sign-on, which can be required by organization and enterprise owners. + +{% else %} + +You can authenticate to {% data variables.product.product_name %} in your browser in a number of ways. + {% endif %} - **Username and password only** - You'll create a password when you create your account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)."{% ifversion fpt or ghec %} - If you have not enabled 2FA, {% data variables.product.product_name %} will ask for additional verification when you first sign in from an unrecognized device, such as a new browser profile, a browser where the cookies have been deleted, or a new computer. - - After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the GitHub Mobile application installed, you'll receive a notification there instead.{% endif %} + + After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the {% data variables.product.prodname_mobile %} application installed, you'll receive a notification there instead. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."{% endif %} - **Two-factor authentication (2FA)** (recommended) - If you enable 2FA, after you successfully enter your username and password, we'll also prompt you to provide a code that's generated by a time-based one time password (TOTP) application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)." - - In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% endif %}{% ifversion ghes %} -- **Identity provider (IdP) authentication** - - Your site administrator may configure {% data variables.product.product_location %} to use authentication with an IdP instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)." + - In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% ifversion ghes %} +- **External authentication** + - Your site administrator may configure {% data variables.product.product_location %} to use external authentication instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)."{% endif %}{% ifversion fpt or ghec %} +- **SAML single sign-on** + - Before you can access resources owned by an organization or enterprise account that uses SAML single sign-on, you may need to also authenticate through an IdP. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} + {% endif %} ## Authenticating with {% data variables.product.prodname_desktop %} - You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." ## Authenticating with the API You can authenticate with the API in different ways. -- **Personal access tokens** +- **Personal access tokens** - In limited situations, such as testing, you can use a personal access token to access the API. Using a personal access token enables you to revoke access at any time. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." - **Web application flow** - For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)." @@ -68,11 +80,11 @@ You can access repositories on {% data variables.product.product_name %} from th ### HTTPS -You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. +You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a personal access token or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). -If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a personal access token. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git). +If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a personal access token. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them with a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git). ### SSH diff --git a/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index cf241ab5cd..b823047c68 100644 --- a/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -44,7 +44,7 @@ A token with no assigned scopes can only access public information. To use your {% data reusables.user-settings.personal_access_tokens %} {% data reusables.user-settings.generate_new_token %} 5. Give your token a descriptive name. - ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %} + ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae or ghec %} 6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker. ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %} 7. Select the scopes, or permissions, you'd like to grant this token. To use your token to access repositories from the command line, select **repo**. @@ -82,5 +82,5 @@ Instead of manually entering your PAT for every HTTPS Git operation, you can cac ## Further reading -- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} - "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} diff --git a/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md index 385e8c165a..d706fb6c7b 100644 --- a/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md +++ b/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md @@ -24,9 +24,9 @@ You can remove the file from the latest commit with `git rm`. For information on {% warning %} -This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. However, it's important to note that those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}. +**Warning**: This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. However, those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}. -**Warning: Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! If you committed a key, generate a new one. Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. Consider these limitations in your decision to rewrite your repository's history. +**Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! If you committed a key, generate a new one. Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. Consider these limitations in your decision to rewrite your repository's history. {% endwarning %} @@ -151,7 +151,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil After using either the BFG tool or `git filter-repo` to remove the sensitive data and pushing your changes to {% data variables.product.product_name %}, you must take a few more steps to fully remove the data from {% data variables.product.product_name %}. -1. Contact {% data variables.contact.contact_support %}, asking them to remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed. +1. Contact {% data variables.contact.contact_support %}, asking them to remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed.{% ifversion ghes %} For more information about how site administrators can remove unreachable Git objects, see "[Command line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repo-gc)."{% endif %} 2. Tell your collaborators to [rebase](https://git-scm.com/book/en/Git-Branching-Rebasing), *not* merge, any branches they created off of your old (tainted) repository history. One merge commit could reintroduce some or all of the tainted history that you just went to the trouble of purging. 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 f8b7483070..b0dbde83b1 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 @@ -28,15 +28,11 @@ The security log lists all actions performed within the last 90 days. ![Security log tab](/assets/images/help/settings/audit-log-tab.png) {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} ## Searching your security log {% data reusables.audit_log.audit-log-search %} ### Search based on the action performed -{% else %} -## Understanding events in your security log -{% endif %} The events listed in your security log are triggered by your actions. Actions are grouped into the following categories: @@ -112,7 +108,7 @@ An overview of some of the most common actions that are recorded as events in th | Action | Description |------------------|------------------- | `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps). -| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %} +| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %} {% ifversion fpt or ghec %} @@ -187,16 +183,16 @@ An overview of some of the most common actions that are recorded as events in th | `sponsor_sponsorship_payment_complete` | Triggered after you sponsor an account and your payment has been processed (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)") | `sponsor_sponsorship_tier_change` | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") -| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") +| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | `sponsored_developer_disable` | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled | `sponsored_developer_redraft` | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state | `sponsored_developer_profile_update` | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)") -| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") +| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)") | `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)") -| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") -| `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") +| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") +| `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") {% endif %} {% ifversion fpt or ghec %} diff --git a/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md index 6c5ecac94e..b184bab5ab 100644 --- a/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md +++ b/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md @@ -14,7 +14,7 @@ redirect_from: - /github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation --- -When a token {% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}has expired or {% endif %} has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token. +When a token {% ifversion fpt or ghae or ghes > 3.2 or ghec %}has expired or {% endif %} has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token. This article explains the possible reasons your {% data variables.product.product_name %} token might be revoked or expire. @@ -24,7 +24,7 @@ This article explains the possible reasons your {% data variables.product.produc {% endnote %} -{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## Token revoked after reaching its expiration date When you create a personal access token, we recommend that you set an expiration for your token. Upon reaching your token's expiration date, the token is automatically revoked. For more information, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." 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 e1fbc4ab74..e7d54494fe 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 @@ -58,7 +58,7 @@ See "[Reviewing your authorized integrations](/articles/reviewing-your-authorize {% ifversion not ghae %} -If you have reset your account password and would also like to trigger a sign-out from the GitHub Mobile app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. For additional information, see "[Reviewing your authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)." +If you have reset your account password and would also like to trigger a sign-out from the {% data variables.product.prodname_mobile %} app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. This will sign out all instances of the {% data variables.product.prodname_mobile %} app associated with your account. For additional information, see "[Reviewing your authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)." {% endif %} 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 56794f90c1..5d22caf825 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 @@ -47,7 +47,7 @@ Jobs that run on Windows and macOS runners that {% data variables.product.prodna The storage used by a repository is the total storage used by {% data variables.product.prodname_actions %} artifacts and {% data variables.product.prodname_registry %}. Your storage cost is the total usage for all repositories owned by your account. For more information about pricing for {% data variables.product.prodname_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)." - If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.25 USD per GB of storage per month and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} rounds the minutes each job uses up to the nearest minute. + If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} rounds the minutes each job uses up to the nearest minute. {% note %} diff --git a/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md index d9247cd964..1bbe77f653 100644 --- a/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md +++ b/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md @@ -49,9 +49,9 @@ All data transferred out, when triggered by {% data variables.product.prodname_a Storage usage is shared with build artifacts produced by {% data variables.product.prodname_actions %} for repositories owned by your account. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." -{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.25 USD per GB of storage and $0.50 USD per GB of data transfer. +{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and $0.50 USD per GB of data transfer. -For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.25 USD per GB or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD. +For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.008 USD per GB per day or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD. {% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %} diff --git a/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md index 15c126e263..49cf14c22f 100644 --- a/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md +++ b/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md @@ -59,7 +59,7 @@ One person may be able to complete the tasks because the person has all of the r **Tips**: - While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_location %} matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license. - - If the subscriber accepts the invitation to the organization with an existing personal account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their personal account on {% data variables.product.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)." + - If the subscriber accepts the invitation to the organization with an existing personal account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their personal account on {% data variables.product.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)." - If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository. {% endtip %} 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 cccde8bdec..a462055e5a 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 @@ -73,7 +73,7 @@ By default, the {% data variables.product.prodname_codeql_workflow %} uses the ` If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Additionally, when an `on:push` scan returns results that can be mapped to an open pull request, these alerts will automatically appear on the pull request in the same places as other pull request alerts. The alerts are identified by comparing the existing analysis of the head of the branch to the analysis for the target branch. For more information on {% data variables.product.prodname_code_scanning %} alerts in pull requests, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." {% endif %} @@ -85,7 +85,7 @@ For more information about the `pull_request` event, see "[Events that trigger w If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." {% endif %} 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 7649b34387..990c6e03c7 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 @@ -155,9 +155,9 @@ The names of the {% data variables.product.prodname_code_scanning %} analysis ch ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png) -When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. +When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. -{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png) The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request. @@ -167,13 +167,13 @@ For example, in the screenshot above, {% data variables.product.prodname_code_sc ![Missing analysis for commit message](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png) {% endif %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ### Reasons for the "Analysis not found" message {% else %} ### Reasons for the "Missing analysis" message {% endif %} -After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. +After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include: diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index 0facaadb22..66507b8e68 100644 --- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -28,7 +28,7 @@ topics: ## About {% data variables.product.prodname_code_scanning %} results on pull requests In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} In repositories where {% data variables.product.prodname_code_scanning %} is configured to scan each time code is pushed, {% data variables.product.prodname_code_scanning %} will also map the results to any open pull requests and add the alerts as annotations in the same places as other pull request checks. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." {% endif %} @@ -42,7 +42,7 @@ There are many options for configuring {% data variables.product.prodname_code_s For all configurations of {% data variables.product.prodname_code_scanning %}, the check that contains the results of {% data variables.product.prodname_code_scanning %} is: **{% data variables.product.prodname_code_scanning_capc %} results**. The results for each analysis tool used are shown separately. Any new alerts caused by changes in the pull request are shown as annotations. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)." +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)." ![{% data variables.product.prodname_code_scanning_capc %} results check on a pull request](/assets/images/help/repository/code-scanning-results-check.png) {% endif %} diff --git a/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index 233364f4bf..b73490579e 100644 --- a/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -10,7 +10,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: diff --git a/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md b/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md index d3b617250a..4ea696faf6 100644 --- a/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md +++ b/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md @@ -5,7 +5,7 @@ shortTitle: Configure Dependabot alerts versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -107,4 +107,4 @@ By default, we notify people with admin permissions in the affected repositories ![Screenshot of "Enable Dependabot alerts" modal with button to disable or enable feature emphasized](/assets/images/help/dependabot/dependabot-alerts-enable-dependabot-alerts-organizations.png) {% endif %}{% endif %}{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot_alerts %} for your organization can be enabled or disabled by your enterprise owner. For more information, see "[About Dependabot for GitHub Enterprise Server](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." -{% endif %} \ No newline at end of file +{% endif %} diff --git a/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md b/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md index 1ca05f1e50..05fba35b45 100644 --- a/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md +++ b/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -30,7 +30,7 @@ When {% data variables.product.prodname_dependabot %} detects vulnerable depende {% ifversion fpt or ghec %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether the detection of vulnerable dependencies will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)." {% endif %} -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} By default, if your enterprise owner has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email. Enterprise owners can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." diff --git a/content/code-security/dependabot/dependabot-alerts/index.md b/content/code-security/dependabot/dependabot-alerts/index.md index 02065dbb14..72bb2a24f7 100644 --- a/content/code-security/dependabot/dependabot-alerts/index.md +++ b/content/code-security/dependabot/dependabot-alerts/index.md @@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md index e1c781a494..f33383fb20 100644 --- a/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md +++ b/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md @@ -6,12 +6,12 @@ redirect_from: - /github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository - /code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository -permissions: Repository administrators and organization owners can view and update dependencies, as well as users and teams with explicit access. +permissions: 'Repository administrators and organization owners can view and update dependencies, as well as users and teams with explicit access.' shortTitle: View Dependabot alerts versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -55,7 +55,7 @@ For supported languages, {% data variables.product.prodname_dependabot %} automa {% note %} -**Note:** During the beta release, this feature is available only for new Python advisories created *after* April 14, 2022, and for a subset of historical Python advisories. GitHub is working to backfill data across additional historical Python advisories, which are added on a rolling basis. Vulnerable calls are highlighted only on the {% data variables.product.prodname_dependabot_alerts %} pages. +**Note:** During the beta release, this feature is available only for new Python advisories created *after* April 14, 2022, and for a subset of historical Python advisories. {% data variables.product.prodname_dotcom %} is working to backfill data across additional historical Python advisories, which are added on a rolling basis. Vulnerable calls are highlighted only on the {% data variables.product.prodname_dependabot_alerts %} pages. {% endnote %} @@ -65,7 +65,7 @@ You can filter the view to show only alerts where {% data variables.product.prod For alerts where vulnerable calls are detected, the alert details page shows additional information: -- A code block showing where the function is used or, where there are multiple calls, the first call to the function. +- One or more code blocks showing where the function is used. - An annotation listing the function itself, with a link to the line where the function is called. ![Screenshot showing the alert details page for an alert with a "Vulnerable call" label](/assets/images/help/repository/review-calls-to-vulnerable-functions.png) diff --git a/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md index a79c611287..fc16885db1 100644 --- a/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md +++ b/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md @@ -61,7 +61,7 @@ If security updates are not enabled for your repository and you don't know why, You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below). -You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your personal account or organization. For more information, see "[Managing security and analysis settings for your personal 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)." +You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your personal account or organization. For more information, see "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data variables.product.prodname_dependabot_security_updates %} require specific repository settings. For more information, see "[Supported repositories](#supported-repositories)." diff --git a/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md index 145b38921f..fb9da56a95 100644 --- a/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md +++ b/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md @@ -30,7 +30,7 @@ shortTitle: Dependabot version updates {% data variables.product.prodname_dependabot %} takes the effort out of maintaining your dependencies. You can use it to ensure that your repository automatically keeps up with the latest releases of the packages and applications it depends on. -You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_configuration file into your repository. The configuration file specifies the location of the manifest, or of other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary. +You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a `dependabot.yml` configuration file into your repository. The configuration file specifies the location of the manifest, or of other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary. When {% data variables.product.prodname_dependabot %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to replace the outdated dependency with the new version directly. You check that your tests pass, review the changelog and release notes included in the pull request summary, and then merge it. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." diff --git a/content/code-security/dependabot/index.md b/content/code-security/dependabot/index.md index cb1f4984f9..2cfeef9d87 100644 --- a/content/code-security/dependabot/index.md +++ b/content/code-security/dependabot/index.md @@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index 722d2e48bd..86519f787b 100644 --- a/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -36,7 +36,7 @@ topics: * {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new vulnerability record is added, it scans all existing repositories and generates an alert for each vulnerable repository. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." * {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)." - {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% ifversion ghes or ghae-issue-4864 %} and synchronized to {% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)." + {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% ifversion ghes or ghae %} and synchronized to {% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)." ## Do {% data variables.product.prodname_dependabot_alerts %} only relate to vulnerable dependencies in manifests and lockfiles? diff --git a/content/code-security/getting-started/github-security-features.md b/content/code-security/getting-started/github-security-features.md index 21c6e0e3f7..c32115569b 100644 --- a/content/code-security/getting-started/github-security-features.md +++ b/content/code-security/getting-started/github-security-features.md @@ -20,7 +20,7 @@ topics: The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Available for all repositories {% endif %} ### Security policy @@ -41,7 +41,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% endif %} -{% ifversion ghes < 3.3 or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae %} ### {% data variables.product.prodname_dependabot_alerts %} {% data reusables.dependabot.dependabot-alerts-beta %} @@ -55,7 +55,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ### Dependency graph The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository. @@ -100,13 +100,13 @@ Available only with a license for {% data variables.product.prodname_GH_advanced Automatically detect tokens or credentials that have been checked into a repository. You can view alerts for any secrets that {% data variables.product.company_short %} finds in your code, so that you know which tokens or credentials to treat as compromised. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ### Dependency review 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 or ghae-issue-4554 %} +{% ifversion ghec or ghes > 3.1 or ghae %} ### Security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams {% ifversion ghec %} diff --git a/content/code-security/getting-started/securing-your-organization.md b/content/code-security/getting-started/securing-your-organization.md index ebb6dbe2c8..dd6785e84c 100644 --- a/content/code-security/getting-started/securing-your-organization.md +++ b/content/code-security/getting-started/securing-your-organization.md @@ -33,7 +33,7 @@ You can create a default security policy that will display in any of your organi {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph {% 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. @@ -51,7 +51,7 @@ You can create a default security policy that will display in any of your organi For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Managing dependency review @@ -138,7 +138,7 @@ 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 fpt or ghes > 3.1 or ghec or ghae-issue-4554 %}{% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae-issue-4554 %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %} +{% ifversion fpt or ghes > 3.1 or ghec or ghae %}{% ifversion ghes > 3.1 or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %} {% ifversion ghec %} diff --git a/content/code-security/getting-started/securing-your-repository.md b/content/code-security/getting-started/securing-your-repository.md index 6ee9dc430b..8b9288bdea 100644 --- a/content/code-security/getting-started/securing-your-repository.md +++ b/content/code-security/getting-started/securing-your-repository.md @@ -44,7 +44,7 @@ From the main page of your repository, click **{% octicon "gear" aria-label="The For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)." -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing the dependency graph {% ifversion fpt or ghec %} @@ -61,7 +61,7 @@ For more information, see "[Exploring the dependencies of a repository](/code-se {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} {% data variables.product.prodname_dependabot_alerts %} are generated when {% data variables.product.prodname_dotcom %} identifies a dependency in the dependency graph with a vulnerability. {% ifversion fpt or ghec %}You can enable {% data variables.product.prodname_dependabot_alerts %} for any repository.{% endif %} @@ -75,11 +75,11 @@ For more information, see "[Exploring the dependencies of a repository](/code-se {% data reusables.dependabot.dependabot-alerts-beta %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[Managing security and analysis settings for your personal account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account){% endif %}." +For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account){% endif %}." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Managing dependency review Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." diff --git a/content/code-security/security-overview/about-the-security-overview.md b/content/code-security/security-overview/about-the-security-overview.md index 468aed1cfe..0a965e2e3e 100644 --- a/content/code-security/security-overview/about-the-security-overview.md +++ b/content/code-security/security-overview/about-the-security-overview.md @@ -1,13 +1,13 @@ --- title: About the security overview intro: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in one place: the Security Overview page.' -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' redirect_from: - /code-security/security-overview/exploring-security-alerts versions: fpt: '*' - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' type: how_to @@ -22,7 +22,7 @@ topics: shortTitle: About security overview --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} @@ -69,7 +69,7 @@ At the organization-level, the security overview displays aggregate and reposito {% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} ### About the enterprise-level security overview -At the enterprise-level, the security overview displays aggregate and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts or view all {% data variables.product.prodname_secret_scanning %} alerts from across your enterprise. +At the enterprise-level, the security overview displays aggregate and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise. Organization owners and security managers for organizations in your enterprise also have limited access to the enterprise-level security overview. They can only view repositories and alerts for the organizations that they have full access to. @@ -80,4 +80,4 @@ At the enterprise-level, the security overview displays aggregate and repository ### About the team-level security overview At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. 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)." -{% endif %} \ No newline at end of file +{% endif %} diff --git a/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index e4887a0120..81970e0a57 100644 --- a/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -1,10 +1,10 @@ --- title: Filtering alerts in the security overview intro: Use filters to view specific categories of alerts -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' versions: - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' type: how_to @@ -17,7 +17,7 @@ topics: shortTitle: Filtering alerts --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} diff --git a/content/code-security/security-overview/index.md b/content/code-security/security-overview/index.md index e7ab1f75e5..81a283c58c 100644 --- a/content/code-security/security-overview/index.md +++ b/content/code-security/security-overview/index.md @@ -5,7 +5,7 @@ intro: 'View, sort, and filter the security alerts from across your organization product: '{% data reusables.gated-features.security-center %}' versions: fpt: '*' - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' topics: diff --git a/content/code-security/security-overview/viewing-the-security-overview.md b/content/code-security/security-overview/viewing-the-security-overview.md index 8239d2dffc..2522b9d9da 100644 --- a/content/code-security/security-overview/viewing-the-security-overview.md +++ b/content/code-security/security-overview/viewing-the-security-overview.md @@ -1,7 +1,7 @@ --- title: Viewing the security overview intro: Navigate to the different views available in the security overview -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' versions: ghae: issue-5503 @@ -17,7 +17,7 @@ topics: shortTitle: View the security overview --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} @@ -29,7 +29,7 @@ shortTitle: View the security overview ![Show more button](/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. +{% data reusables.organizations.security-overview-feature-specific-page %} ![Screenshot of the code scanning-specific page](/assets/images/help/organizations/security-overview-code-scanning-alerts.png) ## Viewing alerts across your organization @@ -46,6 +46,9 @@ shortTitle: View the security overview {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} 1. In the left sidebar, click {% octicon "shield" aria-label="The shield icon" %} **Code Security**. +{% if security-overview-feature-specific-alert-page %} +{% data reusables.organizations.security-overview-feature-specific-page %} +{% endif %} {% endif %} ## Viewing alerts for a repository diff --git a/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md b/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md index 21ac3542f2..08102cf1d6 100644 --- a/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md +++ b/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md @@ -19,6 +19,8 @@ topics: At its core, end-to-end software supply chain security is about making sure the code you distribute hasn't been tampered with. Previously, attackers focused on targeting dependencies you use, for example libraries and frameworks. Attackers have now expanded their focus to include targeting user accounts and build processes, and so those systems must be defended as well. +For information about features in {% data variables.product.prodname_dotcom %} that can help you secure dependencies, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." + ## About these guides This series of guides explains how to think about securing your end-to-end supply chain: personal account, code, and build processes. Each guide explains the risk to that area, and introduces the {% data variables.product.product_name %} features that can help you address that risk. diff --git a/content/code-security/supply-chain-security/index.md b/content/code-security/supply-chain-security/index.md index 920263b971..96123e1f9b 100644 --- a/content/code-security/supply-chain-security/index.md +++ b/content/code-security/supply-chain-security/index.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md index 98a9baa2ee..3a74065bb6 100644 --- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md +++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md @@ -6,7 +6,7 @@ shortTitle: Dependency review versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -37,6 +37,8 @@ For more information about configuring dependency review, see "[Configuring depe Dependency review supports the same languages and package management ecosystems as the dependency graph. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." +For more information on supply chain features available on {% data variables.product.product_name %}, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." + {% ifversion ghec or ghes %} ## Enabling dependency review diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md index 0518b8bf9f..83672fd238 100644 --- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md +++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -54,6 +54,10 @@ Other supply chain features on {% data variables.product.prodname_dotcom %} rely {% data variables.product.prodname_dependabot %} cross-references dependency data provided by the dependency graph with the list of known vulnerabilities published in the {% data variables.product.prodname_advisory_database %}, scans your dependencies and generates {% data variables.product.prodname_dependabot_alerts %} when a potential vulnerability is detected. {% endif %} +{% ifversion fpt or ghec or ghes %} +For best practice guides on end-to-end supply chain security including the protection of personal accounts, code, and build processes, see "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)." +{% endif %} + ## Feature overview ### What is the dependency graph @@ -129,7 +133,7 @@ Public repositories: - **Dependency graph**—enabled by default and cannot be disabled. - **Dependency review**—enabled by default and cannot be disabled. - **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. {% data variables.product.prodname_dotcom %} detects vulnerable dependencies and displays information in 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 %}. - You can also enable or disable 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](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/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-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." + You can also enable or disable 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](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." Private repositories: - **Dependency graph**—not enabled by default. The feature can be enabled by repository administrators. For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)." @@ -139,7 +143,7 @@ Private repositories: - **Dependency review**—available in private repositories owned by organizations provided you have a license for {% data variables.product.prodname_GH_advanced_security %} and the dependency graph enabled. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" and "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)." {% endif %} - **{% data variables.product.prodname_dependabot_alerts %}**—not enabled 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. - You can also enable or disable 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](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/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-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." + You can also enable or disable 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](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." Any repository type: - **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)." 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 409595d281..f0b9ba9358 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 @@ -7,7 +7,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -44,6 +44,8 @@ The dependency graph includes all the dependencies of a repository that are deta The dependency graph identifies indirect dependencies{% ifversion fpt or ghec %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. +For more information on how {% data variables.product.product_name %} helps you understand the dependencies in your environment, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." + {% ifversion fpt or ghec %} ## Dependents included diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md index 935e568789..bf8f34c92f 100644 --- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md +++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md @@ -1,11 +1,11 @@ --- title: Configuring dependency review -intro: 'You can use dependency review to catch vulnerabilities before they are added to your project.' +intro: You can use dependency review to catch vulnerabilities before they are added to your project. shortTitle: Configure dependency review versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md index d8ec9ca435..8d51d53e94 100644 --- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md +++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md @@ -2,11 +2,11 @@ title: Configuring the dependency graph intro: You can allow users to identify their projects' dependencies by enabling the dependency graph. redirect_from: - - /code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph + - /code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index a857d0a12b..9a41314832 100644 --- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -12,7 +12,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md index 1710ee55da..20737355d4 100644 --- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md +++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md @@ -3,7 +3,7 @@ title: Understanding your software supply chain versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependency graph diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md index 6de1b7a25d..0fe9cbaf0e 100644 --- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md +++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md @@ -5,7 +5,7 @@ shortTitle: Troubleshoot dependency graph versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -59,4 +59,4 @@ Yes, the dependency graph has two categories of limits: - "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)" - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" - "[Troubleshooting the detection of vulnerable dependencies](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %} -- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} \ No newline at end of file +- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md b/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md index 71bac5b61d..5cd930c146 100644 --- a/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md +++ b/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md @@ -42,7 +42,7 @@ While this option does not configure a development environment for you, it will ## Option 4: Use Remote-Containers and Docker for a local containerized environment -If your repository has a `devcontainer.json`, consider using the [Remote-Containers extension](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) in Visual Studio Code to build and attach to a local development container for your repository. The setup time for this option will vary depending on your local specifications and the complexity of your dev container setup. +If your repository has a `devcontainer.json`, consider using the [Remote-Containers extension](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) in {% data variables.product.prodname_vscode %} to build and attach to a local development container for your repository. The setup time for this option will vary depending on your local specifications and the complexity of your dev container setup. {% note %} diff --git a/content/codespaces/codespaces-reference/security-in-codespaces.md b/content/codespaces/codespaces-reference/security-in-codespaces.md index 059d44a005..7ddc954391 100644 --- a/content/codespaces/codespaces-reference/security-in-codespaces.md +++ b/content/codespaces/codespaces-reference/security-in-codespaces.md @@ -34,7 +34,7 @@ Each codespace has its own isolated virtual network. We use firewalls to block i ### Authentication -You can connect to a codespace using a web browser or from Visual Studio Code. If you connect from Visual Studio Code, you are prompted to authenticate with {% data variables.product.product_name %}. +You can connect to a codespace using a web browser or from {% data variables.product.prodname_vscode %}. If you connect from {% data variables.product.prodname_vscode_shortname %}, you are prompted to authenticate with {% data variables.product.product_name %}. Every time a codespace is created or restarted, it's assigned a new {% data variables.product.company_short %} token with an automatic expiry period. This period allows you to work in the codespace without needing to reauthenticate during a typical working day, but reduces the chance that you will leave a connection open when you stop using the codespace. @@ -109,4 +109,4 @@ Certain development features can potentially add risk to your environment. For e #### Using extensions -Any additional {% data variables.product.prodname_vscode %} extensions that you've installed can potentially introduce more risk. To help mitigate this risk, ensure that the you only install trusted extensions, and that they are always kept up to date. +Any additional {% data variables.product.prodname_vscode_shortname %} extensions that you've installed can potentially introduce more risk. To help mitigate this risk, ensure that the you only install trusted extensions, and that they are always kept up to date. diff --git a/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md b/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md index 0ff3d6d8cd..a6a0a614df 100644 --- a/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md +++ b/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md @@ -17,7 +17,7 @@ redirect_from: ## Using {% data variables.product.prodname_copilot %} -[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), an AI pair programmer, can be used in any codespace. To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). +[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), an AI pair programmer, can be used in any codespace. To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). To include {% data variables.product.prodname_copilot_short %}, or other extensions, in all of your codespaces, enable Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." Additionally, to include {% data variables.product.prodname_copilot_short %} in a given project for all users, you can specify `GitHub.copilot` as an extension in your `devcontainer.json` file. For information about configuring a `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)." diff --git a/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md index 1abf739940..acb0cad204 100644 --- a/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md +++ b/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md @@ -15,13 +15,13 @@ redirect_from: - /codespaces/codespaces-reference/using-the-command-palette-in-codespaces --- -## About the {% data variables.product.prodname_vscode %} Command Palette +## About the {% data variables.product.prodname_vscode_command_palette %} -The Command Palette is one of the focal features of {% data variables.product.prodname_vscode %} and is available for you to use in Codespaces. The {% data variables.product.prodname_vscode_command_palette %} allows you to access many commands for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode %}. For more information on using the {% data variables.product.prodname_vscode_command_palette %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the Visual Studio Code documentation. +The Command Palette is one of the focal features of {% data variables.product.prodname_vscode %} and is available for you to use in Codespaces. The {% data variables.product.prodname_vscode_command_palette %} allows you to access many commands for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information on using the {% data variables.product.prodname_vscode_command_palette_shortname %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the {% data variables.product.prodname_vscode_shortname %} documentation. -## Accessing the {% data variables.product.prodname_vscode_command_palette %} +## Accessing the {% data variables.product.prodname_vscode_command_palette_shortname %} -You can access the {% data variables.product.prodname_vscode_command_palette %} in a number of ways. +You can access the {% data variables.product.prodname_vscode_command_palette_shortname %} in a number of ways. - Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux). @@ -33,7 +33,7 @@ You can access the {% data variables.product.prodname_vscode_command_palette %} ## Commands for {% data variables.product.prodname_github_codespaces %} -To see all commands related to {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "Codespaces". +To see all commands related to {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "Codespaces". ![A list of all commands that relate to Codespaces](/assets/images/help/codespaces/codespaces-command-palette.png) @@ -41,13 +41,13 @@ To see all commands related to {% data variables.product.prodname_github_codespa If you add a new secret or change the machine type, you'll have to stop and restart the codespace for it to apply your changes. -To suspend or stop your codespace's container, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "stop". Select **Codespaces: Stop Current Codespace**. +To suspend or stop your codespace's container, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "stop". Select **Codespaces: Stop Current Codespace**. ![Command to stop a codespace](/assets/images/help/codespaces/codespaces-stop.png) ### Adding a dev container from a template -To add a dev container from a template, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "dev container". Select **Codespaces: Add Development Container Configuration Files...** +To add a dev container from a template, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "dev container". Select **Codespaces: Add Development Container Configuration Files...** ![Command to add a dev container](/assets/images/help/codespaces/add-prebuilt-container-command.png) @@ -55,14 +55,14 @@ To add a dev container from a template, [access the {% data variables.product.pr If you add a dev container or edit any of the configuration files (`devcontainer.json` and `Dockerfile`), you'll have to rebuild your codespace for it to apply your changes. -To rebuild your container, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "rebuild". Select **Codespaces: Rebuild Container**. +To rebuild your container, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "rebuild". Select **Codespaces: Rebuild Container**. ![Command to rebuild a codespace](/assets/images/help/codespaces/codespaces-rebuild.png) ### Codespaces logs -You can use the {% data variables.product.prodname_vscode_command_palette %} to access the codespace creation logs, or you can use it export all logs. +You can use the {% data variables.product.prodname_vscode_command_palette_shortname %} to access the codespace creation logs, or you can use it export all logs. -To retrieve the logs for Codespaces, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "log". Select **Codespaces: Export Logs** to export all logs related to Codespaces or select **Codespaces: View Creation Logs** to view logs related to the setup. +To retrieve the logs for Codespaces, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "log". Select **Codespaces: Export Logs** to export all logs related to Codespaces or select **Codespaces: View Creation Logs** to view logs related to the setup. ![Command to access logs](/assets/images/help/codespaces/codespaces-logs.png) diff --git a/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 59b5feb5ad..835fe5912a 100644 --- a/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -35,7 +35,7 @@ For more information on what happens when you create a codespace, see "[Deep Div For more information on the lifecycle of a codespace, see "[Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)." -If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the Visual Studio Code documentation. +If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.codespaces.use-visual-studio-features %} diff --git a/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md index a985c3a36c..ff505fbe49 100644 --- a/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ b/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md @@ -33,7 +33,7 @@ shortTitle: Develop in a codespace 4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal. 5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more. -For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation. +For more information on using {% data variables.product.prodname_vscode_shortname %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.codespaces.connect-to-codespace-from-vscode %} @@ -54,7 +54,7 @@ For more information on using {% data variables.product.prodname_vscode %}, see ### Using the {% data variables.product.prodname_vscode_command_palette %} -The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)." +The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette_shortname %} in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)." ## Navigating to an existing codespace diff --git a/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md index 59eb5ed129..3b81563de2 100644 --- a/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ b/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md @@ -20,17 +20,17 @@ shortTitle: Visual Studio Code ## About {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %} -You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. To use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}, you need to install the {% data variables.product.prodname_github_codespaces %} extension. For more information on setting up Codespaces in {% data variables.product.prodname_vscode %}, see "[Prerequisites](#prerequisites)." +You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. To use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode_shortname %}, you need to install the {% data variables.product.prodname_github_codespaces %} extension. For more information on setting up Codespaces in {% data variables.product.prodname_vscode_shortname %}, see "[Prerequisites](#prerequisites)." -By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." +By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode_shortname %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." -If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." +If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode_shortname %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." ## Prerequisites -To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. +To develop in a codespace directly in {% data variables.product.prodname_vscode_shortname %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode_shortname %} October 2020 Release 1.51 or later. -Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode %} documentation. +Use the {% data variables.product.prodname_vscode_marketplace %} to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% mac %} @@ -40,8 +40,8 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. -1. Sign in to {% data variables.product.product_name %} to approve the extension. +2. To authorize {% data variables.product.prodname_vscode_shortname %} to access your account on {% data variables.product.product_name %}, click **Allow**. +3. Sign in to {% data variables.product.product_name %} to approve the extension. {% endmac %} @@ -56,28 +56,28 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. +1. To authorize {% data variables.product.prodname_vscode_shortname %} to access your account on {% data variables.product.product_name %}, click **Allow**. 1. Sign in to {% data variables.product.product_name %} to approve the extension. {% endwindows %} -## Creating a codespace in {% data variables.product.prodname_vscode %} +## Creating a codespace in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.creating-a-codespace-in-vscode %} -## Opening a codespace in {% data variables.product.prodname_vscode %} +## Opening a codespace in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 1. Under "Codespaces", click the codespace you want to develop in. 1. Click the Connect to Codespace icon. - ![The Connect to Codespace icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) + ![The Connect to Codespace icon in {% data variables.product.prodname_vscode_shortname %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) -## Changing the machine type in {% data variables.product.prodname_vscode %} +## Changing the machine type in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.codespaces-machine-types %} You can change the machine type of your codespace at any time. -1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`). +1. In {% data variables.product.prodname_vscode_shortname %}, open the Command Palette (`shift command P` / `shift control P`). 1. Search for and select "Codespaces: Change Machine Type." ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png) @@ -100,13 +100,13 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts. -## Deleting a codespace in {% data variables.product.prodname_vscode %} +## Deleting a codespace in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.deleting-a-codespace-in-vscode %} -## Switching to the Insiders build of {% data variables.product.prodname_vscode %} +## Switching to the Insiders build of {% data variables.product.prodname_vscode_shortname %} -You can use the [Insiders Build of Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_codespaces %}. +You can use the [Insiders Build of {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_codespaces %}. 1. In bottom left of your {% data variables.product.prodname_codespaces %} window, select **{% octicon "gear" aria-label="The settings icon" %} Settings**. 2. From the list, select "Switch to Insiders Version". diff --git a/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md b/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md index 089a99a913..68efad7449 100644 --- a/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md +++ b/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md @@ -24,6 +24,7 @@ You can work with {% data variables.product.prodname_codespaces %} in the {% da - [Delete a codespace](#delete-a-codespace) - [SSH into a codespace](#ssh-into-a-codespace) - [Open a codespace in {% data variables.product.prodname_vscode %}](#open-a-codespace-in-visual-studio-code) +- [Open a codespace in JupyterLab](#open-a-codespace-in-jupyterlab) - [Copying a file to/from a codespace](#copy-a-file-tofrom-a-codespace) - [Modify ports in a codespace](#modify-ports-in-a-codespace) - [Access codespace logs](#access-codespace-logs) @@ -113,6 +114,12 @@ gh codespace code -c codespace-name For more information, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code)." +### Open a codespace in JupyterLab + +```shell +gh codespace jupyter -c codespace-name +``` + ### Copy a file to/from a codespace ```shell diff --git a/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md index 0aa7082eb7..f9ade0113f 100644 --- a/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ b/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md @@ -19,7 +19,7 @@ shortTitle: Source control You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from the remote repository, switch branches, create a new branch, commit and push changes, and create a pull request. You can use the integrated terminal within your codespace to enter Git commands, or you can click icons and menu options to complete all the most common Git tasks. This guide explains how to use the graphical user interface for source control. -Source control in {% data variables.product.prodname_github_codespaces %} uses the same workflow as {% data variables.product.prodname_vscode %}. For more information, see the {% data variables.product.prodname_vscode %} documentation "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)." +Source control in {% data variables.product.prodname_github_codespaces %} uses the same workflow as {% data variables.product.prodname_vscode %}. For more information, see the {% data variables.product.prodname_vscode_shortname %} documentation "[Using Version Control in {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)." A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be: diff --git a/content/codespaces/getting-started/deep-dive.md b/content/codespaces/getting-started/deep-dive.md index b35a0dd68a..47f78fb947 100644 --- a/content/codespaces/getting-started/deep-dive.md +++ b/content/codespaces/getting-started/deep-dive.md @@ -46,13 +46,13 @@ Since your repository is cloned onto the host VM before the container is created ### Step 3: Connecting to the codespace -When your container has been created and any other initialization has run, you'll be connected to your codespace. You can connect to it through the web or via [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed. +When your container has been created and any other initialization has run, you'll be connected to your codespace. You can connect to it through the web or via [{% data variables.product.prodname_vscode_shortname %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed. ### Step 4: Post-creation setup Once you are connected to your codespace, your automated setup may continue to build based on the configuration you specified in your `devcontainer.json` file. You may see `postCreateCommand` and `postAttachCommand` run. -If you want to use Git hooks in your codespace, set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the Visual Studio Code documentation. +If you want to use Git hooks in your codespace, set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. If you have a public dotfiles repository for {% data variables.product.prodname_codespaces %}, you can enable it for use with new codespaces. When enabled, your dotfiles will be cloned to the container and the install script will be invoked. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)." @@ -67,7 +67,7 @@ As you develop in your codespace, it will save any changes to your files every f {% note %} -**Note:** Changes in a codespace in {% data variables.product.prodname_vscode %} are not saved automatically, unless you have enabled [Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). +**Note:** Changes in a codespace in {% data variables.product.prodname_vscode_shortname %} are not saved automatically, unless you have enabled [Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). {% endnote %} ### Closing or stopping your codespace @@ -93,7 +93,7 @@ Running your application when you first land in your codespace can make for a fa ## Committing and pushing your changes -Git is available by default in your codespace and so you can rely on your existing Git workflow. You can work with Git in your codespace either via the Terminal or by using [Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" +Git is available by default in your codespace and so you can rely on your existing Git workflow. You can work with Git in your codespace either via the Terminal or by using [{% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" ![Running git status in Codespaces Terminal](/assets/images/help/codespaces/git-status.png) @@ -107,9 +107,9 @@ You can create a codespace from any branch, commit, or pull request in your proj ## Personalizing your codespace with extensions -Using {% data variables.product.prodname_vscode %} in your codespace gives you access to the {% data variables.product.prodname_vscode %} Marketplace so that you can add any extensions you need. For information on how extensions run in {% data variables.product.prodname_codespaces %}, see [Supporting Remote Development and GitHub Codespaces](https://code.visualstudio.com/api/advanced-topics/remote-extensions) in the {% data variables.product.prodname_vscode %} docs. +Using {% data variables.product.prodname_vscode_shortname %} in your codespace gives you access to the {% data variables.product.prodname_vscode_marketplace %} so that you can add any extensions you need. For information on how extensions run in {% data variables.product.prodname_codespaces %}, see [Supporting Remote Development and GitHub Codespaces](https://code.visualstudio.com/api/advanced-topics/remote-extensions) in the {% data variables.product.prodname_vscode_shortname %} docs. -If you already use {% data variables.product.prodname_vscode %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to automatically sync extensions, settings, themes, and keyboard shortcuts between your local instance and any {% data variables.product.prodname_codespaces %} you create. +If you already use {% data variables.product.prodname_vscode_shortname %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to automatically sync extensions, settings, themes, and keyboard shortcuts between your local instance and any {% data variables.product.prodname_codespaces %} you create. ## Further reading diff --git a/content/codespaces/getting-started/quickstart.md b/content/codespaces/getting-started/quickstart.md index c29dd7b59e..04303abbc2 100644 --- a/content/codespaces/getting-started/quickstart.md +++ b/content/codespaces/getting-started/quickstart.md @@ -76,7 +76,7 @@ Now that you've made a few changes, you can use the integrated terminal or the s ## Personalizing with an extension -Within a codespace, you have access to the Visual Studio Code Marketplace. For this example, you'll install an extension that alters the theme, but you can install any extension that is useful for your workflow. +Within a codespace, you have access to the {% data variables.product.prodname_vscode_marketplace %}. For this example, you'll install an extension that alters the theme, but you can install any extension that is useful for your workflow. 1. In the left sidebar, click the Extensions icon. @@ -88,7 +88,7 @@ Within a codespace, you have access to the Visual Studio Code Marketplace. For t ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png) -4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to any other codespaces you open and any instances of Visual Studio Code that are signed into your GitHub account. +4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to any other codespaces you open and any instances of {% data variables.product.prodname_vscode %} that are signed into your GitHub account. ## Next Steps diff --git a/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md index 9c4ec49bcf..cbdd7fea90 100644 --- a/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md +++ b/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md @@ -41,7 +41,7 @@ You can limit the choice of machine types that are available for repositories ow ## Deleting unused codespaces -Your users can delete their codespaces in https://github.com/codespaces and from within Visual Studio Code. To reduce the size of a codespace, users can manually delete files using the terminal or from within Visual Studio Code. +Your users can delete their codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, users can manually delete files using the terminal or from within {% data variables.product.prodname_vscode_shortname %}. {% note %} diff --git a/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md index 4a29f98e6a..5f54837d95 100644 --- a/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md +++ b/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md @@ -25,7 +25,7 @@ When permissions are listed in the `devcontainer.json` file, you will be prompte To create codespaces with custom permissions defined, you must use one of the following: * The {% data variables.product.prodname_dotcom %} web UI * [{% data variables.product.prodname_dotcom %} CLI](https://github.com/cli/cli/releases/latest) 2.5.2 or later -* [{% data variables.product.prodname_github_codespaces %} Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 or later +* [{% data variables.product.prodname_github_codespaces %} {% data variables.product.prodname_vscode %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 or later ## Setting additional repository permissions diff --git a/content/codespaces/overview.md b/content/codespaces/overview.md index 5dd8184961..88e16eb473 100644 --- a/content/codespaces/overview.md +++ b/content/codespaces/overview.md @@ -34,7 +34,7 @@ To customize the runtimes and tools in your codespace, you can create one or mor If you don't add a dev container configuration, {% data variables.product.prodname_codespaces %} will clone your repository into an environment with the default codespace image that includes many tools, languages, and runtime environments. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". -You can also personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and VS Code extensions. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)". +You can also personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and {% data variables.product.prodname_vscode_shortname %} extensions. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)". ## About billing for {% data variables.product.prodname_codespaces %} diff --git a/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md index ec56098853..cda5e1ada5 100644 --- a/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md +++ b/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md @@ -94,7 +94,7 @@ Prebuilds do not use any user-level secrets while building your environment, bec ## Configuring time-consuming tasks to be included in the prebuild -You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild template creation. For more information, see the Visual Studio Code documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)." +You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild template creation. For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)." `onCreateCommand` is run only once, when the prebuild template is created, whereas `updateContentCommand` is run at template creation and at subsequent template updates. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild template update. diff --git a/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md index f9f1421546..1b05e765d3 100644 --- a/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md +++ b/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md @@ -110,7 +110,7 @@ To use a Dockerfile as part of a dev container configuration, reference it in yo } ``` -For more information about using a Dockerfile in a dev container configuration, see the {% data variables.product.prodname_vscode %} documentation "[Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)." +For more information about using a Dockerfile in a dev container configuration, see the {% data variables.product.prodname_vscode_shortname %} documentation "[Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)." ## Using the default dev container configuration @@ -122,7 +122,7 @@ The default configuration is a good option if you're working on a small project ## Using a predefined dev container configuration -You can choose from a list of predefined configurations to create a dev container configuration for your repository. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed. +You can choose from a list of predefined configurations to create a dev container configuration for your repository. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode_shortname %} settings, and {% data variables.product.prodname_vscode_shortname %} extensions that should be installed. Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project. @@ -192,9 +192,9 @@ If `.devcontainer/devcontainer.json` or `.devcontainer.json` exists, it will be ### Editing the devcontainer.json file -You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %} +You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode_shortname %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %} -The `devcontainer.json` file is written using the JSONC format. This allows you to include comments within the configuration file. For more information, see "[Editing JSON with Visual Studio Code](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode %} documentation. +The `devcontainer.json` file is written using the JSONC format. This allows you to include comments within the configuration file. For more information, see "[Editing JSON with {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% note %} @@ -202,11 +202,11 @@ The `devcontainer.json` file is written using the JSONC format. This allows you {% endnote %} -### Editor settings for Visual Studio Code +### Editor settings for {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.vscode-settings-order %} -You can define default editor settings for {% data variables.product.prodname_vscode %} in two places. +You can define default editor settings for {% data variables.product.prodname_vscode_shortname %} in two places. * Editor settings defined in the `.vscode/settings.json` file in your repository are applied as _Workspace_-scoped settings in the codespace. * Editor settings defined in the `settings` key in the `devcontainer.json` file are applied as _Remote [Codespaces]_-scoped settings in the codespace. diff --git a/content/codespaces/the-githubdev-web-based-editor.md b/content/codespaces/the-githubdev-web-based-editor.md index 087e959b0e..2671daa017 100644 --- a/content/codespaces/the-githubdev-web-based-editor.md +++ b/content/codespaces/the-githubdev-web-based-editor.md @@ -27,7 +27,7 @@ The {% data variables.product.prodname_serverless %} introduces a lightweight ed The {% data variables.product.prodname_serverless %} is available to everyone for free on {% data variables.product.prodname_dotcom_the_website %}. -The {% data variables.product.prodname_serverless %} provides many of the benefits of {% data variables.product.prodname_vscode %}, such as search, syntax highlighting, and a source control view. You can also use Settings Sync to share your own {% data variables.product.prodname_vscode %} settings with the editor. For more information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode %} documentation. +The {% data variables.product.prodname_serverless %} provides many of the benefits of {% data variables.product.prodname_vscode %}, such as search, syntax highlighting, and a source control view. You can also use Settings Sync to share your own {% data variables.product.prodname_vscode_shortname %} settings with the editor. For more information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation. The {% data variables.product.prodname_serverless %} runs entirely in your browser’s sandbox. The editor doesn’t clone the repository, but instead uses the [GitHub Repositories extension](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) to carry out most of the functionality that you will use. Your work is saved in the browser’s local storage until you commit it. You should commit your changes regularly to ensure that they're always accessible. @@ -49,7 +49,7 @@ Both the {% data variables.product.prodname_serverless %} and {% data variables. | **Start up** | The {% data variables.product.prodname_serverless %} opens instantly with a key-press and you can start using it right away, without having to wait for additional configuration or installation. | When you create or resume a codespace, the codespace is assigned a VM and the container is configured based on the contents of a `devcontainer.json` file. This set up may take a few minutes to create the environment. For more information, see "[Creating a Codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." | | **Compute** | There is no associated compute, so you won’t be able to build and run your code or use the integrated terminal. | With {% data variables.product.prodname_codespaces %}, you get the power of dedicated VM on which you can run and debug your application.| | **Terminal access** | None. | {% data variables.product.prodname_codespaces %} provides a common set of tools by default, meaning that you can use the Terminal exactly as you would in your local environment.| -| **Extensions** | Only a subset of extensions that can run in the web will appear in the Extensions View and can be installed. For more information, see "[Using extensions](#using-extensions)."| With Codespaces, you can use most extensions from the Visual Studio Code Marketplace.| +| **Extensions** | Only a subset of extensions that can run in the web will appear in the Extensions View and can be installed. For more information, see "[Using extensions](#using-extensions)."| With Codespaces, you can use most extensions from the {% data variables.product.prodname_vscode_marketplace %}.| ### Continue working on {% data variables.product.prodname_codespaces %} @@ -61,9 +61,9 @@ To continue your work in a codespace, click **Continue Working on…** and selec ## Using source control -When you use the {% data variables.product.prodname_serverless %}, all actions are managed through the Source Control View, which is located in the Activity Bar on the left hand side. For more information on the Source Control View, see "[Version Control](https://code.visualstudio.com/docs/editor/versioncontrol)" in the {% data variables.product.prodname_vscode %} documentation. +When you use the {% data variables.product.prodname_serverless %}, all actions are managed through the Source Control View, which is located in the Activity Bar on the left hand side. For more information on the Source Control View, see "[Version Control](https://code.visualstudio.com/docs/editor/versioncontrol)" in the {% data variables.product.prodname_vscode_shortname %} documentation. -Because the web-based editor uses the GitHub Repositories extension to power its functionality, you can switch branches without needing to stash changes. For more information, see "[GitHub Repositories](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" in the {% data variables.product.prodname_vscode %} documentation. +Because the web-based editor uses the GitHub Repositories extension to power its functionality, you can switch branches without needing to stash changes. For more information, see "[GitHub Repositories](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" in the {% data variables.product.prodname_vscode_shortname %} documentation. ### Create a new branch @@ -88,9 +88,9 @@ You can use the {% data variables.product.prodname_serverless %} to work with an ## Using extensions -The {% data variables.product.prodname_serverless %} supports {% data variables.product.prodname_vscode %} extensions that have been specifically created or updated to run in the web. These extensions are known as "web extensions". To learn how you can create a web extension or update your existing extension to work for the web, see "[Web extensions](https://code.visualstudio.com/api/extension-guides/web-extensions)" in the {% data variables.product.prodname_vscode %} documentation. +The {% data variables.product.prodname_serverless %} supports {% data variables.product.prodname_vscode_shortname %} extensions that have been specifically created or updated to run in the web. These extensions are known as "web extensions". To learn how you can create a web extension or update your existing extension to work for the web, see "[Web extensions](https://code.visualstudio.com/api/extension-guides/web-extensions)" in the {% data variables.product.prodname_vscode_shortname %} documentation. -Extensions that can run in the {% data variables.product.prodname_serverless %} will appear in the Extensions View and can be installed. If you use Settings Sync, any compatible extensions are also installed automatically. For information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode %} documentation. +Extensions that can run in the {% data variables.product.prodname_serverless %} will appear in the Extensions View and can be installed. If you use Settings Sync, any compatible extensions are also installed automatically. For information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation. ## Troubleshooting @@ -104,5 +104,5 @@ If you have issues opening the {% data variables.product.prodname_serverless %}, ### Known limitations - The {% data variables.product.prodname_serverless %} is currently supported in Chrome (and various other Chromium-based browsers), Edge, Firefox, and Safari. We recommend that you use the latest versions of these browsers. -- Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "[Known limitations and adaptations](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" section of the {% data variables.product.prodname_vscode %} documentation. +- Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "[Known limitations and adaptations](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" section of the {% data variables.product.prodname_vscode_shortname %} documentation. - `.` may not work to open the {% data variables.product.prodname_serverless %} according to your local keyboard layout. In that case, you can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} by changing the URL from `github.com` to `github.dev`. diff --git a/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/content/codespaces/troubleshooting/troubleshooting-prebuilds.md index 8076d27db3..914b2c17f2 100644 --- a/content/codespaces/troubleshooting/troubleshooting-prebuilds.md +++ b/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -22,11 +22,11 @@ When you create a codespace, you can choose the type of the virtual machine you ![A list of available machine types](/assets/images/help/codespaces/choose-custom-machine-type.png) -If you have your {% data variables.product.prodname_codespaces %} editor preference set to "Visual Studio Code for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used. +If you have your {% data variables.product.prodname_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used. ![The 'prebuilt codespace found' message](/assets/images/help/codespaces/prebuilt-codespace-found.png) -Similarly, if your editor preference is "Visual Studio Code" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for Codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)." +Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for Codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)." After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal: diff --git a/content/communities/moderating-comments-and-conversations/index.md b/content/communities/moderating-comments-and-conversations/index.md index 7facf03a28..47f9a7dbc5 100644 --- a/content/communities/moderating-comments-and-conversations/index.md +++ b/content/communities/moderating-comments-and-conversations/index.md @@ -16,7 +16,7 @@ children: - /managing-disruptive-comments - /locking-conversations - /limiting-interactions-in-your-repository - - /limiting-interactions-for-your-user-account + - /limiting-interactions-for-your-personal-account - /limiting-interactions-in-your-organization - /tracking-changes-in-a-comment - /managing-how-contributors-report-abuse-in-your-organizations-repository diff --git a/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md b/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md similarity index 92% rename from content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md rename to content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md index 79394cfd3f..b212db7e2f 100644 --- a/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md +++ b/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md @@ -1,5 +1,5 @@ --- -title: Limiting interactions for your user account +title: Limiting interactions for your personal account intro: You can temporarily enforce a period of limited activity for certain users in all public repositories owned by your personal account. versions: fpt: '*' @@ -7,6 +7,7 @@ versions: permissions: Anyone can limit interactions for their own personal account. redirect_from: - /github/building-a-strong-community/limiting-interactions-for-your-user-account + - /communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account topics: - Community shortTitle: Limit interactions in account diff --git a/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md index b7f1a32c09..ab19707716 100644 --- a/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md +++ b/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md @@ -22,7 +22,7 @@ shortTitle: Limit interactions in repo {% data reusables.community.types-of-interaction-limits %} -You can also enable activity limitations on all repositories owned by your personal account or an organization. If a user-wide or organization-wide limit is enabled, you can't limit activity for individual repositories owned by the account. For more information, see "[Limiting interactions for your personal account](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account)" and "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)." +You can also enable activity limitations on all repositories owned by your personal account or an organization. If a user-wide or organization-wide limit is enabled, you can't limit activity for individual repositories owned by the account. For more information, see "[Limiting interactions for your personal account](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account)" and "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)." ## Limiting interactions in your repository diff --git a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md index f7d69d6de4..c72af1ee61 100644 --- a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md +++ b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md @@ -36,9 +36,7 @@ Using the template builder, you can specify a title and description for each tem With issue forms, you can create templates that have web form fields using the {% data variables.product.prodname_dotcom %} form schema. When a contributor opens an issue using an issue form, the form inputs are converted to a standard markdown issue comment. You can specify different input types and set inputs as required to help contributors open actionable issues in your repository. For more information, see "[Configuring issue templates for your repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)" and "[Syntax for issue forms](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)." {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} {% data reusables.repositories.issue-template-config %} For more information, see "[Configuring issue templates for your repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser)." -{% endif %} Issue templates are stored on the repository's default branch, in a hidden `.github/ISSUE_TEMPLATE` directory. If you create a template in another branch, it will not be available for collaborators to use. Issue template filenames are not case sensitive, and need a *.md* extension.{% ifversion fpt or ghec %} Issue templates created with issue forms need a *.yml* extension.{% endif %} {% data reusables.repositories.valid-community-issues %} diff --git a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md index 066cfdc38d..7620665f59 100644 --- a/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md +++ b/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md @@ -21,12 +21,8 @@ shortTitle: Configure {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} - ## Creating issue templates -{% endif %} - {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 3. In the "Features" section, under "Issues," click **Set up templates**. @@ -71,7 +67,6 @@ Here is the rendered version of the issue form. {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} ## Configuring the template chooser {% data reusables.repositories.issue-template-config %} @@ -110,7 +105,6 @@ Your configuration file will customize the template chooser when the file is mer {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -{% endif %} ## Further reading diff --git a/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md b/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md index e1e2978286..eabce3420e 100644 --- a/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md +++ b/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md @@ -16,7 +16,7 @@ shortTitle: Configure default editor - [Atom](https://atom.io/) - [MacVim](https://macvim-dev.github.io/macvim/) -- [Visual Studio Code](https://code.visualstudio.com/) +- [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) - [Visual Studio Codium](https://vscodium.com/) - [Sublime Text](https://www.sublimetext.com/) - [BBEdit](http://www.barebones.com/products/bbedit/) @@ -43,7 +43,7 @@ shortTitle: Configure default editor {% windows %} - [Atom](https://atom.io/) -- [Visual Studio Code](https://code.visualstudio.com/) +- [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) - [Visual Studio Codium](https://vscodium.com/) - [Sublime Text](https://www.sublimetext.com/) - [ColdFusion Builder](https://www.adobe.com/products/coldfusion-builder.html) diff --git a/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md index 1971ab0671..010925e926 100644 --- a/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md +++ b/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md @@ -88,7 +88,7 @@ Permission | Description [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`. [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`. [`statuses`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Grants access to the [Statuses API](/rest/reference/commits#commit-statuses). Can be one of: `none`, `read`, or `write`. -[`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +[`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghae or ghec %} `vulnerability_alerts`| Grants access to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in a repository. See "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" to learn more. Can be one of: `none` or `read`.{% endif %} `watching` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`. diff --git a/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index 1dff469f06..ab9085085c 100644 --- a/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -238,8 +238,8 @@ While most of your API interaction should occur using your server-to-server inst * [List deployments](/rest/reference/deployments#list-deployments) * [Create a deployment](/rest/reference/deployments#create-a-deployment) -* [Get a deployment](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %} -* [Delete a deployment](/rest/reference/deployments#delete-a-deployment){% endif %} +* [Get a deployment](/rest/reference/deployments#get-a-deployment) +* [Delete a deployment](/rest/reference/deployments#delete-a-deployment) #### Events @@ -421,14 +421,12 @@ While most of your API interaction should occur using your server-to-server inst * [Remove pre-receive hook enforcement for an organization](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} #### Organization Team Projects * [List team projects](/rest/reference/teams#list-team-projects) * [Check team permissions for a project](/rest/reference/teams#check-team-permissions-for-a-project) * [Add or update team project permissions](/rest/reference/teams#add-or-update-team-project-permissions) * [Remove a project from a team](/rest/reference/teams#remove-a-project-from-a-team) -{% endif %} #### Organization Team Repositories @@ -574,7 +572,7 @@ While most of your API interaction should occur using your server-to-server inst #### Reactions -{% ifversion fpt or ghes or ghae or ghec %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Delete a reaction](/rest/reference/reactions#delete-a-reaction){% endif %} +* [Delete a reaction](/rest/reference/reactions) * [List reactions for a commit comment](/rest/reference/reactions#list-reactions-for-a-commit-comment) * [Create reaction for a commit comment](/rest/reference/reactions#create-reaction-for-a-commit-comment) * [List reactions for an issue](/rest/reference/reactions#list-reactions-for-an-issue) @@ -586,13 +584,13 @@ While most of your API interaction should occur using your server-to-server inst * [List reactions for a team discussion comment](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) * [Create reaction for a team discussion comment](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) * [List reactions for a team discussion](/rest/reference/reactions#list-reactions-for-a-team-discussion) -* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %} +* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion) * [Delete a commit comment reaction](/rest/reference/reactions#delete-a-commit-comment-reaction) * [Delete an issue reaction](/rest/reference/reactions#delete-an-issue-reaction) * [Delete a reaction to a commit comment](/rest/reference/reactions#delete-an-issue-comment-reaction) * [Delete a pull request comment reaction](/rest/reference/reactions#delete-a-pull-request-comment-reaction) * [Delete team discussion reaction](/rest/reference/reactions#delete-team-discussion-reaction) -* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} +* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction) #### Repositories @@ -706,11 +704,9 @@ While most of your API interaction should occur using your server-to-server inst * [Get a repository README](/rest/reference/repos#get-a-repository-readme) * [Get the license for a repository](/rest/reference/licenses#get-the-license-for-a-repository) -{% ifversion fpt or ghes or ghae or ghec %} #### Repository Event Dispatches * [Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event) -{% endif %} #### Repository Hooks 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 fc1883a9d7..473b1175ea 100644 --- a/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -338,7 +338,7 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr * "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" * "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" -* "[Device flow errors](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +* "[Device flow errors](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} * "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} ## Further reading diff --git a/content/developers/apps/getting-started-with-apps/about-apps.md b/content/developers/apps/getting-started-with-apps/about-apps.md index eec4a49f78..b2ddf4a8d6 100644 --- a/content/developers/apps/getting-started-with-apps/about-apps.md +++ b/content/developers/apps/getting-started-with-apps/about-apps.md @@ -84,7 +84,7 @@ Keep these ideas in mind when using personal access tokens: * You can perform one-off cURL requests. * You can run personal scripts. * Don't set up a script for your whole team or company to use. -* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %} +* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} * Do set an expiration for your personal access tokens, to help keep your information secure.{% endif %} ## Determining which integration to build diff --git a/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md b/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md index bc383cc73c..df2281c42d 100644 --- a/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md +++ b/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md @@ -89,4 +89,4 @@ Your language and server implementations may differ from this example code. Howe * Using a plain `==` operator is **not advised**. A method like [`secure_compare`][secure_compare] performs a "constant time" string comparison, which helps mitigate certain timing attacks against regular equality operators. -[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare +[secure_compare]: https://rubydoc.info/github/rack/rack/main/Rack/Utils:secure_compare diff --git a/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index c0e70736bb..517f94bf5d 100644 --- a/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -353,8 +353,8 @@ Webhook events are triggered based on the specificity of the domain you register ### Webhook payload object Key | Type | Description -----|------|-------------{% ifversion fpt or ghes or ghae or ghec %} -`action` |`string` | The action performed. Can be `created`.{% endif %} +----|------|------------- +`action` |`string` | The action performed. Can be `created`. `deployment` |`object` | The [deployment](/rest/reference/deployments#list-deployments). {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} @@ -378,8 +378,8 @@ Key | Type | Description ### Webhook payload object Key | Type | Description -----|------|-------------{% ifversion fpt or ghes or ghae or ghec %} -`action` |`string` | The action performed. Can be `created`.{% endif %} +----|------|------------- +`action` |`string` | The action performed. Can be `created`. `deployment_status` |`object` | The [deployment status](/rest/reference/deployments#list-deployment-statuses). `deployment_status["state"]` |`string` | The new state. Can be `pending`, `success`, `failure`, or `error`. `deployment_status["target_url"]` |`string` | The optional link added to the status. @@ -1152,7 +1152,6 @@ Key | Type | Description {{ webhookPayloadsForCurrentVersion.release.published }} -{% ifversion fpt or ghes or ghae or ghec %} ## repository_dispatch This event occurs when a {% data variables.product.prodname_github_app %} sends a `POST` request to the "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)" endpoint. @@ -1164,7 +1163,6 @@ This event occurs when a {% data variables.product.prodname_github_app %} sends ### Webhook payload example {{ webhookPayloadsForCurrentVersion.repository_dispatch }} -{% endif %} ## repository @@ -1488,7 +1486,7 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS {{ webhookPayloadsForCurrentVersion.workflow_dispatch }} {% endif %} -{% ifversion fpt or ghes > 3.2 or ghec or ghae-issue-4462 %} +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## workflow_job diff --git a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md index 36db699c94..8a9e3f877f 100644 --- a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md +++ b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md @@ -1,38 +1,38 @@ --- title: About using Visual Studio Code with GitHub Classroom shortTitle: About using Visual Studio Code -intro: 'You can configure Visual Studio Code as the preferred editor for assignments in {% data variables.product.prodname_classroom %}.' +intro: 'You can configure {% data variables.product.prodname_vscode %} as the preferred editor for assignments in {% data variables.product.prodname_classroom %}.' versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/about-using-vs-code-with-github-classroom --- -## About Visual Studio Code +## About {% data variables.product.prodname_vscode %} -Visual Studio Code is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. With the [GitHub Classroom extension for Visual Studio Code](https://aka.ms/classroom-vscode-ext), students can easily browse, edit, submit, collaborate, and test their Classroom Assignments. For more information about IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)." +{% data variables.product.prodname_vscode %} is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. With the [GitHub Classroom extension for {% data variables.product.prodname_vscode_shortname %}](https://aka.ms/classroom-vscode-ext), students can easily browse, edit, submit, collaborate, and test their Classroom Assignments. For more information about IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)." ### Your student's editor of choice -The GitHub Classroom integration with Visual Studio Code provides students with an extension pack which contains: +The GitHub Classroom integration with {% data variables.product.prodname_vscode_shortname %} provides students with an extension pack which contains: 1. [GitHub Classroom Extension](https://aka.ms/classroom-vscode-ext) with custom abstractions that make it easy for students to navigate getting started. 2. [Visual Studio Live Share Extension](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare-pack) integrating into a student view for easy access to teaching assistants and classmates for help and collaboration. 3. [GitHub Pull Request Extension](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) allowing students to see feedback from their instructors within the editor. -### How to launch the assignment in Visual Studio Code -When creating an assignment, Visual Studio Code can be added as the preferred editor for an assignment. For more details, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)." +### How to launch the assignment in {% data variables.product.prodname_vscode_shortname %} +When creating an assignment, {% data variables.product.prodname_vscode_shortname %} can be added as the preferred editor for an assignment. For more details, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)." -This will include an "Open in Visual Studio Code" badge in all student repositories. This badge handles installing Visual Studio Code, the Classroom extension pack, and opening to the active assignment with one click. +This will include an "Open in {% data variables.product.prodname_vscode_shortname %}" badge in all student repositories. This badge handles installing {% data variables.product.prodname_vscode_shortname %}, the Classroom extension pack, and opening to the active assignment with one click. {% note %} -**Note:** The student must have Git installed on their computer to push code from Visual Studio Code to their repository. This is not automatically installed when clicking the **Open in Visual Studio Code** button. The student can download Git from [here](https://git-scm.com/downloads). +**Note:** The student must have Git installed on their computer to push code from {% data variables.product.prodname_vscode_shortname %} to their repository. This is not automatically installed when clicking the **Open in {% data variables.product.prodname_vscode_shortname %}** button. The student can download Git from [here](https://git-scm.com/downloads). {% endnote %} ### How to use GitHub Classroom extension pack The GitHub Classroom extension has two major components: the 'Classrooms' view and the 'Active Assignment' view. -When the student launches the extension for the first time, they are automatically navigated to the Explorer tab in Visual Studio Code, where they can see the "Active Assignment" view alongside the tree-view of files in the repository. +When the student launches the extension for the first time, they are automatically navigated to the Explorer tab in {% data variables.product.prodname_vscode_shortname %}, where they can see the "Active Assignment" view alongside the tree-view of files in the repository. ![GitHub Classroom Active Assignment View](/assets/images/help/classroom/vs-code-active-assignment.png) diff --git a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md index b623657437..0e61e57eb7 100644 --- a/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md +++ b/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md @@ -24,7 +24,7 @@ After a student accepts an assignment with an IDE, the README file in the studen | :- | :- | | {% data variables.product.prodname_github_codespaces %} | "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)" | | Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | -| Visual Studio Code | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace | +| {% data variables.product.prodname_vscode %} | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace | We know cloud IDE integrations are important to your classroom and are working to bring more options. 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 324d48998a..19f6ecfba3 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 @@ -13,7 +13,7 @@ shortTitle: Extensions & integrations --- ## Editor tools -You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and Visual Studio. +You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and {% data variables.product.prodname_vs %}. ### {% data variables.product.product_name %} for Atom @@ -23,13 +23,13 @@ With the {% data variables.product.product_name %} for Atom extension, you can c With the {% data variables.product.product_name %} for Unity editor extension, you can develop on Unity, the open source game development platform, and see your work on {% data variables.product.product_name %}. For more information, see the official Unity editor extension [site](https://unity.github.com/) or the [documentation](https://github.com/github-for-unity/Unity/tree/master/docs). -### {% data variables.product.product_name %} for Visual Studio +### {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} -With the {% data variables.product.product_name %} for Visual Studio extension, you can work in {% data variables.product.product_name %} repositories without leaving Visual Studio. For more information, see the official Visual Studio extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs). +With the {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} extension, you can work in {% data variables.product.product_name %} repositories without leaving {% data variables.product.prodname_vs %}. For more information, see the official {% data variables.product.prodname_vs %} extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs). -### {% data variables.product.prodname_dotcom %} for Visual Studio Code +### {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} -With the {% data variables.product.prodname_dotcom %} for Visual Studio Code extension, you can review and manage {% data variables.product.product_name %} pull requests in Visual Studio Code. For more information, see the official Visual Studio Code extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github). +With the {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} extension, you can review and manage {% data variables.product.product_name %} pull requests in {% data variables.product.prodname_vscode_shortname %}. For more information, see the official {% data variables.product.prodname_vscode_shortname %} extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github). ## Project management tools diff --git a/content/get-started/exploring-projects-on-github/following-organizations.md b/content/get-started/exploring-projects-on-github/following-organizations.md index ab98ff230a..64d7144396 100644 --- a/content/get-started/exploring-projects-on-github/following-organizations.md +++ b/content/get-started/exploring-projects-on-github/following-organizations.md @@ -15,7 +15,7 @@ topics: ## About followers on {% data variables.product.product_name %} -When you follow organizations, you'll see their public activity on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)." +When you follow organizations, you'll see their public activity on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)." You can unfollow an organization if you do not wish to see their {% ifversion fpt or ghec %}public{% endif %} activity on {% data variables.product.product_name %}. diff --git a/content/get-started/exploring-projects-on-github/following-people.md b/content/get-started/exploring-projects-on-github/following-people.md index 7da9ba59eb..da3c32149e 100644 --- a/content/get-started/exploring-projects-on-github/following-people.md +++ b/content/get-started/exploring-projects-on-github/following-people.md @@ -17,7 +17,7 @@ topics: ## About followers on {% data variables.product.product_name %} -When you follow people, you'll see their public activity on your personal dashboard.{% ifversion fpt or ghec %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you.{% endif %} For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)." +When you follow people, you'll see their public activity on your personal dashboard.{% ifversion fpt or ghec %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you.{% endif %} For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)." You can unfollow someone if you do not wish to see their public activity on {% data variables.product.product_name %}. diff --git a/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md b/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md index 4f5b225643..138bd77574 100644 --- a/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md +++ b/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md @@ -25,7 +25,7 @@ You can search, sort, and filter your starred repositories and topics on your {% Starring makes it easy to find a repository or topic again later. You can see all the repositories and topics you have starred by going to your {% data variables.explore.your_stars_page %}. {% ifversion fpt or ghec %} -You can star repositories and topics to discover similar projects on {% data variables.product.product_name %}. When you star repositories or topics, {% data variables.product.product_name %} may recommend related content on your personal dashboard. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)" and "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)." +You can star repositories and topics to discover similar projects on {% data variables.product.product_name %}. When you star repositories or topics, {% data variables.product.product_name %} may recommend related content on your personal dashboard. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)" and "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)." {% endif %} Starring a repository also shows appreciation to the repository maintainer for their work. Many of {% data variables.product.prodname_dotcom %}'s repository rankings depend on the number of stars a repository has. In addition, [Explore](https://github.com/explore) shows popular repositories based on the number of stars they have. diff --git a/content/get-started/getting-started-with-git/about-remote-repositories.md b/content/get-started/getting-started-with-git/about-remote-repositories.md index b706d97d92..612bb78690 100644 --- a/content/get-started/getting-started-with-git/about-remote-repositories.md +++ b/content/get-started/getting-started-with-git/about-remote-repositories.md @@ -81,14 +81,10 @@ When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote reposit {% endtip %} -{% ifversion fpt or ghes or ghae or ghec %} - ## Cloning with {% data variables.product.prodname_cli %} You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} workflows in your terminal. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." -{% endif %} - {% ifversion not ghae %} ## Cloning with Subversion diff --git a/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/content/get-started/getting-started-with-git/associating-text-editors-with-git.md index 5aa79a46c7..d903687c9b 100644 --- a/content/get-started/getting-started-with-git/associating-text-editors-with-git.md +++ b/content/get-started/getting-started-with-git/associating-text-editors-with-git.md @@ -27,9 +27,9 @@ shortTitle: Associate text editors $ git config --global core.editor "atom --wait" ``` -## Using Visual Studio Code as your editor +## Using {% data variables.product.prodname_vscode %} as your editor -1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation. +1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.command_line.open_the_multi_os_terminal %} 3. Type this command: ```shell @@ -67,9 +67,9 @@ shortTitle: Associate text editors $ git config --global core.editor "atom --wait" ``` -## Using Visual Studio Code as your editor +## Using {% data variables.product.prodname_vscode %} as your editor -1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation. +1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.command_line.open_the_multi_os_terminal %} 3. Type this command: ```shell @@ -106,9 +106,9 @@ shortTitle: Associate text editors $ git config --global core.editor "atom --wait" ``` -## Using Visual Studio Code as your editor +## Using {% data variables.product.prodname_vscode %} as your editor -1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation. +1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.command_line.open_the_multi_os_terminal %} 3. Type this command: ```shell 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 7616cc276e..8eaea418ac 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 @@ -30,7 +30,7 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th - **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository.{% if secret-scanning-push-protection %} If push protection is enabled, also detects secrets when they are pushed to your repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)" and "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."{% else %} For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)."{% endif %} -{% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4864 %} +{% ifversion fpt or ghes > 3.1 or ghec or ghae %} - **Dependency review** - 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 %} @@ -113,4 +113,4 @@ For more information on starter workflows, see "[Setting up {% data variables.pr - "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)" {% endif %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/content/get-started/learning-about-github/about-versions-of-github-docs.md b/content/get-started/learning-about-github/about-versions-of-github-docs.md index 3e0c3f751b..90891c4225 100644 --- a/content/get-started/learning-about-github/about-versions-of-github-docs.md +++ b/content/get-started/learning-about-github/about-versions-of-github-docs.md @@ -37,7 +37,7 @@ In a wide browser window, there is no text that immediately follows the {% data On {% data variables.product.prodname_dotcom_the_website %}, each account has its own plan. Each personal account has an associated plan that provides access to certain features, and each organization has a different associated plan. If your personal account is a member of an organization on {% data variables.product.prodname_dotcom_the_website %}, you may have access to different features when you use resources owned by that organization than when you use resources owned by your personal account. For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)." -If you don't know whether an organization uses {% data variables.product.prodname_ghe_cloud %}, ask an organization owner. For more information, see "[Viewing people's roles in an organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)." +If you don't know whether an organization uses {% data variables.product.prodname_ghe_cloud %}, ask an organization owner. For more information, see "[Viewing people's roles in an organization](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)." ### {% data variables.product.prodname_ghe_server %} diff --git a/content/get-started/onboarding/getting-started-with-your-github-account.md b/content/get-started/onboarding/getting-started-with-your-github-account.md index fb8cf05ac1..2e0c446eb0 100644 --- a/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -75,7 +75,7 @@ For more information about how to authenticate to {% data variables.product.prod | ------------- | ------------- | ------------- | | Browse to {% data variables.product.prodname_dotcom_the_website %} | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests.| This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally. | | {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} extends and simplifies your {% data variables.product.prodname_dotcom_the_website %} workflow, using a visual interface instead of text commands on the command line. For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}. | -| IDE or text editor | You can set a default text editor, like [Atom](https://atom.io/) or [Visual Studio Code](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. | +| IDE or text editor | You can set a default text editor, like [Atom](https://atom.io/) or [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. | | Command line, with or without {% data variables.product.prodname_cli %} | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."

{% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line. | | {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)." | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. | ### 4. Writing on {% data variables.product.product_name %} diff --git a/content/get-started/quickstart/communicating-on-github.md b/content/get-started/quickstart/communicating-on-github.md index 3f155a9a7e..a4328502c5 100644 --- a/content/get-started/quickstart/communicating-on-github.md +++ b/content/get-started/quickstart/communicating-on-github.md @@ -116,7 +116,6 @@ This example shows the {% data variables.product.prodname_discussions %} welcome This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository. {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} ### Scenarios for team discussions - I have a question that's not necessarily related to specific files in the repository. @@ -139,8 +138,6 @@ The `octocat` team member posted a team discussion, informing the team of variou - There is a blog post describing how the teams use {% data variables.product.prodname_actions %} to produce their docs. - Material about the April All Hands is now available for all team members to view. -{% endif %} - ## Next steps These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs. diff --git a/content/get-started/using-github/github-command-palette.md b/content/get-started/using-github/github-command-palette.md index 293ae6772c..751f81b7a9 100644 --- a/content/get-started/using-github/github-command-palette.md +++ b/content/get-started/using-github/github-command-palette.md @@ -153,7 +153,7 @@ These commands are available from all scopes. |`New organization`|Create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." | |`New project`|Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)." | |`New repository`|Create a new repository from scratch. For more information, see "[Creating a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository)." | -|`Switch theme to `|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." | +|`Switch theme to `|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)." | ### Organization commands diff --git a/content/get-started/using-github/github-mobile.md b/content/get-started/using-github/github-mobile.md index e99da062ad..fe88929e61 100644 --- a/content/get-started/using-github/github-mobile.md +++ b/content/get-started/using-github/github-mobile.md @@ -25,10 +25,13 @@ With {% data variables.product.prodname_mobile %} you can: - Read, review, and collaborate on issues and pull requests - Search for, browse, and interact with users, repositories, and organizations - Receive a push notification when someone mentions your username -{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication{% endif %} +{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication +- Verify your sign in attempts on unrecognized devices{% endif %} For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)." +{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)." {% endif %} + ## Installing {% data variables.product.prodname_mobile %} To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% data variables.product.prodname_mobile %}](https://github.com/mobile). diff --git a/content/get-started/using-github/keyboard-shortcuts.md b/content/get-started/using-github/keyboard-shortcuts.md index 619f8d7304..a8a2111f3d 100644 --- a/content/get-started/using-github/keyboard-shortcuts.md +++ b/content/get-started/using-github/keyboard-shortcuts.md @@ -19,7 +19,7 @@ versions: Typing ? on {% data variables.product.prodname_dotcom %} brings up a dialog box that lists the keyboard shortcuts available for that page. You can use these keyboard shortcuts to perform actions across the site without using your mouse to navigate. {% if keyboard-shortcut-accessibility-setting %} -You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see "[Managing accessibility settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings)."{% endif %} +You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see "[Managing accessibility settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings)."{% endif %} Below is a list of some of the available keyboard shortcuts. {% if command-palette %} @@ -30,7 +30,7 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a | Keyboard shortcut | Description |-----------|------------ |S or / | Focus the search bar. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." -|G N | Go to your notifications. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." +|G N | Go to your notifications. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)." |Esc | When focused on a user, issue, or pull request hovercard, closes the hovercard and refocuses on the element the hovercard is in {% if command-palette %}|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 %} @@ -89,10 +89,12 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |-----------|------------ |Command+B (Mac) or
Ctrl+B (Windows/Linux) | Inserts Markdown formatting for bolding text |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) | Inserts Markdown formatting for creating a link +|Command+E (Mac) or
Ctrl+E (Windows/Linux) | Inserts Markdown formatting for code or a command within a line{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.1 or ghec %} +|Command+K (Mac) or
Ctrl+K (Windows/Linux) | Inserts Markdown formatting for creating a link{% endif %}{% ifversion fpt or ghae-issue-7103 or ghes > 3.5 or ghec %} +|Command+V (Mac) or
Ctrl+V (Windows/Linux) | Creates a Markdown link when applied over highlighted text{% endif %} |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+Opt+V (Mac) or
Ctrl+Shift+Alt+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) | Submits a comment @@ -101,7 +103,6 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |Command+G (Mac) or
Ctrl+G (Windows/Linux) | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." |{% endif %} |R | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." | - ## Issue and pull request lists | Keyboard shortcut | Description @@ -137,8 +138,8 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |J | Move selection down in the list |K | Move selection up in the list |Command+Shift+Enter | Add a single comment on a pull request diff | -|Alt and click | 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. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|{% endif %} +|Alt and click | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down Alt and clicking **Show outdated** or **Hide outdated**.| +|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. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."| ## Project boards @@ -195,7 +196,6 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr ## Notifications -{% ifversion fpt or ghes or ghae or ghec %} | Keyboard shortcut | Description |-----------|------------ |E | Mark as done @@ -203,13 +203,6 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |Shift+I| Mark as read |Shift+M | Unsubscribe -{% else %} - -| Keyboard shortcut | Description -|-----------|------------ -|E or I or Y | Mark as read -|Shift+M | Mute thread -{% endif %} ## Network graph diff --git a/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md index 00a5333f72..ce5486664c 100644 --- a/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ b/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md @@ -60,7 +60,6 @@ Gist supports mapping GeoJSON files. These maps are displayed in embedded gists, Follow the steps below to create a gist. -{% ifversion fpt or ghes or ghae or ghec %} {% note %} You can also create a gist using the {% data variables.product.prodname_cli %}. For more information, see "[`gh gist create`](https://cli.github.com/manual/gh_gist_create)" in the {% data variables.product.prodname_cli %} documentation. @@ -68,7 +67,6 @@ You can also create a gist using the {% data variables.product.prodname_cli %}. Alternatively, you can drag and drop a text file from your desktop directly into the editor. {% endnote %} -{% endif %} 1. Sign in to {% data variables.product.product_name %}. 2. Navigate to your {% data variables.gists.gist_homepage %}. 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 3446f690ed..8abb878595 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 @@ -28,10 +28,9 @@ When you use two or more headings, GitHub automatically generates a table of con ![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. +You can indicate emphasis with bold, italic, strikethrough, subscript, or superscript text in comment fields and `.md` files. | Style | Syntax | Keyboard shortcut | Example | Output | | --- | --- | --- | --- | --- | @@ -40,6 +39,8 @@ You can indicate emphasis with bold, italic, or strikethrough text in comment fi | Strikethrough | `~~ ~~` | | `~~This was mistaken text~~` | ~~This was mistaken text~~ | | Bold and nested italic | `** **` and `_ _` | | `**This text is _extremely_ important**` | **This text is _extremely_ important** | | All bold and italic | `*** ***` | | `***All this text is important***` | ***All this text is important*** | +| Subscript | ` ` | | `This is a subscript text` | This is a subscript text | +| Superscript | ` ` | | `This is a superscript text` | This is a superscript text | ## Quoting text @@ -90,6 +91,8 @@ For more information, see "[Creating and highlighting code blocks](/articles/cre You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also use the keyboard shortcut Command+K to create a link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %} +{% ifversion fpt or ghae-issue-7103 or ghes > 3.5 or ghec %} You can also create a Markdown hyperlink by highlighting the text and using the keyboard shortcut Command+V. If you'd like to replace the text with the link, use the keyboard shortcut Command+Shift+V.{% endif %} + `This site was built using [GitHub Pages](https://pages.github.com/).` ![Rendered link](/assets/images/help/writing/link-rendered.png) @@ -234,7 +237,7 @@ For more information, see "[About task lists](/articles/about-task-lists)." ## Mentioning people and teams -You can mention a person or [team](/articles/setting-up-teams/) on {% data variables.product.product_name %} by typing @ plus their username or team name. This will trigger a notification and bring their attention to the conversation. People will also receive a notification if you edit a comment to mention their username or team name. For more information about notifications, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." +You can mention a person or [team](/articles/setting-up-teams/) on {% data variables.product.product_name %} by typing @ plus their username or team name. This will trigger a notification and bring their attention to the conversation. People will also receive a notification if you edit a comment to mention their username or team name. For more information about notifications, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)." {% note %} @@ -295,7 +298,7 @@ For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet]( You can create a new paragraph by leaving a blank line between lines of text. -{% ifversion fpt or ghae-issue-5180 or ghes > 3.2 or ghec %} +{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## Footnotes You can add footnotes to your content by using this bracket syntax: 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 b635490bff..71c305824a 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 @@ -14,6 +14,7 @@ children: - /organizing-information-with-collapsed-sections - /creating-and-highlighting-code-blocks - /creating-diagrams + - /writing-mathematical-expressions - /autolinked-references-and-urls - /attaching-files - /creating-a-permanent-link-to-a-code-snippet diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md b/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md index 337d425e67..a6ea7be3a1 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md @@ -15,7 +15,7 @@ topics: ## Linking a pull request to an 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`. +To link a pull request to an issue to show that a fix is in progress and to 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`. * close * closes diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md new file mode 100644 index 0000000000..c9485dfa83 --- /dev/null +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md @@ -0,0 +1,59 @@ +--- +title: Writing mathematical expressions +intro: 'Use Markdown to display mathematical expressions on {% data variables.product.company_short %}.' +versions: + feature: math +shortTitle: Mathematical expressions +--- + +To enable clear communication of mathematical expressions, {% data variables.product.product_name %} supports LaTeX formatted math within Markdown. For more information, see [LaTeX/Mathematics](http://en.wikibooks.org/wiki/LaTeX/Mathematics) in Wikibooks. + +{% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide). + +## Writing inline expressions + +To include a math expression inline with your text, delimit the expression with a dollar symbol `$`. + +``` +This sentence uses `$` delimiters to show math inline: $\sqrt{3x-1}+(1+x)^2$ +``` + +![Inline math markdown rendering](/assets/images/help/writing/inline-math-markdown-rendering.png) + +## Writing expressions as blocks + +To add a math expression as a block, start a new line and delimit the expression with two dollar symbols `$$`. + +``` +**The Cauchy-Schwarz Inequality** + +$$\left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right)$$ +``` + +![Math expression as a block rendering](/assets/images/help/writing/math-expression-as-a-block-rendering.png) + +## Writing dollar signs in line with and within mathematical expressions + +To display a dollar sign as a character in the same line as a mathematical expression, you need to escape the non-delimiter `$` to ensure the line renders correctly. + + - Within a math expression, add a `\` symbol before the explicit `$`. + + ``` + This expression uses `\$` to display a dollar sign: $\sqrt{\$4}$ + ``` + + ![Dollar sign within math expression](/assets/images/help/writing/dollar-sign-within-math-expression.png) + + - Outside a math expression, but on the same line, use span tags around the explicit `$`. + + ``` + To split $100 in half, we calculate $100/2$ + ``` + + ![Dollar sign inline math expression](/assets/images/help/writing/dollar-sign-inline-math-expression.png) + +## Further reading + +* [The MathJax website](http://mathjax.org) +* [Getting started with writing and formatting on GitHub](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github) +* [GitHub Flavored Markdown Spec](https://github.github.com/gfm/) diff --git a/content/github/copilot/about-github-copilot-telemetry.md b/content/github/copilot/about-github-copilot-telemetry.md index 4b8db2affa..9b9248a610 100644 --- a/content/github/copilot/about-github-copilot-telemetry.md +++ b/content/github/copilot/about-github-copilot-telemetry.md @@ -9,7 +9,7 @@ versions: ## What data is collected -Data collected is described in the "[{% data variables.product.prodname_copilot %} Telemetry Terms](/github/copilot/github-copilot-telemetry-terms)." In addition, the {% data variables.product.prodname_copilot %} extension/plugin collects activity from the user's Integrated Development Environment (IDE), tied to a timestamp, and metadata collected by the extension/plugin telemetry package. When used with Visual Studio Code, IntelliJ, NeoVIM, or other IDEs, {% data variables.product.prodname_copilot %} collects the standard metadata provided by those IDEs. +Data collected is described in the "[{% data variables.product.prodname_copilot %} Telemetry Terms](/github/copilot/github-copilot-telemetry-terms)." In addition, the {% data variables.product.prodname_copilot %} extension/plugin collects activity from the user's Integrated Development Environment (IDE), tied to a timestamp, and metadata collected by the extension/plugin telemetry package. When used with {% data variables.product.prodname_vscode %}, IntelliJ, NeoVIM, or other IDEs, {% data variables.product.prodname_copilot %} collects the standard metadata provided by those IDEs. ## How the data is used by {% data variables.product.company_short %} diff --git a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md index 8ef74e1919..df592acef0 100644 --- a/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md +++ b/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md @@ -29,8 +29,8 @@ You can also use the "Filter cards" search bar at the top of each project board - Filter by check status using `status:pending`, `status:success`, or `status:failure` - Filter cards by type using `type:issue`, `type:pr`, or `type:note` - Filter cards by state and type using `is:open`, `is:closed`, or `is:merged`; and `is:issue`, `is:pr`, or `is:note` -- Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr`{% ifversion fpt or ghes or ghae or ghec %} -- Filter cards by repository in an organization-wide project board using `repo:ORGANIZATION/REPOSITORY`{% endif %} +- Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr` +- Filter cards by repository in an organization-wide project board using `repo:ORGANIZATION/REPOSITORY` 1. Navigate to the project board that contains the cards you want to filter. 2. Above the project card columns, click into the "Filter cards" search bar and type a search query to filter the cards. diff --git a/content/issues/tracking-your-work-with-issues/about-issues.md b/content/issues/tracking-your-work-with-issues/about-issues.md index a60eaf166a..7bd3da9292 100644 --- a/content/issues/tracking-your-work-with-issues/about-issues.md +++ b/content/issues/tracking-your-work-with-issues/about-issues.md @@ -21,7 +21,7 @@ topics: Issues let you track your work on {% data variables.product.company_short %}, where development happens. When you mention an issue in another issue or pull request, the issue's timeline reflects the cross-reference so that you can keep track of related work. To indicate that work is in progress, you can link an issue to a pull request. When the pull request merges, the linked issue automatically closes. -For more information on keywords, see "[Linking a pull request to an issue](issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)." +For more information on keywords, see "[Linking a pull request to an issue](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)." ## Quickly create issues @@ -35,7 +35,7 @@ For more information about projects, see {% ifversion fpt or ghec %}"[About proj ## Stay up to date -To stay updated on the most recent comments in an issue, you can subscribe to an issue to receive notifications about the latest comments. To quickly find links to recently updated issues you're subscribed to, visit your dashboard. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}" and "[About your personal dashboard](/articles/about-your-personal-dashboard)." +To stay updated on the most recent comments in an issue, you can subscribe to an issue to receive notifications about the latest comments. To quickly find links to recently updated issues you're subscribed to, visit your dashboard. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[About your personal dashboard](/articles/about-your-personal-dashboard)." ## Community management diff --git a/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index cf85394183..5c162949b5 100644 --- a/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -178,11 +178,9 @@ With issue and pull request search terms, you can: {% endtip %} {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} For issues, you can also use search to: - Filter for issues that are linked to a pull request by a closing reference: `linked:pr` -{% endif %} For pull requests, you can also use search to: - Filter [draft](/articles/about-pull-requests#draft-pull-requests) pull requests: `is:draft` @@ -193,8 +191,8 @@ For pull requests, you can also use search to: - Filter pull requests by [reviewer](/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 %} -- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %} -- Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue`{% endif %} +- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/atom` +- Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue` ## Sorting issues and pull requests @@ -217,7 +215,6 @@ You can sort any filtered view by: To clear your sort selection, click **Sort** > **Newest**. - ## Sharing filters When you filter or sort issues and pull requests, your browser's URL is automatically updated to match the new view. diff --git a/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md index 2f4e2d02b8..479c147c68 100644 --- a/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ b/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md @@ -26,7 +26,7 @@ shortTitle: Link PR to issue ## About linked issues and pull requests -You can link an issue to a pull request {% ifversion fpt or ghes or ghae or ghec %}manually or {% endif %}using a supported keyword in the pull request description. +You can link an issue to a pull request manually or using a supported keyword in the pull request description. When you link a pull request to the issue the pull request addresses, collaborators can see that someone is working on the issue. @@ -56,11 +56,10 @@ Issue in the same repository | *KEYWORD* #*ISSUE-NUMBER* | `Closes #10` Issue in a different repository | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100` Multiple issues | Use full syntax for each issue | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` -{% ifversion fpt or ghes or ghae or ghec %}Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword.{% endif %} +Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword. You can also use closing keywords in a commit message. The issue will be closed when you merge the commit into the default branch, but the pull request that contains the commit will not be listed as a linked pull request. -{% ifversion fpt or ghes or ghae or ghec %} ## Manually linking a pull request to an issue Anyone with write permissions to a repository can manually link a pull request to an issue. @@ -78,7 +77,6 @@ You can manually link up to ten issues to each pull request. The issue and pull {% endif %} 5. Click the issue you want to link to the pull request. ![Drop down to link issue](/assets/images/help/pull_requests/link-issue-drop-down.png) -{% endif %} ## Further reading diff --git a/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md b/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md index 45ac72dd0d..50a36dcf69 100644 --- a/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md +++ b/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md @@ -26,4 +26,4 @@ Your issues and pull request dashboards are available at the top of any page. On ## Further reading -- {% 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 %}" +- "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching)" diff --git a/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md index cb6bcf0755..b22365e690 100644 --- a/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md +++ b/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -35,7 +35,7 @@ In the left sidebar of your dashboard, you can access your organization's top re In the "All activity" section of your news feed, you can view updates from other teams and repositories in your organization. -The "All activity" section shows all recent activity in the organization, including activity in repositories you're not subscribed to and of people you're not following. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Watching and unwatching repositories](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}" and "[Following people](/articles/following-people)." +The "All activity" section shows all recent activity in the organization, including activity in repositories you're not subscribed to and of people you're not following. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[Following people](/articles/following-people)." For instance, the organization news feed shows updates when someone in the organization: - Creates a new branch. diff --git a/content/organizations/collaborating-with-your-team/about-team-discussions.md b/content/organizations/collaborating-with-your-team/about-team-discussions.md index 04845b1e72..aa01ec69db 100644 --- a/content/organizations/collaborating-with-your-team/about-team-discussions.md +++ b/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -32,7 +32,7 @@ When someone posts or replies to a public discussion on a team's page, members o {% tip %} -**Tip:** Depending on your notification settings, you'll receive updates by email, the web notifications page on {% data variables.product.product_name %}, or both. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications)" and "[About web notifications](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}." +**Tip:** Depending on your notification settings, you'll receive updates by email, the web notifications page on {% data variables.product.product_name %}, or both. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)." {% endtip %} @@ -40,7 +40,7 @@ By default, if your username is mentioned in a team discussion, you'll receive n To turn off notifications for team discussions, you can unsubscribe to a specific discussion post or change your notification settings to unwatch or completely ignore a specific team's discussions. You can subscribe to notifications for a specific discussion post even if you're unwatching that team's discussions. -For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Subscribing to and unsubscribing from notifications](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" and "[Nested teams](/articles/about-teams/#nested-teams)." +For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)" and "[Nested teams](/articles/about-teams/#nested-teams)." {% ifversion fpt or ghec %} diff --git a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md index 8fd6ad0d77..31574c549c 100644 --- a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md +++ b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md @@ -162,5 +162,5 @@ You can manage access to {% data variables.product.prodname_GH_advanced_security - "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %} - "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %} -- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae-issue-4864 %} +- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae %} - "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)"{% endif %} diff --git a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index 40c99ceccc..401665144c 100644 --- a/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -41,7 +41,7 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing. | [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. | -| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %} | [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/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.{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %} | [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." @@ -61,8 +61,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | {% endif %} | [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion ghec %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %} -| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} +| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %} +| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization. | [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps. | [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %} | [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} @@ -75,7 +75,7 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae or ghec %} | [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% if secret-scanning-audit-log-custom-patterns %} | [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %} | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %} | [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% if custom-repository-roles %} | [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %} @@ -236,7 +236,7 @@ An overview of some of the most common actions that are recorded as events in th | `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{% ifversion fpt or ghec or ghes > 3.2 or ghae %} ### `dependabot_alerts` category actions | Action | Description @@ -497,7 +497,6 @@ For more information, see "[Managing the publication of {% data variables.produc | `delete` | Triggered when a custom pattern is removed from secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)." {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} ### `organization_label` category actions | Action | Description @@ -506,8 +505,6 @@ For more information, see "[Managing the publication of {% data variables.produc | `update` | Triggered when a default label is edited. | `destroy` | Triggered when a default label is deleted. -{% endif %} - ### `oauth_application` category actions | Action | Description @@ -572,11 +569,10 @@ For more information, see "[Managing the publication of {% data variables.produc | `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch. | `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed. | `rejected_ref_update ` | Triggered when a branch update attempt is rejected. -| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.{% ifversion fpt or ghes or ghae or ghec %} +| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator. | `update_allow_force_pushes_enforcement_level ` | Triggered when force pushes are enabled or disabled for a protected branch. | `update_allow_deletions_enforcement_level ` | Triggered when branch deletion is enabled or disabled for a protected branch. | `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch. -{% endif %} {% ifversion fpt or ghes > 3.1 or ghae or ghec %} @@ -707,7 +703,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a repository. -{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% endif %}{% ifversion fpt or ghes or ghae or ghec %} ### `repository_vulnerability_alert` category actions | Action | Description diff --git a/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index 0a30561f90..b066eaede4 100644 --- a/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -152,18 +152,18 @@ Some of the features listed below are limited to organizations using {% data var In this section, you can find the access required for security features, such as {% data variables.product.prodname_advanced_security %} features. | Repository action | Read | Triage | Write | Maintain | Admin | -|:---|:---:|:---:|:---:|:---:|:---:| {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +|:---|:---:|:---:|:---:|:---:|:---:| {% ifversion fpt or ghes or ghae or ghec %} | Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | -| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %} +| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} | Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 or ghec %} +| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae or ghec %} | [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %} | [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | | [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | | [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} -| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %} +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **X** |{% endif %} [1] Repository writers and maintainers can only see alert information for their own commits. diff --git a/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md b/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md index 3e53f6b979..9ac00d4bc7 100644 --- a/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md +++ b/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md @@ -5,8 +5,6 @@ permissions: Organization owners can export member information for their organiz versions: fpt: '*' ghec: '*' - ghes: '>=3.3' - ghae: issue-5146 topics: - Organizations - Teams diff --git a/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md index 8c989dfce9..8111066c71 100644 --- a/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md +++ b/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -26,8 +26,8 @@ shortTitle: Convert organization to user 2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner). 3. {% data variables.product.signin_link %} to the new personal account. 4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new personal account. -5. [Rename the organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) to make the current username available. -6. [Rename the user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) to the organization's name. +5. [Rename the organization](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username) to make the current username available. +6. [Rename the user](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username) to the organization's name. 7. [Delete the organization](/organizations/managing-organization-settings/deleting-an-organization-account). diff --git a/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md index 256e5a43c6..8e51209f92 100644 --- a/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md +++ b/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md @@ -139,7 +139,7 @@ Some of the features listed below are limited to organizations using {% data var | Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)") | **X** | | | | |{% endif %} | Manage pull request reviews in the organization (see "[Managing pull request reviews in your organization](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)") | **X** | | | | | -{% elsif ghes > 3.2 or ghae-issue-4999 %} +{% elsif ghes > 3.2 or ghae %} | Organization action | Owners | Members | Security managers | diff --git a/content/organizations/organizing-members-into-teams/about-teams.md b/content/organizations/organizing-members-into-teams/about-teams.md index 052dc5b6af..a48986bd53 100644 --- a/content/organizations/organizing-members-into-teams/about-teams.md +++ b/content/organizations/organizing-members-into-teams/about-teams.md @@ -37,7 +37,7 @@ You can also use LDAP Sync to synchronize {% data variables.product.product_loca {% data reusables.organizations.types-of-team-visibility %} -You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)." +You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)." ## Team pages diff --git a/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md b/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md index d398fdffce..70ebd9df35 100644 --- a/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md +++ b/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md @@ -31,11 +31,10 @@ People with the team maintainer role can manage team membership and settings. - [Delete team discussions](/articles/managing-disruptive-comments/#deleting-a-comment) - [Add organization members to the team](/articles/adding-organization-members-to-a-team) - [Remove organization members from the team](/articles/removing-organization-members-from-a-team) -- Remove the team's access to repositories{% ifversion fpt or ghes or ghae or ghec %} -- [Manage code review assignment for the team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% ifversion fpt or ghec %} +- Remove the team's access to repositories +- [Manage code review assignment for the team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% ifversion fpt or ghec %} - [Manage scheduled reminders for pull requests](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %} - ## Promoting an organization member to team maintainer Before you can promote an organization member to team maintainer, the person must already be a member of the team. diff --git a/content/pages/index.md b/content/pages/index.md index ef3f74412d..5d69134c3a 100644 --- a/content/pages/index.md +++ b/content/pages/index.md @@ -1,7 +1,34 @@ --- title: GitHub Pages Documentation shortTitle: GitHub Pages -intro: 'You can create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.' +intro: 'Learn how to create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Explore website building tools like Jekyll and troubleshoot issues with your {% data variables.product.prodname_pages %} site.' +introLinks: + quickstart: /pages/quickstart + overview: /pages/getting-started-with-github-pages/about-github-pages +featuredLinks: + guides: + - /pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site + - /pages/getting-started-with-github-pages/creating-a-github-pages-site + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll{% endif %}' + - '{% ifversion ghec %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site{% endif %}' + - '{% ifversion fpt %}/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll{% endif %}' + popular: + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages{% endif %}' + - /pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll) + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages{% endif %}' + - '{% ifversion fpt or ghec %}/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https{% endif %}' + - '{% ifversion ghes or ghae %}/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll{% endif %}' + guideCards: + - /pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site + - /pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll + - /pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites +changelog: + label: pages +layout: product-landing redirect_from: - /categories/20/articles - /categories/95/articles @@ -23,5 +50,4 @@ children: - /getting-started-with-github-pages - /setting-up-a-github-pages-site-with-jekyll - /configuring-a-custom-domain-for-your-github-pages-site ---- - +--- \ No newline at end of file diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md index e93f69bfd4..0f99b32644 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -51,7 +51,7 @@ People with write permissions for a repository can add a theme to a {% data vari --- --- - @import "{{ site.theme }}"; + @import "{% raw %}{{ site.theme }}{% endraw %}"; ``` 3. Add any custom CSS or Sass (including imports) you'd like immediately after the `@import` line. diff --git a/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md index cdec1046a8..f6b0db8135 100644 --- a/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md +++ b/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md @@ -23,13 +23,17 @@ topics: ### Merge message for a squash merge -When you squash and merge, {% data variables.product.prodname_dotcom %} generates a commit message which you can change if you want to. The message default depends on whether the pull request contains multiple commits or just one. We do not include merge commits when we count the total number of commits. +When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. The default message depends on the number of commits in the pull request, not including merge commits. Number of commits | Summary | Description | ----------------- | ------- | ----------- | One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order +{% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %} +People with admin access to a repository can configure the repository to use the title of the pull request as the default merge message for all squashed commits. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)". +{% endif %} + ### Squashing and merging a long-running branch If you plan to continue work on the [head branch](/github/getting-started-with-github/github-glossary#head-branch) of a pull request after the pull request is merged, we recommend you don't squash and merge the pull request. diff --git a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md index a260cbbe84..4f8797dc68 100644 --- a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md +++ b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md @@ -1,6 +1,6 @@ --- title: Changing the stage of a pull request -intro: 'You can mark a draft pull request as ready for review{% ifversion fpt or ghae or ghes or ghec %} or convert a pull request to a draft{% endif %}.' +intro: You can mark a draft pull request as ready for review or convert a pull request to a draft. permissions: People with write permissions to a repository and pull request authors can change the stage of a pull request. product: '{% data reusables.gated-features.draft-prs %}' redirect_from: @@ -21,21 +21,17 @@ shortTitle: Change the state {% data reusables.pull_requests.mark-ready-review %} -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Tip**: You can also mark a pull request as ready for review using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)" in the {% data variables.product.prodname_cli %} documentation. {% endtip %} -{% endif %} {% data reusables.repositories.sidebar-pr %} 2. In the "Pull requests" list, click the pull request you'd like to mark as ready for review. 3. In the merge box, click **Ready for review**. ![Ready for review button](/assets/images/help/pull_requests/ready-for-review-button.png) -{% ifversion fpt or ghae or ghes or ghec %} - ## Converting a pull request to a draft You can convert a pull request to a draft at any time. For example, if you accidentally opened a pull request instead of a draft, or if you've received feedback on your pull request that needs to be addressed, you can convert the pull request to a draft to indicate further changes are needed. No one can merge the pull request until you mark the pull request as ready for review again. People who are already subscribed to notifications for the pull request will not be unsubscribed when you convert the pull request to a draft. @@ -47,8 +43,6 @@ You can convert a pull request to a draft at any time. For example, if you accid 4. Click **Convert to draft**. ![Convert to draft confirmation](/assets/images/help/pull_requests/convert-to-draft-dialog.png) -{% endif %} - ## Further reading - "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)" diff --git a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md index 4ce18de40c..19b6706e34 100644 --- a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md +++ b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md @@ -21,7 +21,7 @@ Repositories belong to a personal account (a single individual owner) or an orga To assign a reviewer to a pull request, you will need write access to the repository. For more information about repository access, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." If you have write access, you can assign anyone who has read access to the repository as a reviewer. -Organization members with write access can also assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. {% ifversion fpt or ghae or ghes or ghec %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} +Organization members with write access can also assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." {% note %} diff --git a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md index 72a631d3b9..37fff36380 100644 --- a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md +++ b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md @@ -21,7 +21,7 @@ After a pull request is opened, anyone with *read* access can review and comment {% if pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %} -Repository owners and collaborators can request a pull request review from a specific person. Organization members can also request a pull request review from a team with read access to the repository. For more information, see "[Requesting a pull request review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." {% ifversion fpt or ghae or ghes or ghec %}You can specify a subset of team members to be automatically assigned in the place of the whole team. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} +Repository owners and collaborators can request a pull request review from a specific person. Organization members can also request a pull request review from a team with read access to the repository. For more information, see "[Requesting a pull request review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." You can specify a subset of team members to be automatically assigned in the place of the whole team. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." Reviews allow for discussion of proposed changes and help ensure that the changes meet the repository's contributing guidelines and other quality standards. You can define which individuals or teams own certain types or areas of code in a CODEOWNERS file. When a pull request modifies code that has a defined owner, that individual or team will automatically be requested as a reviewer. For more information, see "[About code owners](/articles/about-code-owners/)." diff --git a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 36ff4cc7d1..baea88ca85 100644 --- a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -5,7 +5,7 @@ product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md b/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md index 59d1f77e29..7d5654b4d3 100644 --- a/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md +++ b/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md @@ -30,10 +30,10 @@ Here's an example of a [comparison between two branches](https://github.com/octo ## Comparing tags -Comparing release tags will show you changes to your repository since the last release. {% ifversion fpt or ghae or ghes or ghec %} -For more information, see "[Comparing releases](/github/administering-a-repository/comparing-releases)."{% endif %} +Comparing release tags will show you changes to your repository since the last release. +For more information, see "[Comparing releases](/github/administering-a-repository/comparing-releases)." -{% ifversion fpt or ghae or ghes or ghec %}To compare tags, you can select a tag name from the `compare` drop-down menu at the top of the page.{% else %} Instead of typing a branch name, type the name of your tag in the `compare` drop down menu.{% endif %} +To compare tags, you can select a tag name from the `compare` drop-down menu at the top of the page. Here's an example of a [comparison between two tags](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3). diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md b/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md index ce2d25bd63..6e4262001a 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md @@ -26,8 +26,7 @@ shortTitle: About merge methods {% data reusables.pull_requests.default_merge_option %} -{% ifversion fpt or ghae or ghes or ghec %} -The default merge method creates a merge commit. You can prevent anyone from pushing merge commits to a protected branch by enforcing a linear commit history. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-linear-history)."{% endif %} +The default merge method creates a merge commit. You can prevent anyone from pushing merge commits to a protected branch by enforcing a linear commit history. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-linear-history)." ## Squashing your merge commits diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md index 249403b393..a3554ebd90 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md @@ -68,11 +68,11 @@ When you create a branch rule, the branch you specify doesn't have to exist yet - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)." ![Require review from code owners](/assets/images/help/repository/PR-review-required-code-owner.png) {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5611 %} - - Optionally, to allow specific people or teams to push code to the branch without creating pull requests when they're required, select **Allow specific actors to bypass required pull requests**. Then, search for and select the people or teams who should be allowed to skip creating a pull request. - ![Allow specific actors to bypass pull request requirements checkbox](/assets/images/help/repository/PR-bypass-requirements.png) + - Optionally, to allow specific actors to push code to the branch without creating pull requests when they're required, select **Allow specified actors to bypass required pull requests**. Then, search for and select the actors who should be allowed to skip creating a pull request. + ![Allow specific actors to bypass pull request requirements checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-bypass-requirements-with-apps.png){% else %}(/assets/images/help/repository/PR-bypass-requirements.png){% endif %} {% endif %} - - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." - ![Restrict who can dismiss pull request reviews checkbox](/assets/images/help/repository/PR-review-required-dismissals.png) + - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the actors who are allowed to dismiss pull request reviews. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." + ![Restrict who can dismiss pull request reviews checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-review-required-dismissals-with-apps.png){% else %}(/assets/images/help/repository/PR-review-required-dismissals.png){% endif %} 1. Optionally, enable required status checks. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." - Select **Require status checks to pass before merging**. ![Required status checks option](/assets/images/help/repository/required-status-checks.png) @@ -115,8 +115,8 @@ When you create a branch rule, the branch you specify doesn't have to exist yet {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5624 %} Then, choose who can force push to the branch. - Select **Everyone** to allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions. - - Select **Specify who can force push** to allow only specific people or teams to force push to the branch. Then, search for and select those people or teams. - ![Screenshot of the options to specify who can force push](/assets/images/help/repository/allow-force-pushes-specify-who.png) + - Select **Specify who can force push** to allow only specific actors to force push to the branch. Then, search for and select those actors. + ![Screenshot of the options to specify who can force push]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png){% else %}(/assets/images/help/repository/allow-force-pushes-specify-who.png){% endif %} {% endif %} For more information about force pushes, see "[Allow force pushes](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)." diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md index c1cc5636b9..c3b91a9c2a 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md @@ -36,14 +36,11 @@ remote: error: Required status check "ci-build" is failing {% endnote %} -{% ifversion fpt or ghae or ghes or ghec %} - ## Conflicts between head commit and test merge commit Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, the test merge commit must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)." ![Branch with conflicting merge commits](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) -{% endif %} ## Handling skipped but required checks diff --git a/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md index a8a463dce3..af0fdbf058 100644 --- a/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md +++ b/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md @@ -25,19 +25,17 @@ topics: {% endtip %} -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Tip**: You can also create a repository using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation. {% endtip %} -{% endif %} {% data reusables.repositories.create_new %} 2. Optionally, to create a repository with the directory structure and files of an existing repository, use the **Choose a template** drop-down and select a template repository. You'll see template repositories that are owned by you and organizations you're a member of or that you've used before. For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)." - ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %} + ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png) 3. Optionally, if you chose to use a template, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**. - ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} + ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png) 3. In the Owner drop-down, select the account you wish to create the repository on. ![Owner drop-down menu](/assets/images/help/repository/create-repository-owner.png) {% data reusables.repositories.repo-name %} diff --git a/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md index 280aa369a1..9bdef7e4d6 100644 --- a/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md +++ b/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md @@ -18,17 +18,13 @@ shortTitle: Create from a template Anyone with read permissions to a template repository can create a repository from that template. For more information, see "[Creating a template repository](/articles/creating-a-template-repository)." -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Tip**: You can also create a repository from a template using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation. {% endtip %} -{% endif %} -{% ifversion fpt or ghae or ghes or ghec %} You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches. -{% endif %} Creating a repository from a template is similar to forking a repository, but there are important differences: - A new fork includes the entire commit history of the parent repository, while a repository created from a template starts with a single commit. @@ -44,8 +40,8 @@ For more information about forks, see "[About forks](/pull-requests/collaboratin ![Use this template button](/assets/images/help/repository/use-this-template-button.png) {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} -{% data reusables.repositories.choose-repo-visibility %}{% ifversion fpt or ghae or ghes or ghec %} +{% data reusables.repositories.choose-repo-visibility %} 6. Optionally, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**. - ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} + ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png) {% data reusables.repositories.select-marketplace-apps %} 8. Click **Create repository from template**. diff --git a/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md b/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md index da56cb531b..c9281f3645 100644 --- a/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md +++ b/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md @@ -1,6 +1,6 @@ --- title: Creating a template repository -intro: 'You can make an existing repository a template, so you and others can generate new repositories with the same directory structure{% ifversion fpt or ghae or ghes or ghec %}, branches,{% endif %} and files.' +intro: 'You can make an existing repository a template, so you and others can generate new repositories with the same directory structure, branches, and files.' permissions: Anyone with admin permissions to a repository can make the repository a template. redirect_from: - /articles/creating-a-template-repository @@ -23,7 +23,7 @@ shortTitle: Create a template repo To create a template repository, you must create a repository, then make the repository a template. For more information about creating a repository, see "[Creating a new repository](/articles/creating-a-new-repository)." -After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% ifversion fpt or ghae or ghes or ghec %} They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)." +After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch. They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches. For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md index 67c8fece20..dbb15fcae3 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md @@ -30,7 +30,7 @@ Each email notification for a push to a repository lists the new commits and lin - The files that were changed as part of the commit - The commit message -You can filter email notifications you receive for pushes to a repository. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About notification emails](/github/receiving-notifications-about-activity-on-github/about-email-notifications)." You can also turn off email notifications for pushes. For more information, see "[Choosing the delivery method for your notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}." +You can filter email notifications you receive for pushes to a repository. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)." ## Enabling email notifications for pushes to your repository @@ -45,10 +45,5 @@ You can filter email notifications you receive for pushes to a repository. For m ![Setup notifications button](/assets/images/help/settings/setup_notifications_settings.png) ## Further reading -{% ifversion fpt or ghae or ghes or ghec %} - "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" -{% else %} -- "[About notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" -- "[Choosing the delivery method for your notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)" -- "[About email notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" -- "[About web notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)"{% endif %} + diff --git a/content/repositories/releasing-projects-on-github/about-releases.md b/content/repositories/releasing-projects-on-github/about-releases.md index 29261145b4..9c9f2fd285 100644 --- a/content/repositories/releasing-projects-on-github/about-releases.md +++ b/content/repositories/releasing-projects-on-github/about-releases.md @@ -31,7 +31,7 @@ Releases are deployable software iterations you can package and make available f Releases are based on [Git tags](https://git-scm.com/book/en/Git-Basics-Tagging), which mark a specific point in your repository's history. A tag date may be different than a release date since they can be created at different times. For more information about viewing your existing tags, see "[Viewing your repository's releases and tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)." -You can receive notifications when new releases are published in a repository without receiving notifications about other updates to the repository. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching releases for a repository](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}." +You can receive notifications when new releases are published in a repository without receiving notifications about other updates to the repository. For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)." Anyone with read access to a repository can view and compare releases, but only people with write permissions to a repository can manage releases. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)." @@ -39,6 +39,10 @@ Anyone with read access to a repository can view and compare releases, but only You can manually create release notes while managing a release. Alternatively, you can automatically generate release notes from a default template, or customize your own release notes template. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)." {% endif %} +{% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7054 %} +When viewing the details for a release, the creation date for each release asset is shown next to the release asset. +{% endif %} + {% ifversion fpt or ghec %} People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository)." @@ -47,7 +51,7 @@ If a release fixes a security vulnerability, you should publish a security advis You can view the **Dependents** tab of the dependency graph to see which repositories and packages depend on code in your repository, and may therefore be affected by a new release. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." {% endif %} -You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/rest/reference/repos#releases)." +You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/rest/reference/releases)." {% ifversion fpt or ghec %} ## Storage and bandwidth quotas diff --git a/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md index 393e6eb56c..630ebe1848 100644 --- a/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md +++ b/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md @@ -16,13 +16,11 @@ topics: - Repositories shortTitle: View releases & tags --- -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Tip**: You can also view a release using the {% data variables.product.prodname_cli %}. For more information, see "[`gh release view`](https://cli.github.com/manual/gh_release_view)" in the {% data variables.product.prodname_cli %} documentation. {% endtip %} -{% endif %} ## Viewing releases diff --git a/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md index 890f1e122a..f7c49e2573 100644 --- a/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md +++ b/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md @@ -66,7 +66,7 @@ Forks are listed alphabetically by the username of the person who forked the rep 3. In the left sidebar, click **Forks**. ![Forks tab](/assets/images/help/graphs/graphs-sidebar-forks-tab.png) -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Viewing the dependencies of a repository You can use the dependency graph to explore the code your repository depends on. diff --git a/content/rest/enterprise-admin/audit-log.md b/content/rest/enterprise-admin/audit-log.md index 7fa5096e21..d0c27c5eb8 100644 --- a/content/rest/enterprise-admin/audit-log.md +++ b/content/rest/enterprise-admin/audit-log.md @@ -5,6 +5,7 @@ versions: fpt: '*' ghes: '>=3.3' ghec: '*' + ghae: '*' topics: - API miniTocMaxHeadingLevel: 3 diff --git a/content/rest/guides/getting-started-with-the-checks-api.md b/content/rest/guides/getting-started-with-the-checks-api.md index 11f50ee872..3ae85111e2 100644 --- a/content/rest/guides/getting-started-with-the-checks-api.md +++ b/content/rest/guides/getting-started-with-the-checks-api.md @@ -41,9 +41,7 @@ A check run is an individual test that is part of a check suite. Each run includ ![Check runs workflow](/assets/images/check_runs.png) -{% ifversion fpt or ghes or ghae or ghec %} If a check run is in a incomplete state for more than 14 days, then the check run's `conclusion` becomes `stale` and appears on {% data variables.product.prodname_dotcom %} as stale with {% octicon "issue-reopened" aria-label="The issue-reopened icon" %}. Only {% data variables.product.prodname_dotcom %} can mark check runs as `stale`. For more information about possible conclusions of a check run, see the [`conclusion` parameter](/rest/reference/checks#create-a-check-run--parameters). -{% endif %} As soon as you receive the [`check_suite`](/webhooks/event-payloads/#check_suite) webhook, you can create the check run, even if the check is not complete. You can update the `status` of the check run as it completes with the values `queued`, `in_progress`, or `completed`, and you can update the `output` as more details become available. A check run can contain timestamps, a link to more details on your external site, detailed annotations for specific lines of code, and information about the analysis performed. diff --git a/content/rest/guides/getting-started-with-the-rest-api.md b/content/rest/guides/getting-started-with-the-rest-api.md index 4791afc212..726026840e 100644 --- a/content/rest/guides/getting-started-with-the-rest-api.md +++ b/content/rest/guides/getting-started-with-the-rest-api.md @@ -148,7 +148,7 @@ When authenticating, you should see your rate limit bumped to 5,000 requests an You can easily [create a **personal access token**][personal token] using your [Personal access tokens settings page][tokens settings]: -{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} {% warning %} To help keep your information secure, we highly recommend setting an expiration for your personal access tokens. @@ -164,7 +164,7 @@ To help keep your information secure, we highly recommend setting an expiration ![Personal Token selection](/assets/images/help/personal_token_ghae.png) {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} API requests using an expiring personal access token will return that token's expiration date via the `GitHub-Authentication-Token-Expiration` header. You can use the header in your scripts to provide a warning message when the token is close to its expiration date. {% endif %} diff --git a/content/rest/overview/libraries.md b/content/rest/overview/libraries.md index cb5063dcbd..7d9ef972f2 100644 --- a/content/rest/overview/libraries.md +++ b/content/rest/overview/libraries.md @@ -144,6 +144,7 @@ Warning: As of late October 2021, the offical Octokit libraries are not currentl | Library name | Repository | |---|---| |**Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab)| +|**Octocat**|[octocat-rs/octocat-rs](https://github.com/octocat-rs/octocat-rs)| ### Scala diff --git a/content/rest/overview/resources-in-the-rest-api.md b/content/rest/overview/resources-in-the-rest-api.md index 1f7b2c54ac..7a2f660515 100644 --- a/content/rest/overview/resources-in-the-rest-api.md +++ b/content/rest/overview/resources-in-the-rest-api.md @@ -133,7 +133,7 @@ You will be unable to authenticate using your OAuth2 key and secret while in pri {% ifversion fpt or ghec %} -Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). +Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-apps). {% endif %} diff --git a/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md index b812221e4e..0174fae54a 100644 --- a/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md +++ b/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md @@ -86,7 +86,6 @@ If your search query contains whitespace, you will need to surround it with quot Some non-alphanumeric symbols, such as spaces, are dropped from code search queries within quotation marks, so results can be unexpected. -{% ifversion fpt or ghes or ghae or ghec %} ## Queries with usernames If your search query contains a qualifier that requires a username, such as `user`, `actor`, or `assignee`, you can use any {% data variables.product.product_name %} username, to specify a specific person, or `@me`, to specify the current user. @@ -97,4 +96,3 @@ Query | Example `QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) matches issues assigned to the person viewing the results You can only use `@me` with a qualifier and not as search term, such as `@me main.workflow`. -{% endif %} diff --git a/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/content/search-github/searching-on-github/searching-issues-and-pull-requests.md index dd17c6fc17..0ab2490764 100644 --- a/content/search-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -54,15 +54,12 @@ To search issues and pull requests in all repositories owned by a certain user o {% data reusables.pull_requests.large-search-workaround %} - | Qualifier | Example | ------------- | ------------- | user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) matches issues with the word "ubuntu" from repositories owned by @defunkt. | org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) matches issues in repositories owned by the GitHub organization. | repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) matches issues from @mozilla's shumway project that were created before March 2012. - - ## Search by open or closed state You can filter issues and pull requests based on whether they're open or closed using the `state` or `is` qualifier. @@ -136,7 +133,6 @@ You can use the `involves` qualifier to find issues that in some way involve a c | involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** matches issues either @defunkt or @jlord are involved in. | | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) matches issues @mdo is involved in that do not contain the word "bootstrap" in the body. -{% ifversion fpt or ghes or ghae or ghec %} ## Search for linked issues and pull requests You can narrow your results to only include issues that are linked to a pull request by a closing reference, or pull requests that are linked to an issue that the pull request may close. @@ -145,7 +141,7 @@ You can narrow your results to only include issues that are linked to a pull req | `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) matches open issues in the `desktop/desktop` repository that are linked to a pull request by a closing reference. | | `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) matches closed pull requests in the `desktop/desktop` repository that were linked to an issue that the pull request may have closed. | | `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) matches open issues in the `desktop/desktop` repository that are not linked to a pull request by a closing reference. | -| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) matches open pull requests in the `desktop/desktop` repository that are not linked to an issue that the pull request may close. |{% endif %} +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) matches open pull requests in the `desktop/desktop` repository that are not linked to an issue that the pull request may close. | ## Search by label @@ -243,10 +239,9 @@ You can filter issues and pull requests by the number of reactions using the `re You can filter for draft pull requests. For more information, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)." | Qualifier | Example -| ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %} +| ------------- | ------------- | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) matches draft pull requests. -| `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) matches pull requests that are ready for review.{% else %} -| `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) matches draft pull requests.{% endif %} +| `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) matches pull requests that are ready for review. ## Search by pull request review status and reviewer diff --git a/content/site-policy/github-terms/github-community-guidelines.md b/content/site-policy/github-terms/github-community-guidelines.md index cbca920b27..763291de97 100644 --- a/content/site-policy/github-terms/github-community-guidelines.md +++ b/content/site-policy/github-terms/github-community-guidelines.md @@ -39,7 +39,7 @@ While some disagreements can be resolved with direct, respectful communication b * **Communicate expectations** - Maintainers can set community-specific guidelines to help users understand how to interact with their projects, for example, in a repository’s README, [CONTRIBUTING file](/articles/setting-guidelines-for-repository-contributors/), or [dedicated code of conduct](/articles/adding-a-code-of-conduct-to-your-project/). You can find additional information on building communities [here](/communities). -* **Moderate Comments** - Users with [write-access privileges](/articles/repository-permission-levels-for-an-organization/) for a repository can [edit, delete, or hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) on commits, pull requests, and issues. Anyone with read access to a repository can view a comment's edit history. Comment authors and people with write access to a repository can also delete sensitive information from a [comment's edit history](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment). Moderating your projects can feel like a big task if there is a lot of activity, but you can [add collaborators](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) to assist you in managing your community. +* **Moderate Comments** - Users with [write-access privileges](/articles/repository-permission-levels-for-an-organization/) for a repository can [edit, delete, or hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) on commits, pull requests, and issues. Anyone with read access to a repository can view a comment's edit history. Comment authors and people with write access to a repository can also delete sensitive information from a [comment's edit history](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment). Moderating your projects can feel like a big task if there is a lot of activity, but you can [add collaborators](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) to assist you in managing your community. * **Lock Conversations**  - If a discussion in an issue, pull request, or commit gets out of hand, off topic, or violates your project’s code of conduct or GitHub’s policies, owners, collaborators, and anyone else with write access can put a temporary or permanent [lock](/articles/locking-conversations/) on the conversation. diff --git a/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md b/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md index 5c84b46a70..1c0e2c9a1e 100644 --- a/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md +++ b/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md @@ -16,8 +16,8 @@ Use of GitHub Codespaces is subject to the [GitHub Privacy Statement](/github/si Activity on github.dev is subject to [GitHub's Beta Previews terms](/github/site-policy/github-terms-of-service#j-beta-previews) -## Using Visual Studio Code +## Using {% data variables.product.prodname_vscode %} -GitHub Codespaces and github.dev allow for use of Visual Studio Code in the web browser. When using Visual Studio Code in the web browser, some telemetry collection is enabled by default and is [explained in detail on the Visual Studio Code website](https://code.visualstudio.com/docs/getstarted/telemetry). Users can opt out of telemetry by going to File > Preferences > Settings under the top left menu. +GitHub Codespaces and github.dev allow for use of {% data variables.product.prodname_vscode %} in the web browser. When using {% data variables.product.prodname_vscode_shortname %} in the web browser, some telemetry collection is enabled by default and is [explained in detail on the {% data variables.product.prodname_vscode_shortname %} website](https://code.visualstudio.com/docs/getstarted/telemetry). Users can opt out of telemetry by going to File > Preferences > Settings under the top left menu. -If a user chooses to opt out of telemetry capture in Visual Studio Code while inside of a codespace as outlined, this will sync the disable telemetry preference across all future web sessions in GitHub Codespaces and github.dev. +If a user chooses to opt out of telemetry capture in {% data variables.product.prodname_vscode_shortname %} while inside of a codespace as outlined, this will sync the disable telemetry preference across all future web sessions in GitHub Codespaces and github.dev. diff --git a/content/site-policy/privacy-policies/github-privacy-statement.md b/content/site-policy/privacy-policies/github-privacy-statement.md index b1c3fa8608..f5e67a86f1 100644 --- a/content/site-policy/privacy-policies/github-privacy-statement.md +++ b/content/site-policy/privacy-policies/github-privacy-statement.md @@ -65,7 +65,7 @@ We require some basic information at the time of account creation. When you crea #### Payment information If you sign on to a paid Account with us, send funds through the GitHub Sponsors Program, or buy an application on GitHub Marketplace, we collect your full name, address, and credit card information or PayPal information. Please note, GitHub does not process or store your credit card information or PayPal information, but our third-party payment processor does. -If you list and sell an application on [GitHub Marketplace](https://github.com/marketplace), we require your banking information. If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes. +If you list and sell an application on [GitHub Marketplace](https://github.com/marketplace), we require your banking information. If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes. #### Profile information You may choose to give us more information for your Account profile, such as your full name, an avatar which may include a photograph, your biography, your location, your company, and a URL to a third-party website. This information may include User Personal Information. Please note that your profile information may be visible to other Users of our Service. diff --git a/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md index 4918a84824..1e44b4bbff 100644 --- a/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md +++ b/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md @@ -19,7 +19,7 @@ topics: {% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)." -{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)." +{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)." {% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." diff --git a/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md index 0fb3ae74fb..e80ef26e64 100644 --- a/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md +++ b/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md @@ -16,7 +16,7 @@ shortTitle: Open source contributors ## Joining {% data variables.product.prodname_sponsors %} -{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)." +{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)." {% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." @@ -28,7 +28,7 @@ You can set a goal for your sponsorships. For more information, see "[Managing y ## Sponsorship tiers -{% data reusables.sponsors.tier-details %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)," "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization), and "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)." +{% data reusables.sponsors.tier-details %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)," "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization), and "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)." It's best to set up a range of different sponsorship options, including monthly and one-time tiers, to make it easy for anyone to support your work. In particular, one-time payments allow people to reward your efforts without worrying about whether their finances will support a regular payment schedule. diff --git a/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md index 74cf5d0d58..b6386717e9 100644 --- a/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md +++ b/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md @@ -11,7 +11,7 @@ versions: ghec: '*' children: - /about-github-sponsors-for-open-source-contributors - - /setting-up-github-sponsors-for-your-user-account + - /setting-up-github-sponsors-for-your-personal-account - /setting-up-github-sponsors-for-your-organization - /editing-your-profile-details-for-github-sponsors - /managing-your-sponsorship-goal diff --git a/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md index d8887ec3cd..c017f69b2c 100644 --- a/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -23,7 +23,7 @@ shortTitle: Set up for organization After you receive an invitation for your organization to join {% data variables.product.prodname_sponsors %}, you can complete the steps below to become a sponsored organization. -To join {% data variables.product.prodname_sponsors %} as an individual contributor outside an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)." +To join {% data variables.product.prodname_sponsors %} as an individual contributor outside an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)." {% data reusables.sponsors.navigate-to-github-sponsors %} {% data reusables.sponsors.view-eligible-accounts %} diff --git a/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md similarity index 96% rename from content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md rename to content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md index 6357dc2829..f8189cf379 100644 --- a/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md @@ -1,10 +1,11 @@ --- -title: Setting up GitHub Sponsors for your user account +title: Setting up GitHub Sponsors for your personal account intro: 'You can become a sponsored developer by joining {% data variables.product.prodname_sponsors %}, completing your sponsored developer profile, creating sponsorship tiers, submitting your bank and tax information, and enabling two-factor authentication for your account on {% data variables.product.product_location %}.' redirect_from: - /articles/becoming-a-sponsored-developer - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account + - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account versions: fpt: '*' ghec: '*' diff --git a/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md index c80c0cc92a..80cdb50e02 100644 --- a/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md +++ b/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md @@ -28,7 +28,7 @@ If you are a taxpayer in the United States, you must submit a [W-9](https://www. W-8 BEN and W-8 BEN-E tax forms help {% data variables.product.prodname_dotcom %} determine the beneficial owner of an amount subject to withholding. -If you are a taxpayer in any other region besides the United States, you must submit a [W-8 BEN](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf) (individual) or [W-8 BEN-E](https://www.irs.gov/forms-pubs/about-form-w-8-ben-e) (company) form before you can publish your {% data variables.product.prodname_sponsors %} profile. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-tax-information)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)." {% data variables.product.prodname_dotcom %} will send you the appropriate forms, notify you when they are due, and give you a reasonable amount of time to complete and send in the forms. +If you are a taxpayer in any other region besides the United States, you must submit a [W-8 BEN](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf) (individual) or [W-8 BEN-E](https://www.irs.gov/forms-pubs/about-form-w-8-ben-e) (company) form before you can publish your {% data variables.product.prodname_sponsors %} profile. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-tax-information)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)." {% data variables.product.prodname_dotcom %} will send you the appropriate forms, notify you when they are due, and give you a reasonable amount of time to complete and send in the forms. If you have been assigned an incorrect tax form, [contact {% data variables.product.prodname_dotcom %} Support](https://support.github.com/contact?form%5Bsubject%5D=GitHub%20Sponsors:%20tax%20form&tags=sponsors) to get reassigned the correct one for your situation. diff --git a/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md index fc3de06def..dabf0fcdcb 100644 --- a/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md +++ b/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md @@ -43,7 +43,7 @@ You can choose whether to display your sponsorship publicly. One-time sponsorshi If the sponsored account retires your tier, the tier will remain in place for you until you choose a different tier or cancel your subscription. For more information, see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)." -If the account you want to sponsor does not have a profile on {% data variables.product.prodname_sponsors %}, you can encourage the account to join. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." +If the account you want to sponsor does not have a profile on {% data variables.product.prodname_sponsors %}, you can encourage the account to join. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." {% data reusables.sponsors.sponsorships-not-tax-deductible %} diff --git a/data/features/integration-branch-protection-exceptions.yml b/data/features/integration-branch-protection-exceptions.yml new file mode 100644 index 0000000000..50d2e94a3a --- /dev/null +++ b/data/features/integration-branch-protection-exceptions.yml @@ -0,0 +1,7 @@ +# Reference: #6665 +# GitHub Apps are supported as actors in all types of exceptions to branch protections +versions: + fpt: '*' + ghec: '*' + ghes: '>= 3.6' + ghae: 'issue-6665' diff --git a/data/features/math.yml b/data/features/math.yml new file mode 100644 index 0000000000..82aceb6233 --- /dev/null +++ b/data/features/math.yml @@ -0,0 +1,7 @@ +# Issues 6054 +# Math support using LaTeX syntax +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.6' + ghae: 'issue-6054' diff --git a/data/features/security-managers.yml b/data/features/security-managers.yml index d168d91b5a..689f14c090 100644 --- a/data/features/security-managers.yml +++ b/data/features/security-managers.yml @@ -3,5 +3,5 @@ versions: fpt: '*' ghes: '>=3.3' - ghae: 'issue-4999' + ghae: '*' ghec: '*' diff --git a/data/features/security-overview-feature-specific-alert-page.yml b/data/features/security-overview-feature-specific-alert-page.yml new file mode 100644 index 0000000000..a3ac7515ce --- /dev/null +++ b/data/features/security-overview-feature-specific-alert-page.yml @@ -0,0 +1,7 @@ +# Reference: #7028. +# Documentation for feature-specific page for security overview at enterprise-level. +versions: + fpt: '*' + ghec: '*' + ghes: '>3.5' + ghae: 'issue-7028' diff --git a/data/graphql/ghae/schema.docs-ghae.graphql b/data/graphql/ghae/schema.docs-ghae.graphql index c632e5aaa0..7c045e5a11 100644 --- a/data/graphql/ghae/schema.docs-ghae.graphql +++ b/data/graphql/ghae/schema.docs-ghae.graphql @@ -5368,7 +5368,7 @@ input CreateBranchProtectionRuleInput { pattern: String! """ - A list of User, Team or App IDs allowed to push to matching branches. + A list of User, Team, or App IDs allowed to push to matching branches. """ pushActorIds: [ID!] @@ -39257,7 +39257,7 @@ input UpdateBranchProtectionRuleInput { pattern: String """ - A list of User, Team or App IDs allowed to push to matching branches. + A list of User, Team, or App IDs allowed to push to matching branches. """ pushActorIds: [ID!] diff --git a/data/graphql/ghec/schema.docs.graphql b/data/graphql/ghec/schema.docs.graphql index 8945408973..13d1e13def 100644 --- a/data/graphql/ghec/schema.docs.graphql +++ b/data/graphql/ghec/schema.docs.graphql @@ -5651,7 +5651,7 @@ input CreateBranchProtectionRuleInput { pattern: String! """ - A list of User, Team or App IDs allowed to push to matching branches. + A list of User, Team, or App IDs allowed to push to matching branches. """ pushActorIds: [ID!] @@ -45282,7 +45282,7 @@ input UpdateBranchProtectionRuleInput { pattern: String """ - A list of User, Team or App IDs allowed to push to matching branches. + A list of User, Team, or App IDs allowed to push to matching branches. """ pushActorIds: [ID!] diff --git a/data/graphql/schema.docs.graphql b/data/graphql/schema.docs.graphql index 8945408973..13d1e13def 100644 --- a/data/graphql/schema.docs.graphql +++ b/data/graphql/schema.docs.graphql @@ -5651,7 +5651,7 @@ input CreateBranchProtectionRuleInput { pattern: String! """ - A list of User, Team or App IDs allowed to push to matching branches. + A list of User, Team, or App IDs allowed to push to matching branches. """ pushActorIds: [ID!] @@ -45282,7 +45282,7 @@ input UpdateBranchProtectionRuleInput { pattern: String """ - A list of User, Team or App IDs allowed to push to matching branches. + A list of User, Team, or App IDs allowed to push to matching branches. """ pushActorIds: [ID!] diff --git a/data/release-notes/enterprise-server/3-1/21.yml b/data/release-notes/enterprise-server/3-1/21.yml new file mode 100644 index 0000000000..b6e1956267 --- /dev/null +++ b/data/release-notes/enterprise-server/3-1/21.yml @@ -0,0 +1,24 @@ +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - Packages have been updated to the latest security versions. + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not supported. + - Support bundles now include the row count of tables stored in MySQL. + 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 %} instance 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 {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} 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/data/release-notes/enterprise-server/3-2/13.yml b/data/release-notes/enterprise-server/3-2/13.yml new file mode 100644 index 0000000000..f5607682a0 --- /dev/null +++ b/data/release-notes/enterprise-server/3-2/13.yml @@ -0,0 +1,26 @@ +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - Packages have been updated to the latest security versions. + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - Videos uploaded to issue comments would not be rendered properly. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. + - Support bundles now include the row count of tables stored in MySQL. + - Dependency Graph can now be enabled without vulnerability data, allowing you to see what dependencies are in use and at what versions. Enabling Dependency Graph without enabling {% data variables.product.prodname_github_connect %} will **not** provide vulnerability information. + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} instance 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 {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - 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. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. diff --git a/data/release-notes/enterprise-server/3-3/8.yml b/data/release-notes/enterprise-server/3-3/8.yml new file mode 100644 index 0000000000..6372514d71 --- /dev/null +++ b/data/release-notes/enterprise-server/3-3/8.yml @@ -0,0 +1,33 @@ +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - Packages have been updated to the latest security versions. + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + - Videos uploaded to issue comments would not be rendered properly. + - When using the file finder on a repository page, typing the backspace key within the search field would result in search results being listed multiple times and cause rendering problems. + - When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events. + - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. + - Support bundles now include the row count of tables stored in MySQL. + - When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects. + - The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload. + 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. + - 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 {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - 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. + - 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.' + - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' diff --git a/data/release-notes/enterprise-server/3-4/2.yml b/data/release-notes/enterprise-server/3-4/2.yml index 4b631dfb51..f3a3aee274 100644 --- a/data/release-notes/enterprise-server/3-4/2.yml +++ b/data/release-notes/enterprise-server/3-4/2.yml @@ -79,6 +79,11 @@ sections: Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. To start a repository maintenance task manually, browse to `https:///stafftools/repositories///network` for each affected repository and click the Schedule button. - + + - heading: Theme picker for GitHub Pages has been removed + notes: + - | + The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)." + backups: - '{% data variables.product.prodname_ghe_server %} 3.4 requires at least [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).' diff --git a/data/release-notes/enterprise-server/3-4/3.yml b/data/release-notes/enterprise-server/3-4/3.yml new file mode 100644 index 0000000000..8c1ffa4ecb --- /dev/null +++ b/data/release-notes/enterprise-server/3-4/3.yml @@ -0,0 +1,40 @@ +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - Packages have been updated to the latest security versions. + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. + - When adding custom patterns and providing non-UTF8 test strings, match highlighting was incorrect. + - LDAP users with an underscore character (`_`) in their user names can now login successfully. + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - After enabling SAML encrypted assertions with Azure as identity provider, the sign in page would fail with a `500` error. + - Character key shortcut preferences weren't respected. + - Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + - Videos uploaded to issue comments would not be rendered properly. + - When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events. + - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - The Nomad allocation timeout for Dependency Graph has been increased to ensure post-upgrade migrations can complete. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. + - Support bundles now include the row count of tables stored in MySQL. + - When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects. + - The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload. + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} instance 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 {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - 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. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - | + When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11] + + To work around this problem, you can take one of the two following actions. + - Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute. + - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL. diff --git a/data/release-notes/enterprise-server/3-5/0-rc1.yml b/data/release-notes/enterprise-server/3-5/0-rc1.yml index df694f2041..ddebbe7a5d 100644 --- a/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -403,7 +403,12 @@ sections: # https://github.com/github/releases/issues/1632 - | The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, 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)." - + + - heading: Theme picker for GitHub Pages has been removed + notes: + - | + The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)." + known_issues: - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - Custom firewall rules are removed during the upgrade process. @@ -412,4 +417,4 @@ sections: - 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. - 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. - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. - - Actions services need to be restarted after restoring an appliance from a backup taken on a different host. + - Actions services need to be restarted after restoring an appliance from a backup taken on a different host. \ No newline at end of file diff --git a/data/release-notes/github-ae/2021-06/2021-12-06.yml b/data/release-notes/github-ae/2021-06/2021-12-06.yml index 76d38f7860..032bc1087a 100644 --- a/data/release-notes/github-ae/2021-06/2021-12-06.yml +++ b/data/release-notes/github-ae/2021-06/2021-12-06.yml @@ -1,7 +1,7 @@ date: '2021-12-06' friendlyDate: 'December 6, 2021' title: 'December 6, 2021' -currentWeek: true +currentWeek: false sections: features: - heading: 'Administration' diff --git a/data/release-notes/github-ae/2022-05/2022-05-17.yml b/data/release-notes/github-ae/2022-05/2022-05-17.yml new file mode 100644 index 0000000000..b8da1e31db --- /dev/null +++ b/data/release-notes/github-ae/2022-05/2022-05-17.yml @@ -0,0 +1,201 @@ +date: '2022-05-17' +friendlyDate: 'May 17, 2022' +title: 'May 17, 2022' +currentWeek: true +sections: + features: + - heading: 'GitHub Advanced Security features are generally available' + notes: + - | + Code scanning and secret scanning are now generally available for GitHub AE. For more information, see "[About code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)." + - | + Custom patterns for secret scanning is now generally available. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + + - heading: 'View all code scanning alerts for a pull request' + notes: + - | + You can now find all code scanning alerts associated with your pull request with the new pull request filter on the code scanning alerts page. The pull request checks page shows the alerts introduced in a pull request, but not existing alerts on the pull request branch. The new "View all branch alerts" link on the Checks page takes you to the code scanning alerts page with the specific pull request filter already applied, so you can see all the alerts associated with your pull request. This can be useful to manage lots of alerts, and to see more detailed information for individual alerts. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)." + + - heading: 'Security overview for organizations' + notes: + - | + GitHub Advanced Security now offers an organization-level view of the application security risks detected by code scanning, Dependabot, and secret scanning. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. + + In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + + ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) + + - heading: 'Dependency graph' + notes: + - | + Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." + + - heading: 'Dependabot alerts' + notes: + - | + Dependabot alerts can now notify you of vulnerabilities in your dependencies on GitHub AE. You can enable Dependabot alerts by enabling the dependency graph, enabling GitHub Connect, and syncing vulnerabilities from the GitHub Advisory Database. This feature is in beta and subject to change. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)." + + After you enable Dependabot alerts, members of your organization will receive notifications any time a new vulnerability that affects their dependencies is added to the GitHub Advisory Database or a vulnerable dependency is added to their manifest. Members can customize notification settings. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)." + + - heading: 'Security manager role for organizations' + notes: + - | + Organizations can now grant teams permission to manage security alerts and settings on all their repositories. The "security manager" role can be applied to any team and grants the team's members the following permissions. + + - Read access on all repositories in the organization + - Write access on all security alerts in the organization + - Access to the organization-level security tab + - Write access on security settings at the organization level + - Write access on security settings at the repository level + + For more information, see "[Managing security managers in your organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." + + - heading: 'Ephemeral runners and autoscaling webhooks for GitHub Actions' + notes: + - | + GitHub AE now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. + + Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, GitHub AE automatically unregisteres ephemeral runners, allowing you to perform any post-job management. + + You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to job requests from GitHub Actions. + + For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)." + + - heading: 'Composite actions for GitHub Actions' + notes: + - | + You can reduce duplication in your workflows by using composition to reference other actions. Previously, actions written in YAML could only use scripts. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)." + + - heading: 'New token scope for management of self-hosted runners' + notes: + - | + Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the `new manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to many REST API endpoints to manage your enterprise's self-hosted runners. + + - heading: 'Audit log accessible via REST API' + notes: + - | + You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." + + - heading: 'Expiration dates for personal access tokens' + notes: + - | + You can now set an expiration date on new and existing personal access tokens. GitHub AE will send you an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving you a duplicate token with the same properties as the original. When using a token with the GitHub AE API, you'll see a new header, `GitHub-Authentication-Token-Expiration`, indicating the token's expiration date. You can use this in scripts, for example to log a warning message as the expiration date approaches. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" and "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#using-personal-access-tokens)." + + - heading: 'Export a list of people with access to a repository' + notes: + - | + Organization owners can now export a list of the people with access to a repository in CSV format. For more information, see "[Viewing people with access to your repository](/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository#exporting-a-list-of-people-with-access-to-your-repository)." + + - heading: 'Improved management of code review assignments' + notes: + - | + New settings to manage code review assignment code review assignment help distribute a team's pull request review across the team members so reviews aren't the responsibility of just one or two team members. + + - Child team members: Limit assignment to only direct members of the team. Previously, team review requests could be assigned to direct members of the team or members of child teams. + - Count existing requests: Continue with automatic assignment even if one or more members of the team are already requested. Previously, a team member who was already requested would be counted as one of the team's automatic review requests. + - Team review request: Keep a team assigned to review even if one or more members is newly assigned. + + For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." + + - heading: 'New themes' + notes: + - | + Two new themes are available for the GitHub AE web UI. + + - A dark high contrast theme, with greater contrast between foreground and background elements + - Light and dark colorblind, which swap colors such as red and green for orange and blue + + For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + + - heading: 'Markdown improvements' + notes: + - | + You can now use footnote syntax in any Markdown field to reference relevant information without disrupting the flow of your prose. Footnotes are displayed as superscript links. Click a footnote to jump to the reference, displayed in a new section at the bottom of the document. 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#footnotes)." + + - | + You can now toggle between the source view and rendered Markdown view through the web UI by clicking the {% octicon "code" aria-label="The Code icon" %} button to "Display the source diff" at the top of any Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file. + + - | + You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + + - | + GitHub AE now automatically generates a table of contents for Wikis, based on headings. + + changes: + - heading: 'Performance' + notes: + - | + Page loads and jobs are now significantly faster for repositories with many Git refs. + + - heading: 'Administration' + notes: + - | + The user impersonation process is improved. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise owner. For more information, see "[Impersonating a user](/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)." + + - heading: 'GitHub Actions' + notes: + - | + To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." + + - | + The audit log now includes additional events for GitHub Actions. GitHub AE now records audit log entries for the following events. + + - A self-hosted runner is registered or removed. + - A self-hosted runner is added to a runner group, or removed from a runner group. + - A runner group is created or removed. + - A workflow run is created or completed. + - A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner. + + For more information, see "[Security hardening for GitHub Actions](/actions/security-guides/security-hardening-for-github-actions)." + + - heading: 'GitHub Advanced Security' + notes: + - | + Code scanning will now map alerts identified in `on:push` workflows to show up on pull requests, when possible. The alerts shown on the pull request are those identified by comparing the existing analysis of the head of the branch to the analysis for the target branch that you are merging against. Note that if the pull request's merge commit is not used, alerts can be less accurate when compared to the approach that uses `on:pull_request` triggers. For more information, see "[About code scanning with CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." + + Some other CI/CD systems can exclusively be configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, code scanning will try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see "[Uploading a SARIF file to GitHub](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)." + + - | + GitHub AE now detects secrets from additional providers. For more information, see "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets)." + + - heading: 'Pull requests' + notes: + - | + The timeline and Reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members because that team uses code review assignment. + + ![Screenshot of indicator for automatic assignment of code review](https://user-images.githubusercontent.com/2503052/134931920-409dea07-7a70-4557-b208-963357db7a0d.png) + + - | + You can now filter pull request searches to only include pull requests you are directly requested to review by choosing **Awaiting review from you**. For more information, see "[Searching issues and pull requests](https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests)." + + - | + If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list. + + - | + When viewing a branch that has a corresponding open pull request, GitHub AE now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request. + + - | + You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click in the toolbar. Note that this feature is currently only available in some browsers. + + - | + A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [GitHub Changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/). + + - heading: 'Repositories' + notes: + - | + GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](​​https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." + + - | + You can now add, delete, or view autolinks through the Repositories API's Autolinks endpoint. For more information, see "[Autolinked references and URLs](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)" and "[Repositories](/rest/reference/repos#autolinks)" in the REST API documentation. + + - heading: 'Releases' + notes: + + - | + The tag selection component for GitHub releases is now a drop-down menu rather than a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)." + + - heading: 'Markdown' + notes: + + - | + When dragging and dropping files such as images and videos into a Markdown editor, GitHub AE now uses the mouse pointer location instead of the cursor location when placing the file. diff --git a/data/reusables/actions/allow-specific-actions-intro.md b/data/reusables/actions/allow-specific-actions-intro.md index 5918d645aa..efaede7995 100644 --- a/data/reusables/actions/allow-specific-actions-intro.md +++ b/data/reusables/actions/allow-specific-actions-intro.md @@ -4,8 +4,8 @@ When you choose {% data reusables.actions.policy-label-for-select-actions-workflows %}, local actions{% if actions-workflow-policy %} and reusable workflows{% endif %} are allowed, and there are additional options for allowing other specific actions{% if actions-workflow-policy %} and reusable workflows{% endif %}: -- **Allow actions created by {% data variables.product.prodname_dotcom %}:** You can allow all actions created by {% data variables.product.prodname_dotcom %} to be used by workflows. Actions created by {% data variables.product.prodname_dotcom %} are located in the `actions` and `github` organizations. For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.{% ifversion fpt or ghes or ghae-issue-5094 or ghec %} -- **Allow Marketplace actions by verified creators:** {% ifversion ghes or ghae-issue-5094 %}This option is available if you have {% data variables.product.prodname_github_connect %} enabled and configured with {% data variables.product.prodname_actions %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)."{% endif %} You can allow all {% data variables.product.prodname_marketplace %} actions created by verified creators to be used by workflows. When GitHub has verified the creator of the action as a partner organization, the {% octicon "verified" aria-label="The verified badge" %} badge is displayed next to the action in {% data variables.product.prodname_marketplace %}.{% endif %} +- **Allow actions created by {% data variables.product.prodname_dotcom %}:** You can allow all actions created by {% data variables.product.prodname_dotcom %} to be used by workflows. Actions created by {% data variables.product.prodname_dotcom %} are located in the `actions` and `github` organizations. For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.{% ifversion fpt or ghes or ghae or ghec %} +- **Allow Marketplace actions by verified creators:** {% ifversion ghes or ghae %}This option is available if you have {% data variables.product.prodname_github_connect %} enabled and configured with {% data variables.product.prodname_actions %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)."{% endif %} You can allow all {% data variables.product.prodname_marketplace %} actions created by verified creators to be used by workflows. When GitHub has verified the creator of the action as a partner organization, the {% octicon "verified" aria-label="The verified badge" %} badge is displayed next to the action in {% data variables.product.prodname_marketplace %}.{% endif %} - **Allow specified actions{% if actions-workflow-policy %} and reusable workflows{% endif %}:** You can restrict workflows to use actions{% if actions-workflow-policy %} and reusable workflows{% endif %} in specific organizations and repositories. To restrict access to specific tags or commit SHAs of an action{% if actions-workflow-policy %} or reusable workflow{% endif %}, use the same syntax used in the workflow to select the action{% if actions-workflow-policy %} or reusable workflow{% endif %}. diff --git a/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md b/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md index d250482df8..8fe124a3bd 100644 --- a/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md +++ b/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md @@ -1,6 +1,8 @@ You can use `jobs..outputs` to create a `map` of outputs for a job. Job outputs are available to all downstream jobs that depend on this job. For more information on defining job dependencies, see [`jobs..needs`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idneeds). -Job outputs are strings, and job outputs containing expressions are evaluated on the runner at the end of each job. Outputs containing secrets are redacted on the runner and not sent to {% data variables.product.prodname_actions %}. +{% data reusables.actions.output-limitations %} + +Job outputs containing expressions are evaluated on the runner at the end of each job. Outputs containing secrets are redacted on the runner and not sent to {% data variables.product.prodname_actions %}. To use job outputs in a dependent job, you can use the `needs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#needs-context)." diff --git a/data/reusables/actions/jobs/using-matrix-strategy.md b/data/reusables/actions/jobs/using-matrix-strategy.md index 58d520c087..aeb6374e96 100644 --- a/data/reusables/actions/jobs/using-matrix-strategy.md +++ b/data/reusables/actions/jobs/using-matrix-strategy.md @@ -1,4 +1,4 @@ -Use `jobs..strategy.matrix` to define a matrix of different job configurations. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a veriable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`: +Use `jobs..strategy.matrix` to define a matrix of different job configurations. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a variable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`: ```yaml jobs: diff --git a/data/reusables/actions/message-parameters.md b/data/reusables/actions/message-parameters.md index f7e9299c70..647019cef2 100644 --- a/data/reusables/actions/message-parameters.md +++ b/data/reusables/actions/message-parameters.md @@ -1,8 +1,8 @@ | Parameter | Value | -| :- | :- |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +| :- | :- |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `title` | Custom title |{% endif %} | `file` | Filename | -| `col` | Column number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +| `col` | Column number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endColumn` | End column number |{% endif %} -| `line` | Line number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +| `line` | Line number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endLine` | End line number |{% endif %} diff --git a/data/reusables/actions/output-limitations.md b/data/reusables/actions/output-limitations.md new file mode 100644 index 0000000000..d26de54a7f --- /dev/null +++ b/data/reusables/actions/output-limitations.md @@ -0,0 +1 @@ +Outputs are Unicode strings, and can be a maximum of 1 MB. The total of all outputs in a workflow run can be a maximum of 50 MB. diff --git a/data/reusables/apps/deprecating_auth_with_query_parameters.md b/data/reusables/apps/deprecating_auth_with_query_parameters.md index 80a1833994..1c83fc9695 100644 --- a/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,4 +1,3 @@ -{% ifversion fpt or ghes or ghae or ghec %} {% warning %} **Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% ifversion fpt or ghec %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %} For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). @@ -6,4 +5,3 @@ {% ifversion ghes or ghae %} Authentication to the API using query parameters while available is no longer supported due to security concerns. Instead we recommend integrators move their access token, `client_id`, or `client_secret` in the header. {% data variables.product.prodname_dotcom %} will announce the removal of authentication by query parameters with advanced notice. {% endif %} {% endwarning %} -{% endif %} diff --git a/data/reusables/audit_log/audit-log-action-categories.md b/data/reusables/audit_log/audit-log-action-categories.md index 53bc87905e..97a342be65 100644 --- a/data/reusables/audit_log/audit-log-action-categories.md +++ b/data/reusables/audit_log/audit-log-action-categories.md @@ -28,7 +28,7 @@ {%- ifversion ghes %} | `config_entry` | Contains activities related to configuration settings. These events are only visible in the site admin audit log. {%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} | +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | | `dependabot_alerts` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." | `dependabot_alerts_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. | `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access. @@ -37,7 +37,7 @@ | `dependabot_security_updates` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." | `dependabot_security_updates_new_repos` | 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 or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} | `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." | `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization. {%- endif %} @@ -155,7 +155,7 @@ {%- ifversion fpt or ghec %} | `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization. {%- endif %} -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} | `repository_vulnerability_alert` | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies). {%- endif %} {%- ifversion fpt or ghec %} diff --git a/data/reusables/cli/filter-issues-and-pull-requests-tip.md b/data/reusables/cli/filter-issues-and-pull-requests-tip.md index 98812b7152..cb30d4cea9 100644 --- a/data/reusables/cli/filter-issues-and-pull-requests-tip.md +++ b/data/reusables/cli/filter-issues-and-pull-requests-tip.md @@ -1,7 +1,5 @@ -{% ifversion fpt or ghes or ghae or ghec %} {% tip %} **Tip**: You can also filter issues or pull requests using the {% data variables.product.prodname_cli %}. For more information, see "[`gh issue list`](https://cli.github.com/manual/gh_issue_list)" or "[`gh pr list`](https://cli.github.com/manual/gh_pr_list)" in the {% data variables.product.prodname_cli %} documentation. {% endtip %} -{% endif %} diff --git a/data/reusables/code-scanning/beta.md b/data/reusables/code-scanning/beta.md index ecb5dc9480..076408a9c9 100644 --- a/data/reusables/code-scanning/beta.md +++ b/data/reusables/code-scanning/beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-5752 %} +{% ifversion ghae %} diff --git a/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/data/reusables/codespaces/click-remote-explorer-icon-vscode.md index 874a9f57b0..83bf494e4d 100644 --- a/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ b/data/reusables/codespaces/click-remote-explorer-icon-vscode.md @@ -1,2 +1,2 @@ -1. In {% data variables.product.prodname_vscode %}, in the left sidebar, click the Remote Explorer icon. +1. In {% data variables.product.prodname_vscode_shortname %}, in the left sidebar, click the Remote Explorer icon. ![The Remote Explorer icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) diff --git a/data/reusables/codespaces/committing-link-to-procedure.md b/data/reusables/codespaces/committing-link-to-procedure.md index 0bf78b2fe5..ebbdafc054 100644 --- a/data/reusables/codespaces/committing-link-to-procedure.md +++ b/data/reusables/codespaces/committing-link-to-procedure.md @@ -1,3 +1,3 @@ -Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit your changes. Committing changes to your repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, such as adding {% data variables.product.prodname_vscode %} extensions, will appear for all users. +Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit your changes. Committing changes to your repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, such as adding {% data variables.product.prodname_vscode_shortname %} extensions, will appear for all users. For information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)." diff --git a/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/data/reusables/codespaces/connect-to-codespace-from-vscode.md index 045387a57b..9ab86b13a4 100644 --- a/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ b/data/reusables/codespaces/connect-to-codespace-from-vscode.md @@ -1 +1 @@ -You can connect to your codespace directly from {% data variables.product.prodname_vscode %}. For more information, see "[Using Codespaces in {% data variables.product.prodname_vscode %}](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)." +You can connect to your codespace directly from {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Using Codespaces in {% data variables.product.prodname_vscode_shortname %}](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)." diff --git a/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/data/reusables/codespaces/creating-a-codespace-in-vscode.md index 96eb32c448..bdb7adec1c 100644 --- a/data/reusables/codespaces/creating-a-codespace-in-vscode.md +++ b/data/reusables/codespaces/creating-a-codespace-in-vscode.md @@ -1,8 +1,8 @@ -After you connect your account on {% data variables.product.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). +After you connect your account on {% data variables.product.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). {% note %} -**Note**: Currently, {% data variables.product.prodname_vscode %} doesn't allow you to choose a dev container configuration when you create a codespace. If you want to choose a specific dev container configuration, use the {% data variables.product.prodname_dotcom %} web interface to create your codespace. For more information, click the **Web browser** tab at the top of this page. +**Note**: Currently, {% data variables.product.prodname_vscode_shortname %} doesn't allow you to choose a dev container configuration when you create a codespace. If you want to choose a specific dev container configuration, use the {% data variables.product.prodname_dotcom %} web interface to create your codespace. For more information, click the **Web browser** tab at the top of this page. {% endnote %} diff --git a/data/reusables/codespaces/deleting-a-codespace-in-vscode.md b/data/reusables/codespaces/deleting-a-codespace-in-vscode.md index ff8bb8110f..67183c4ef2 100644 --- a/data/reusables/codespaces/deleting-a-codespace-in-vscode.md +++ b/data/reusables/codespaces/deleting-a-codespace-in-vscode.md @@ -1,4 +1,4 @@ -You can delete codespaces from within {% data variables.product.prodname_vscode %} when you are not currently working in a codespace. +You can delete codespaces from within {% data variables.product.prodname_vscode_shortname %} when you are not currently working in a codespace. {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 1. Under "GITHUB CODESPACES", right-click the codespace you want to delete. diff --git a/data/reusables/codespaces/more-info-devcontainer.md b/data/reusables/codespaces/more-info-devcontainer.md index 430a9f1156..f0fd5c863b 100644 --- a/data/reusables/codespaces/more-info-devcontainer.md +++ b/data/reusables/codespaces/more-info-devcontainer.md @@ -1 +1 @@ -For information about the settings and properties that you can set in a `devcontainer.json` file, see "[devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json)" in the {% data variables.product.prodname_vscode %} documentation. \ No newline at end of file +For information about the settings and properties that you can set in a `devcontainer.json` file, see "[devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json)" in the {% data variables.product.prodname_vscode_shortname %} documentation. \ No newline at end of file diff --git a/data/reusables/codespaces/use-visual-studio-features.md b/data/reusables/codespaces/use-visual-studio-features.md index a5b1cf9151..4cabe97da4 100644 --- a/data/reusables/codespaces/use-visual-studio-features.md +++ b/data/reusables/codespaces/use-visual-studio-features.md @@ -1 +1 @@ -You can edit code, debug, and use Git commands while developing in a codespace with {% data variables.product.prodname_vscode %}. For more information, see the [{% data variables.product.prodname_vscode %} documentation](https://code.visualstudio.com/docs). +You can edit code, debug, and use Git commands while developing in a codespace with {% data variables.product.prodname_vscode_shortname %}. For more information, see the [{% data variables.product.prodname_vscode_shortname %} documentation](https://code.visualstudio.com/docs). diff --git a/data/reusables/codespaces/vscode-settings-order.md b/data/reusables/codespaces/vscode-settings-order.md index fc4b840129..27e09a3975 100644 --- a/data/reusables/codespaces/vscode-settings-order.md +++ b/data/reusables/codespaces/vscode-settings-order.md @@ -1 +1 @@ -When you configure editor settings for {% data variables.product.prodname_vscode %}, there are three scopes available: _Workspace_, _Remote [Codespaces]_, and _User_. If a setting is defined in multiple scopes, _Workspace_ settings take priority, then _Remote [Codespaces]_, then _User_. +When you configure editor settings for {% data variables.product.prodname_vscode_shortname %}, there are three scopes available: _Workspace_, _Remote [Codespaces]_, and _User_. If a setting is defined in multiple scopes, _Workspace_ settings take priority, then _Remote [Codespaces]_, then _User_. diff --git a/data/reusables/dependabot/dependabot-alerts-beta.md b/data/reusables/dependabot/dependabot-alerts-beta.md index 4cfd65386a..c2bfc45615 100644 --- a/data/reusables/dependabot/dependabot-alerts-beta.md +++ b/data/reusables/dependabot/dependabot-alerts-beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-4864 %} +{% ifversion ghae %} {% note %} **Note:** {% data variables.product.prodname_dependabot_alerts %} is currently in beta and is subject to change. diff --git a/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md b/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md index d5ae9b8415..930c6ac941 100644 --- a/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md +++ b/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md @@ -1,3 +1,3 @@ -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} Enterprise owners can configure {% ifversion ghes %}the dependency graph and {% endif %}{% data variables.product.prodname_dependabot_alerts %} for an enterprise. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} diff --git a/data/reusables/gated-features/dependency-review.md b/data/reusables/gated-features/dependency-review.md index bd88b5b182..5c0c364fc7 100644 --- a/data/reusables/gated-features/dependency-review.md +++ b/data/reusables/gated-features/dependency-review.md @@ -7,7 +7,7 @@ Dependency review is included in {% data variables.product.product_name %} for p {%- elsif ghes > 3.1 %} Dependency review is available for organization-owned repositories in {% data variables.product.product_name %}. This feature requires a license for {% data variables.product.prodname_GH_advanced_security %}. -{%- elsif ghae-issue-4864 %} +{%- elsif ghae %} Dependency review is available for organization-owned repositories in {% data variables.product.product_name %}. This is a {% data variables.product.prodname_GH_advanced_security %} feature (free during the beta release). -{%- endif %} {% data reusables.advanced-security.more-info-ghas %} \ No newline at end of file +{%- endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md index d65eeb566d..dfe433d5e0 100644 --- a/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md +++ b/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md @@ -1,3 +1,3 @@ -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} You can choose the delivery method and frequency of notifications about {% data variables.product.prodname_dependabot_alerts %} on repositories that you are watching or where you have subscribed to notifications for security alerts. {% endif %} diff --git a/data/reusables/notifications/vulnerable-dependency-notification-options.md b/data/reusables/notifications/vulnerable-dependency-notification-options.md index 8d2b81380d..96569a17c1 100644 --- a/data/reusables/notifications/vulnerable-dependency-notification-options.md +++ b/data/reusables/notifications/vulnerable-dependency-notification-options.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} -{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes > 3.1 or ghae %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %} - by email, an email is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**Email each time a vulnerability is found** option). - in the user interface, a warning is shown in your repository's file and code views if there are any vulnerable dependencies (**UI alerts** option). diff --git a/data/reusables/organizations/security-overview-feature-specific-page.md b/data/reusables/organizations/security-overview-feature-specific-page.md new file mode 100644 index 0000000000..606fab66d0 --- /dev/null +++ b/data/reusables/organizations/security-overview-feature-specific-page.md @@ -0,0 +1 @@ +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 that feature to fine-tune your search. diff --git a/data/reusables/organizations/team_maintainers_can.md b/data/reusables/organizations/team_maintainers_can.md index 7399688abc..45748e8eb2 100644 --- a/data/reusables/organizations/team_maintainers_can.md +++ b/data/reusables/organizations/team_maintainers_can.md @@ -10,6 +10,6 @@ Members with team maintainer permissions can: - [Add organization members to the team](/articles/adding-organization-members-to-a-team) - [Remove organization members from the team](/articles/removing-organization-members-from-a-team) - [Promote an existing team member to team maintainer](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member) -- Remove the team's access to repositories{% ifversion fpt or ghes or ghae or ghec %} -- [Manage code review settings for the team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% endif %}{% ifversion fpt or ghec %} +- Remove the team's access to repositories +- [Manage code review settings for the team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% ifversion fpt or ghec %} - [Manage scheduled reminders for pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/data/reusables/pull_requests/close-issues-using-keywords.md b/data/reusables/pull_requests/close-issues-using-keywords.md index b6d3070db6..f7ed5cf566 100644 --- a/data/reusables/pull_requests/close-issues-using-keywords.md +++ b/data/reusables/pull_requests/close-issues-using-keywords.md @@ -1 +1 @@ -You can 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. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)." +You can link a pull request to an issue to show that a fix is in progress and to automatically close the issue when someone merges the pull request. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)." diff --git a/data/reusables/repositories/copy-clone-url.md b/data/reusables/repositories/copy-clone-url.md index 423aff6859..6890b61434 100644 --- a/data/reusables/repositories/copy-clone-url.md +++ b/data/reusables/repositories/copy-clone-url.md @@ -1,6 +1,8 @@ 1. Above the list of files, click {% octicon "download" aria-label="The download icon" %} **Code**. !["Code" button](/assets/images/help/repository/code-button.png) -1. To clone the repository using HTTPS, under "Clone with HTTPS", click {% octicon "clippy" aria-label="The clipboard icon" %}. To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **Use SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. To clone a repository using {% data variables.product.prodname_cli %}, click **Use {% data variables.product.prodname_cli %}**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. - ![The clipboard icon for copying the URL to clone a repository](/assets/images/help/repository/https-url-clone.png) - {% ifversion fpt or ghes or ghae or ghec %} - ![The clipboard icon for copying the URL to clone a repository with GitHub CLI](/assets/images/help/repository/https-url-clone-cli.png){% endif %} +1. Copy the URL for the repository. + + - To clone the repository using HTTPS, under "HTTPS", click {% octicon "clippy" aria-label="The clipboard icon" %}. + - To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. + - To clone a repository using {% data variables.product.prodname_cli %}, click **{% data variables.product.prodname_cli %}**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. + ![The clipboard icon for copying the URL to clone a repository with GitHub CLI](/assets/images/help/repository/https-url-clone-cli.png) diff --git a/data/reusables/repositories/default-issue-templates.md b/data/reusables/repositories/default-issue-templates.md index e315eae12c..6dcea09ba6 100644 --- a/data/reusables/repositories/default-issue-templates.md +++ b/data/reusables/repositories/default-issue-templates.md @@ -1,2 +1 @@ -You can create default issue templates{% ifversion fpt or ghes or ghae or ghec %} and a default configuration file for issue templates{% endif %} for your organization{% ifversion fpt or ghes or ghae or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." - +You can create default issue templates and a default configuration file for issue templates for your organization or personal account. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." diff --git a/data/reusables/repositories/dependency-review.md b/data/reusables/repositories/dependency-review.md index 734a376e3b..b25af1da78 100644 --- a/data/reusables/repositories/dependency-review.md +++ b/data/reusables/repositories/dependency-review.md @@ -1,3 +1,3 @@ -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} Additionally, {% data variables.product.prodname_dotcom %} can review any dependencies added, updated, or removed in a pull request made against the default branch of a repository, and flag any changes that would introduce a vulnerability into your project. This allows you to spot and deal with vulnerable dependencies before, rather than after, they reach your codebase. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)." {% endif %} diff --git a/data/reusables/repositories/enable-security-alerts.md b/data/reusables/repositories/enable-security-alerts.md index 61a3c1b50d..375d5d5c4c 100644 --- a/data/reusables/repositories/enable-security-alerts.md +++ b/data/reusables/repositories/enable-security-alerts.md @@ -1,3 +1,3 @@ -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} Enterprise owners must enable {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} diff --git a/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index eddee42d31..03f4a57505 100644 --- a/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% ifversion fpt or ghes or ghae or ghec %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} +If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." diff --git a/data/reusables/repositories/start-line-comment.md b/data/reusables/repositories/start-line-comment.md index 1990d4f680..366c592780 100644 --- a/data/reusables/repositories/start-line-comment.md +++ b/data/reusables/repositories/start-line-comment.md @@ -1,2 +1,2 @@ -1. Hover over the line of code where you'd like to add a comment, and click the blue comment icon.{% ifversion fpt or ghes or ghae or ghec %} To add a comment on multiple lines, click and drag to select the range of lines, then click the blue comment icon.{% endif %} +1. Hover over the line of code where you'd like to add a comment, and click the blue comment icon. To add a comment on multiple lines, click and drag to select the range of lines, then click the blue comment icon. ![Blue comment icon](/assets/images/help/commits/hover-comment-icon.gif) diff --git a/data/reusables/repositories/suggest-changes.md b/data/reusables/repositories/suggest-changes.md index c9079f8ec0..00256f1309 100644 --- a/data/reusables/repositories/suggest-changes.md +++ b/data/reusables/repositories/suggest-changes.md @@ -1,2 +1,2 @@ -1. Optionally, to suggest a specific change to the line{% ifversion fpt or ghes or ghae or ghec %} or lines{% endif %}, click {% octicon "diff" aria-label="The diff symbol" %}, then edit the text within the suggestion block. +1. Optionally, to suggest a specific change to the line or lines, click {% octicon "diff" aria-label="The diff symbol" %}, then edit the text within the suggestion block. ![Suggestion block](/assets/images/help/pull_requests/suggestion-block.png) diff --git a/data/reusables/secret-scanning/beta.md b/data/reusables/secret-scanning/beta.md index 30ec5c2ce6..5b7328e460 100644 --- a/data/reusables/secret-scanning/beta.md +++ b/data/reusables/secret-scanning/beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-5752 %} +{% ifversion ghae %} diff --git a/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/data/reusables/secret-scanning/partner-secret-list-private-repo.md index af52b9b335..88d6afb8fa 100644 --- a/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -17,9 +17,9 @@ Amazon | Amazon OAuth Client ID | amazon_oauth_client_id{% endif %} Amazon | Amazon OAuth Client Secret | amazon_oauth_client_secret{% endif %} Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} @@ -37,7 +37,7 @@ Azure | Azure Service Management Certificate | azure_management_certificate {%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %} Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} Azure | Azure Storage Account Key | azure_storage_account_key -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Beamer | Beamer API Key | beamer_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key{% endif %} @@ -46,7 +46,7 @@ Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key{% endif % Clojars | Clojars Deploy Token | clojars_deploy_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Contentful | Contentful Personal Access Token | contentful_personal_access_token{% endif %} Databricks | Databricks Access Token | databricks_access_token {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} @@ -82,7 +82,7 @@ Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key{ Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key{% endif %} Frame.io | Frame.io JSON Web Token | frameio_jwt Frame.io| Frame.io Developer Token | frameio_developer_token -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} FullStory | FullStory API Key | fullstory_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %} @@ -97,15 +97,15 @@ GitHub | GitHub SSH Private Key | github_ssh_private_key GitLab | GitLab Access Token | gitlab_access_token{% endif %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} Google | Google API Key | google_api_key Google | Google Cloud Private Key ID | google_cloud_private_key_id -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Google | Google OAuth Access Token | google_oauth_access_token{% endif %} @@ -129,9 +129,9 @@ Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %} Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} JD Cloud | JD Cloud Access Key | jd_cloud_access_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Linear | Linear API Key | linear_api_key{% endif %} @@ -153,13 +153,13 @@ Meta | Facebook Access Token | facebook_access_token{% endif %} Midtrans | Midtrans Production Server Key | midtrans_production_server_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Midtrans | Midtrans Sandbox Server Key | midtrans_sandbox_server_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic License Key | new_relic_license_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Notion | Notion Integration Token | notion_integration_token{% endif %} @@ -176,15 +176,15 @@ Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} OpenAI | OpenAI API Key | openai_api_key{% endif %} Palantir | Palantir JSON Web Token | palantir_jwt -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Plivo | Plivo Auth ID | plivo_auth_id{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Plivo | Plivo Auth Token | plivo_auth_token{% endif %} Postman | Postman API Key | postman_api_key Proctorio | Proctorio Consumer Key | proctorio_consumer_key @@ -202,9 +202,9 @@ Samsara | Samsara OAuth Access Token | samsara_oauth_access_token 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 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Shippo | Shippo Live API Token | shippo_live_api_token{% endif %} diff --git a/data/reusables/security-center/permissions.md b/data/reusables/security-center/permissions.md new file mode 100644 index 0000000000..f18dc342ec --- /dev/null +++ b/data/reusables/security-center/permissions.md @@ -0,0 +1 @@ +Organization owners and security managers can access the security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} and view their organization's repositories via the enterprise-level security overview. Enterprise owners can use the enterprise-level security overview to view all repositories in their enterprise's organizations{% endif %}. Members of a team can see the security overview for repositories that the team has admin privileges for. \ No newline at end of file diff --git a/data/reusables/security/compliance-report-list.md b/data/reusables/security/compliance-report-list.md index 731afc0ca0..cb121885f2 100644 --- a/data/reusables/security/compliance-report-list.md +++ b/data/reusables/security/compliance-report-list.md @@ -1,4 +1,5 @@ - SOC 1, Type 2 - SOC 2, Type 2 - Cloud Security Alliance CAIQ self-assessment (CSA CAIQ) +- ISO/IEC 27001:2013 certification - {% data variables.product.prodname_dotcom_the_website %} Services Continuity and Incident Management Plan diff --git a/data/reusables/ssh/key-type-support.md b/data/reusables/ssh/key-type-support.md index 57b5241f88..05e444cc2b 100644 --- a/data/reusables/ssh/key-type-support.md +++ b/data/reusables/ssh/key-type-support.md @@ -1,3 +1,4 @@ +{% ifversion fpt or ghec %} {% note %} **Note:** {% data variables.product.company_short %} improved security by dropping older, insecure key types on March 15, 2022. @@ -7,3 +8,4 @@ As of that date, DSA keys (`ssh-dss`) are no longer supported. You cannot add ne RSA keys (`ssh-rsa`) with a `valid_after` before November 2, 2021 may continue to use any signature algorithm. RSA keys generated after that date must use a SHA-2 signature algorithm. Some older clients may need to be upgraded in order to use SHA-2 signatures. {% endnote %} +{% endif %} \ No newline at end of file diff --git a/data/reusables/user-settings/removes-personal-access-tokens.md b/data/reusables/user-settings/removes-personal-access-tokens.md index b11c0bbd8b..c6184d182d 100644 --- a/data/reusables/user-settings/removes-personal-access-tokens.md +++ b/data/reusables/user-settings/removes-personal-access-tokens.md @@ -1 +1 @@ -As a security precaution, {% data variables.product.company_short %} automatically removes personal access tokens that haven't been used in a year.{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} To provide additional security, we highly recommend adding an expiration to your personal access tokens.{% endif %} +As a security precaution, {% data variables.product.company_short %} automatically removes personal access tokens that haven't been used in a year.{% ifversion fpt or ghes > 3.1 or ghae or ghec %} To provide additional security, we highly recommend adding an expiration to your personal access tokens.{% endif %} diff --git a/data/reusables/webhooks/check_run_properties.md b/data/reusables/webhooks/check_run_properties.md index b5ec1cacab..f20b5838af 100644 --- a/data/reusables/webhooks/check_run_properties.md +++ b/data/reusables/webhooks/check_run_properties.md @@ -3,7 +3,7 @@ Key | Type | Description `action`|`string` | The action performed. Can be one of:
  • `created` - A new check run was created.
  • `completed` - The `status` of the check run is `completed`.
  • `rerequested` - Someone requested to re-run your check run from the pull request UI. See "[About status checks](/articles/about-status-checks#checks)" for more details about the GitHub UI. When you receive a `rerequested` action, you'll need to [create a new check run](/rest/reference/checks#create-a-check-run). Only the {% data variables.product.prodname_github_app %} that someone requests to re-run the check will receive the `rerequested` payload.
  • `requested_action` - Someone requested an action your app provides to be taken. Only the {% data variables.product.prodname_github_app %} someone requests to perform an action will receive the `requested_action` payload. To learn more about check runs and requested actions, see "[Check runs and requested actions](/rest/reference/checks#check-runs-and-requested-actions)."
`check_run`|`object` | The [check_run](/rest/reference/checks#get-a-check-run). `check_run[status]`|`string` | The current status of the check run. Can be `queued`, `in_progress`, or `completed`. -`check_run[conclusion]`|`string` | The result of the completed check run. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% ifversion fpt or ghes or ghae or ghec %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. This value will be `null` until the check run has `completed`. +`check_run[conclusion]`|`string` | The result of the completed check run. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, `action_required` or `stale`. This value will be `null` until the check run has `completed`. `check_run[name]`|`string` | The name of the check run. `check_run[check_suite][id]`|`integer` | The id of the check suite that this check run is part of. `check_run[check_suite][pull_requests]`|`array`| An array of pull requests that match this check suite. A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
diff --git a/data/reusables/webhooks/check_suite_properties.md b/data/reusables/webhooks/check_suite_properties.md index 07ea1debcb..3f5487c324 100644 --- a/data/reusables/webhooks/check_suite_properties.md +++ b/data/reusables/webhooks/check_suite_properties.md @@ -5,6 +5,6 @@ Key | Type | Description `check_suite[head_branch]`|`string` | The head branch name the changes are on. `check_suite[head_sha]`|`string` | The SHA of the most recent commit for this check suite. `check_suite[status]`|`string` | The summary status for all check runs that are part of the check suite. Can be `requested`, `in_progress`, or `completed`. -`check_suite[conclusion]`|`string`| The summary conclusion for all check runs that are part of the check suite. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% ifversion fpt or ghes or ghae or ghec %}`action_required` or `stale`{% else %}or `action_required`{% endif %}. This value will be `null` until the check run has `completed`. +`check_suite[conclusion]`|`string`| The summary conclusion for all check runs that are part of the check suite. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, `action_required` or `stale`. This value will be `null` until the check run has `completed`. `check_suite[url]`|`string` | URL that points to the check suite API resource. `check_suite[pull_requests]`|`array`| An array of pull requests that match this check suite. A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
diff --git a/data/reusables/webhooks/installation_properties.md b/data/reusables/webhooks/installation_properties.md index c2a6d203e6..e597666aea 100644 --- a/data/reusables/webhooks/installation_properties.md +++ b/data/reusables/webhooks/installation_properties.md @@ -1,4 +1,4 @@ Key | Type | Description ----|------|------------ -`action` | `string` | The action that was performed. Can be one of:
  • `created` - Someone installs a {% data variables.product.prodname_github_app %}.
  • `deleted` - Someone uninstalls a {% data variables.product.prodname_github_app %}
    • {% ifversion fpt or ghes or ghae or ghec %}
  • `suspend` - Someone suspends a {% data variables.product.prodname_github_app %} installation.
  • `unsuspend` - Someone unsuspends a {% data variables.product.prodname_github_app %} installation.
    • {% endif %}
  • `new_permissions_accepted` - Someone accepts new permissions for a {% data variables.product.prodname_github_app %} installation. When a {% data variables.product.prodname_github_app %} owner requests new permissions, the person who installed the {% data variables.product.prodname_github_app %} must accept the new permissions request.
+`action` | `string` | The action that was performed. Can be one of:
  • `created` - Someone installs a {% data variables.product.prodname_github_app %}.
  • `deleted` - Someone uninstalls a {% data variables.product.prodname_github_app %}
  • `suspend` - Someone suspends a {% data variables.product.prodname_github_app %} installation.
  • `unsuspend` - Someone unsuspends a {% data variables.product.prodname_github_app %} installation.
  • `new_permissions_accepted` - Someone accepts new permissions for a {% data variables.product.prodname_github_app %} installation. When a {% data variables.product.prodname_github_app %} owner requests new permissions, the person who installed the {% data variables.product.prodname_github_app %} must accept the new permissions request.
`repositories` | `array` | An array of repository objects that the installation can access. diff --git a/data/variables/product.yml b/data/variables/product.yml index e2179f921b..70d1e3bce8 100644 --- a/data/variables/product.yml +++ b/data/variables/product.yml @@ -178,10 +178,14 @@ prodname_codeql_workflow: 'CodeQL analysis workflow' # Visual Studio prodname_vs: 'Visual Studio' +prodname_vscode_shortname: 'VS Code' prodname_vscode: 'Visual Studio Code' prodname_vss_ghe: 'Visual Studio subscriptions with GitHub Enterprise' prodname_vss_admin_portal_with_url: 'the [administrator portal for Visual Studio subscriptions](https://visualstudio.microsoft.com/subscriptions-administration/)' -prodname_vscode_command_palette: 'VS Code Command Palette' +prodname_vscode_command_palette_shortname: 'VS Code Command Palette' +prodname_vscode_command_palette: 'Visual Studio Code Command Palette' +prodname_vscode_marketplace: 'Visual Studio Code Marketplace' +prodname_vs_marketplace_shortname: 'VS Code Marketplace' # GitHub Dependabot prodname_dependabot: 'Dependabot' diff --git a/lib/frontmatter.js b/lib/frontmatter.js index a4e9fe1df2..97bded6467 100644 --- a/lib/frontmatter.js +++ b/lib/frontmatter.js @@ -64,6 +64,10 @@ export const schema = { hidden: { type: 'boolean', }, + // specify whether an Early Access article should not have a header notice + noEarlyAccessBanner: { + type: 'boolean', + }, layout: { type: ['string', 'boolean'], enum: layoutNames, diff --git a/components/lib/getThemeProps.ts b/lib/get-theme.js similarity index 55% rename from components/lib/getThemeProps.ts rename to lib/get-theme.js index 29d119afb2..50a6e0d181 100644 --- a/components/lib/getThemeProps.ts +++ b/lib/get-theme.js @@ -1,18 +1,18 @@ -type ThemeT = { name: string; color_mode: string } - -const defaultCSSThemeProps = { +// export const defaultCSSThemeProps = { +export const defaultCSSTheme = { colorMode: 'auto', // light, dark, auto nightTheme: 'dark', dayTheme: 'light', } -export const defaultComponentThemeProps = { +// export const defaultComponentThemeProps = { +export const defaultComponentTheme = { colorMode: 'auto', // day, night, auto nightTheme: 'dark', dayTheme: 'light', } -const cssColorModeToComponentColorMode: Record = { +const cssColorModeToComponentColorMode = { auto: 'auto', light: 'day', dark: 'night', @@ -24,7 +24,7 @@ const supportedThemes = ['light', 'dark', 'dark_dimmed'] * Our version of primer/css is out of date, so we can only support known themes. * For the least jarring experience possible, we fallback to the color_mode (light / dark) if provided by the theme, otherwise our own defaults */ -function getSupportedTheme(theme: ThemeT | undefined, fallbackTheme: string) { +function getSupportedTheme(theme, fallbackTheme) { if (!theme) { return fallbackTheme } @@ -33,35 +33,36 @@ function getSupportedTheme(theme: ThemeT | undefined, fallbackTheme: string) { } /* - * Returns theme props for consumption by either primer/css or primer/components + * Returns theme for consumption by either primer/css or primer/components * based on the cookie and/or fallback values */ -export function getThemeProps(req: any, mode?: 'css') { - let cookieValue: { - color_mode?: 'auto' | 'light' | 'dark' - dark_theme?: ThemeT - light_theme?: ThemeT - } = {} - const defaultThemeProps = mode === 'css' ? defaultCSSThemeProps : defaultComponentThemeProps +export function getTheme(req, cssMode = false) { + const cookieValue = {} + + const defaultTheme = cssMode ? defaultCSSTheme : defaultComponentTheme if (req.cookies?.color_mode) { try { - cookieValue = JSON.parse(decodeURIComponent(req.cookies.color_mode)) - } catch { - // do nothing + const parsed = JSON.parse(decodeURIComponent(req.cookies.color_mode)) + cookieValue.color_mode = parsed.color_mode + cookieValue.dark_theme = parsed.dark_theme + cookieValue.light_theme = parsed.light_theme + } catch (err) { + if (process.env.NODE_ENV !== 'test') { + console.warn("Unable to parse 'color_mode' cookie", err) + } } } // The cookie value is a primer/css color_mode. sometimes we need to convert that to a primer/components compatible version const colorMode = - (mode === 'css' + (cssMode ? cookieValue.color_mode - : cssColorModeToComponentColorMode[cookieValue.color_mode || '']) || - defaultThemeProps.colorMode + : cssColorModeToComponentColorMode[cookieValue.color_mode || '']) || defaultTheme.colorMode return { colorMode, - nightTheme: getSupportedTheme(cookieValue.dark_theme, defaultThemeProps.nightTheme), - dayTheme: getSupportedTheme(cookieValue.light_theme, defaultThemeProps.dayTheme), + nightTheme: getSupportedTheme(cookieValue.dark_theme, defaultTheme.nightTheme), + dayTheme: getSupportedTheme(cookieValue.light_theme, defaultTheme.dayTheme), } } diff --git a/lib/graphql/static/prerendered-input-objects.json b/lib/graphql/static/prerendered-input-objects.json index f30222f2c4..e9536c5c83 100644 --- a/lib/graphql/static/prerendered-input-objects.json +++ b/lib/graphql/static/prerendered-input-objects.json @@ -1,6 +1,6 @@ { "dotcom": { - "html": "
\n
\n

\n \n \nAbortQueuedMigrationsInput

\n

Autogenerated input type of AbortQueuedMigrations.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that is running the migrations.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAcceptEnterpriseAdministratorInvitationInput

\n

Autogenerated input type of AcceptEnterpriseAdministratorInvitation.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

invitationId (ID!)

The id of the invitation being accepted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAcceptTopicSuggestionInput

\n

Autogenerated input type of AcceptTopicSuggestion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the suggested topic.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddAssigneesToAssignableInput

\n

Autogenerated input type of AddAssigneesToAssignable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignableId (ID!)

The id of the assignable object to add assignees to.

\n\n\n\n\n\n\n\n\n\n\n\n

assigneeIds ([ID!]!)

The id of users to add as assignees.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddCommentInput

\n

Autogenerated input type of AddComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddDiscussionCommentInput

\n

Autogenerated input type of AddDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The Node ID of the discussion to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

replyToId (ID)

The Node ID of the discussion comment within this discussion to reply to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddEnterpriseSupportEntitlementInput

\n

Autogenerated input type of AddEnterpriseSupportEntitlement.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the admin belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of a member who will receive the support entitlement.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddLabelsToLabelableInput

\n

Autogenerated input type of AddLabelsToLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!]!)

The ids of the labels to add.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the labelable object to add labels to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectCardInput

\n

Autogenerated input type of AddProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

contentId (ID)

The content of the card. Must be a member of the ProjectCardItem union.

\n\n\n\n\n\n\n\n\n\n\n\n

note (String)

The note on the card.

\n\n\n\n\n\n\n\n\n\n\n\n

projectColumnId (ID!)

The Node ID of the ProjectColumn.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectColumnInput

\n

Autogenerated input type of AddProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the column.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Node ID of the project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectDraftIssueInput

\n

Autogenerated input type of AddProjectDraftIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The IDs of the assignees of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to add the draft issue to.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectNextItemInput

\n

Autogenerated input type of AddProjectNextItem.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

contentId (ID!)

The content id of the item (Issue or PullRequest).

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to add the item to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewCommentInput

\n

Autogenerated input type of AddPullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitOID (GitObjectID)

The SHA of the commit to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

inReplyTo (ID)

The comment id to reply to.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String)

The relative path of the file to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int)

The line index in the diff to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The node ID of the pull request reviewing.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Node ID of the review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewInput

\n

Autogenerated input type of AddPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The contents of the review body comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comments ([DraftPullRequestReviewComment])

The review line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

commitOID (GitObjectID)

The commit OID the review pertains to.

\n\n\n\n\n\n\n\n\n\n\n\n

event (PullRequestReviewEvent)

The event to perform on the pull request review.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

threads ([DraftPullRequestReviewThread])

The review line comment threads.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewThreadInput

\n

Autogenerated input type of AddPullRequestReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the thread's first comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

line (Int!)

The line of the blob to which the thread refers. The end of the line range for multi-line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The node ID of the pull request reviewing.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Node ID of the review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

side (DiffSide)

The side of the diff on which the line resides. For multi-line comments, this is the side for the end of the line range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int)

The first line of the range to which the comment refers.

\n\n\n\n\n\n\n\n\n\n\n\n

startSide (DiffSide)

The side of the diff on which the start line resides.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddReactionInput

\n

Autogenerated input type of AddReaction.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

content (ReactionContent!)

The name of the emoji to react with.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddStarInput

\n

Autogenerated input type of AddStar.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

starrableId (ID!)

The Starrable ID to star.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddUpvoteInput

\n

Autogenerated input type of AddUpvote.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the discussion or comment to upvote.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddVerifiableDomainInput

\n

Autogenerated input type of AddVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

domain (URI!)

The URL of the domain.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner to add the domain to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nApproveDeploymentsInput

\n

Autogenerated input type of ApproveDeployments.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comment (String)

Optional comment for approving deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentIds ([ID!]!)

The ids of environments to reject deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

workflowRunId (ID!)

The node ID of the workflow run containing the pending deployments.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nApproveVerifiableDomainInput

\n

Autogenerated input type of ApproveVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to approve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nArchiveRepositoryInput

\n

Autogenerated input type of ArchiveRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to mark as archived.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAuditLogOrder

\n

Ordering options for Audit Log connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (AuditLogOrderField)

The field to order Audit Logs by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCancelEnterpriseAdminInvitationInput

\n

Autogenerated input type of CancelEnterpriseAdminInvitation.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

invitationId (ID!)

The Node ID of the pending enterprise administrator invitation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCancelSponsorshipInput

\n

Autogenerated input type of CancelSponsorship.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorId (ID)

The ID of the user or organization who is acting as the sponsor, paying for\nthe sponsorship. Required if sponsorLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorLogin (String)

The username of the user or organization who is acting as the sponsor, paying\nfor the sponsorship. Required if sponsorId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who is receiving the sponsorship. Required if sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who is receiving the sponsorship. Required if sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nChangeUserStatusInput

\n

Autogenerated input type of ChangeUserStatus.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

emoji (String)

The emoji to represent your status. Can either be a native Unicode emoji or an emoji name with colons, e.g., 😀.

\n\n\n\n\n\n\n\n\n\n\n\n

expiresAt (DateTime)

If set, the user status will not be shown after this date.

\n\n\n\n\n\n\n\n\n\n\n\n

limitedAvailability (Boolean)

Whether this status should indicate you are not fully available on GitHub, e.g., you are away.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String)

A short description of your current status.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID)

The ID of the organization whose members will be allowed to see the status. If\nomitted, the status will be publicly visible.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckAnnotationData

\n

Information from a check run analysis to specific lines of code.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

annotationLevel (CheckAnnotationLevel!)

Represents an annotation's information level.

\n\n\n\n\n\n\n\n\n\n\n\n

location (CheckAnnotationRange!)

The location of the annotation.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String!)

A short description of the feedback for these lines of code.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to add an annotation to.

\n\n\n\n\n\n\n\n\n\n\n\n

rawDetails (String)

Details about this annotation.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title that represents the annotation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckAnnotationRange

\n

Information from a check run analysis to specific lines of code.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

endColumn (Int)

The ending column of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

endLine (Int!)

The ending line of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

startColumn (Int)

The starting column of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int!)

The starting line of the range.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunAction

\n

Possible further actions the integrator can perform.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

description (String!)

A short explanation of what this action would do.

\n\n\n\n\n\n\n\n\n\n\n\n

identifier (String!)

A reference for the action on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

label (String!)

The text to be displayed on a button in the web UI.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunFilter

\n

The filters that are available when fetching check runs.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (Int)

Filters the check runs created by this application ID.

\n\n\n\n\n\n\n\n\n\n\n\n

checkName (String)

Filters the check runs by this name.

\n\n\n\n\n\n\n\n\n\n\n\n

checkType (CheckRunType)

Filters the check runs by this type.

\n\n\n\n\n\n\n\n\n\n\n\n

status (CheckStatusState)

Filters the check runs by this status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunOutput

\n

Descriptive details about the check run.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

annotations ([CheckAnnotationData!])

The annotations that are made as part of the check run.

\n\n\n\n\n\n\n\n\n\n\n\n

images ([CheckRunOutputImage!])

Images attached to the check run output displayed in the GitHub pull request UI.

\n\n\n\n\n\n\n\n\n\n\n\n

summary (String!)

The summary of the check run (supports Commonmark).

\n\n\n\n\n\n\n\n\n\n\n\n

text (String)

The details of the check run (supports Commonmark).

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

A title to provide for this check run.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunOutputImage

\n

Images attached to the check run output displayed in the GitHub pull request UI.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

alt (String!)

The alternative text for the image.

\n\n\n\n\n\n\n\n\n\n\n\n

caption (String)

A short image description.

\n\n\n\n\n\n\n\n\n\n\n\n

imageUrl (URI!)

The full URL of the image.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckSuiteAutoTriggerPreference

\n

The auto-trigger preferences that are available for check suites.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (ID!)

The node ID of the application that owns the check suite.

\n\n\n\n\n\n\n\n\n\n\n\n

setting (Boolean!)

Set to true to enable automatic creation of CheckSuite events upon pushes to the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckSuiteFilter

\n

The filters that are available when fetching check suites.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (Int)

Filters the check suites created by this application ID.

\n\n\n\n\n\n\n\n\n\n\n\n

checkName (String)

Filters the check suites by this name.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nClearLabelsFromLabelableInput

\n

Autogenerated input type of ClearLabelsFromLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the labelable object to clear the labels from.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloneProjectInput

\n

Autogenerated input type of CloneProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

includeWorkflows (Boolean!)

Whether or not to clone the source project's workflows.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

The visibility of the project, defaults to false (private).

\n\n\n\n\n\n\n\n\n\n\n\n

sourceId (ID!)

The source project to clone.

\n\n\n\n\n\n\n\n\n\n\n\n

targetOwnerId (ID!)

The owner ID to create the project under.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloneTemplateRepositoryInput

\n

Autogenerated input type of CloneTemplateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

includeAllBranches (Boolean)

Whether to copy all branches from the template to the new repository. Defaults\nto copying only the default branch of the template.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner for the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the template repository.

\n\n\n\n\n\n\n\n\n\n\n\n

visibility (RepositoryVisibility!)

Indicates the repository's visibility level.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloseIssueInput

\n

Autogenerated input type of CloseIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

ID of the issue to be closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nClosePullRequestInput

\n

Autogenerated input type of ClosePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitAuthor

\n

Specifies an author for filtering Git commits.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

emails ([String!])

Email addresses to filter by. Commits authored by any of the specified email addresses will be returned.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID)

ID of a User to filter by. If non-null, only commits authored by this user\nwill be returned. This field takes precedence over emails.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitContributionOrder

\n

Ordering options for commit contribution connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (CommitContributionOrderField!)

The field by which to order commit contributions.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitMessage

\n

A message to include with a new commit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The body of the message.

\n\n\n\n\n\n\n\n\n\n\n\n

headline (String!)

The headline of the message.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommittableBranch

\n

A git ref for a commit to be appended to.

\n

The ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).

\n

The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.

\n

Examples

\n

Specify a branch using a global node ID:

\n
{ "id": "MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=" }\n
\n

Specify a branch using nameWithOwner and branch name:

\n
{\n  "nameWithOwner": "github/graphql-client",\n  "branchName": "main"\n}.\n
\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branchName (String)

The unqualified name of the branch to append the commit to.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID)

The Node ID of the Ref to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryNameWithOwner (String)

The nameWithOwner of the repository to commit to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nContributionOrder

\n

Ordering options for contribution connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nConvertProjectCardNoteToIssueInput

\n

Autogenerated input type of ConvertProjectCardNoteToIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The body of the newly created issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectCardId (ID!)

The ProjectCard ID to convert.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to create the issue in.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the newly created issue. Defaults to the card's note text.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nConvertPullRequestToDraftInput

\n

Autogenerated input type of ConvertPullRequestToDraft.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to convert to draft.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateBranchProtectionRuleInput

\n

Autogenerated input type of CreateBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowsDeletions (Boolean)

Can this branch be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

allowsForcePushes (Boolean)

Are force pushes allowed on this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

blocksCreations (Boolean)

Is branch creation a protected operation.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassForcePushActorIds ([ID!])

A list of User or Team IDs allowed to bypass force push targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassPullRequestActorIds ([ID!])

A list of User or Team IDs allowed to bypass pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissesStaleReviews (Boolean)

Will new commits pushed to matching branches dismiss pull request review approvals.

\n\n\n\n\n\n\n\n\n\n\n\n

isAdminEnforced (Boolean)

Can admins overwrite branch protection.

\n\n\n\n\n\n\n\n\n\n\n\n

pattern (String!)

The glob-like pattern used to determine matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

pushActorIds ([ID!])

A list of User, Team or App IDs allowed to push to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The global relay id of the repository in which a new branch protection rule should be created in.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredApprovingReviewCount (Int)

Number of approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusCheckContexts ([String!])

List of required status check contexts that must pass for commits to be accepted to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusChecks ([RequiredStatusCheckInput!])

The list of required status checks.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresApprovingReviews (Boolean)

Are approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCodeOwnerReviews (Boolean)

Are reviews from code owners required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCommitSignatures (Boolean)

Are commits required to be signed.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresConversationResolution (Boolean)

Are conversations required to be resolved before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresLinearHistory (Boolean)

Are merge commits prohibited from being pushed to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStatusChecks (Boolean)

Are status checks required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStrictStatusChecks (Boolean)

Are branches required to be up to date before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsPushes (Boolean)

Is pushing to matching branches restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsReviewDismissals (Boolean)

Is dismissal of pull request reviews restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewDismissalActorIds ([ID!])

A list of User or Team IDs allowed to dismiss reviews on pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCheckRunInput

\n

Autogenerated input type of CreateCheckRun.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actions ([CheckRunAction!])

Possible further actions the integrator can perform, which a user may trigger.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

completedAt (DateTime)

The time that the check run finished.

\n\n\n\n\n\n\n\n\n\n\n\n

conclusion (CheckConclusionState)

The final conclusion of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

detailsUrl (URI)

The URL of the integrator's site that has the full details of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

externalId (String)

A reference for the run on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

headSha (GitObjectID!)

The SHA of the head commit.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

output (CheckRunOutput)

Descriptive details about the run.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

startedAt (DateTime)

The time that the check run began.

\n\n\n\n\n\n\n\n\n\n\n\n

status (RequestableCheckStatusState)

The current status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCheckSuiteInput

\n

Autogenerated input type of CreateCheckSuite.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

headSha (GitObjectID!)

The SHA of the head commit.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCommitOnBranchInput

\n

Autogenerated input type of CreateCommitOnBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branch (CommittableBranch!)

The Ref to be updated. Must be a branch.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID!)

The git commit oid expected at the head of the branch prior to the commit.

\n\n\n\n\n\n\n\n\n\n\n\n

fileChanges (FileChanges)

A description of changes to files in this commit.

\n\n\n\n\n\n\n\n\n\n\n\n

message (CommitMessage!)

The commit message the be included with the commit.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDeploymentInput

\n

Autogenerated input type of CreateDeployment.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateDeploymentInput is available under the Deployments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoMerge (Boolean)

Attempt to automatically merge the default branch into the requested ref, defaults to true.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

Short description of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

environment (String)

Name for the target deployment environment.

\n\n\n\n\n\n\n\n\n\n\n\n

payload (String)

JSON payload with extra information about the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The node ID of the ref to be deployed.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredContexts ([String!])

The status contexts to verify against commit status checks. To bypass required\ncontexts, pass an empty array. Defaults to all unique contexts.

\n\n\n\n\n\n\n\n\n\n\n\n

task (String)

Specifies a task to execute.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDeploymentStatusInput

\n

Autogenerated input type of CreateDeploymentStatus.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateDeploymentStatusInput is available under the Deployments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoInactive (Boolean)

Adds a new inactive status to all non-transient, non-production environment\ndeployments with the same repository and environment name as the created\nstatus's deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

deploymentId (ID!)

The node ID of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the status. Maximum length of 140 characters.

\n\n\n\n\n\n\n\n\n\n\n\n

environment (String)

If provided, updates the environment of the deploy. Otherwise, does not modify the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentUrl (String)

Sets the URL for accessing your environment.

\n\n\n\n\n\n\n\n\n\n\n\n

logUrl (String)

The log URL to associate with this status. This URL should contain\noutput to keep the user updated while the task is running or serve as\nhistorical information for what happened in the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

state (DeploymentStatusState!)

The state of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDiscussionInput

\n

Autogenerated input type of CreateDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The body of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

categoryId (ID!)

The id of the discussion category to associate with this discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The id of the repository on which to create the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateEnterpriseOrganizationInput

\n

Autogenerated input type of CreateEnterpriseOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

adminLogins ([String!]!)

The logins for the administrators of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

billingEmail (String!)

The email used for sending billing receipts.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise owning the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

profileName (String!)

The profile name of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateEnvironmentInput

\n

Autogenerated input type of CreateEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateIpAllowListEntryInput

\n

Autogenerated input type of CreateIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowListValue (String!)

An IP address or range of addresses in CIDR notation.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isActive (Boolean!)

Whether the IP allow list entry is active when an IP allow list is enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

An optional name for the IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner for which to create the new IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateIssueInput

\n

Autogenerated input type of CreateIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The Node ID for the user assignee for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body for the issue description.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueTemplate (String)

The name of an issue template in the repository, assigns labels and assignees from the template to the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title for the issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateLabelInput

\n

Autogenerated input type of CreateLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

color (String!)

A 6 character hex code, without the leading #, identifying the color of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A brief description of the label, such as its purpose.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateMigrationSourceInput

\n

Autogenerated input type of CreateMigrationSource.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

accessToken (String)

The Octoshift migration source access token.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

githubPat (String)

The GitHub personal access token of the user importing to the target repository.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The Octoshift migration source name.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that will own the Octoshift migration source.

\n\n\n\n\n\n\n\n\n\n\n\n

type (MigrationSourceType!)

The Octoshift migration source type.

\n\n\n\n\n\n\n\n\n\n\n\n

url (String!)

The Octoshift migration source URL.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateProjectInput

\n

Autogenerated input type of CreateProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of project.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The owner ID to create the project under.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryIds ([ID!])

A list of repository IDs to create as linked repositories for the project.

\n\n\n\n\n\n\n\n\n\n\n\n

template (ProjectTemplate)

The name of the GitHub-provided template.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreatePullRequestInput

\n

Autogenerated input type of CreatePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

baseRefName (String!)

The name of the branch you want your changes pulled into. This should be an existing branch\non the current repository. You cannot update the base branch on a pull request to point\nto another repository.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The contents of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

draft (Boolean)

Indicates whether this pull request should be a draft.

\n\n\n\n\n\n\n\n\n\n\n\n

headRefName (String!)

The name of the branch where your changes are implemented. For cross-repository pull requests\nin the same network, namespace head_ref_name with a user like this: username:branch.

\n\n\n\n\n\n\n\n\n\n\n\n

maintainerCanModify (Boolean)

Indicates whether maintainers can modify the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateRefInput

\n

Autogenerated input type of CreateRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The fully qualified name of the new Ref (ie: refs/heads/my_new_branch).

\n\n\n\n\n\n\n\n\n\n\n\n

oid (GitObjectID!)

The GitObjectID that the new Ref shall target. Must point to a commit.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the Repository to create the Ref in.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateRepositoryInput

\n

Autogenerated input type of CreateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

hasIssuesEnabled (Boolean)

Indicates if the repository should have the issues feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasWikiEnabled (Boolean)

Indicates if the repository should have the wiki feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

homepageUrl (URI)

The URL for a web page about this repository.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID)

The ID of the owner for the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

teamId (ID)

When an organization is specified as the owner, this ID identifies the team\nthat should be granted access to the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

template (Boolean)

Whether this repository should be marked as a template such that anyone who\ncan access it can create new repositories with the same files and directory structure.

\n\n\n\n\n\n\n\n\n\n\n\n

visibility (RepositoryVisibility!)

Indicates the repository's visibility level.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateSponsorsTierInput

\n

Autogenerated input type of CreateSponsorsTier.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

amount (Int!)

The value of the new tier in US dollars. Valid values: 1-12000.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String!)

A description of what this tier is, what perks sponsors might receive, what a sponsorship at this tier means for you, etc.

\n\n\n\n\n\n\n\n\n\n\n\n

isRecurring (Boolean)

Whether sponsorships using this tier should happen monthly/yearly or just once.

\n\n\n\n\n\n\n\n\n\n\n\n

publish (Boolean)

Whether to make the tier available immediately for sponsors to choose.\nDefaults to creating a draft tier that will not be publicly visible.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID)

Optional ID of the private repository that sponsors at this tier should gain\nread-only access to. Must be owned by an organization.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryName (String)

Optional name of the private repository that sponsors at this tier should gain\nread-only access to. Must be owned by an organization. Necessary if\nrepositoryOwnerLogin is given. Will be ignored if repositoryId is given.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryOwnerLogin (String)

Optional login of the organization owner of the private repository that\nsponsors at this tier should gain read-only access to. Necessary if\nrepositoryName is given. Will be ignored if repositoryId is given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who owns the GitHub Sponsors profile.\nDefaults to the current user if omitted and sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who owns the GitHub Sponsors profile.\nDefaults to the current user if omitted and sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

welcomeMessage (String)

Optional message new sponsors at this tier will receive.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateSponsorshipInput

\n

Autogenerated input type of CreateSponsorship.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

amount (Int)

The amount to pay to the sponsorable in US dollars. Required if a tierId is not specified. Valid values: 1-12000.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isRecurring (Boolean)

Whether the sponsorship should happen monthly/yearly or just this one time. Required if a tierId is not specified.

\n\n\n\n\n\n\n\n\n\n\n\n

privacyLevel (SponsorshipPrivacy)

Specify whether others should be able to see that the sponsor is sponsoring\nthe sponsorable. Public visibility still does not reveal which tier is used.

\n\n\n\n\n\n\n\n\n\n\n\n

receiveEmails (Boolean)

Whether the sponsor should receive email updates from the sponsorable.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorId (ID)

The ID of the user or organization who is acting as the sponsor, paying for\nthe sponsorship. Required if sponsorLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorLogin (String)

The username of the user or organization who is acting as the sponsor, paying\nfor the sponsorship. Required if sponsorId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who is receiving the sponsorship. Required if sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who is receiving the sponsorship. Required if sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

tierId (ID)

The ID of one of sponsorable's existing tiers to sponsor at. Required if amount is not specified.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateTeamDiscussionCommentInput

\n

Autogenerated input type of CreateTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The content of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The ID of the discussion to which the comment belongs.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateTeamDiscussionInput

\n

Autogenerated input type of CreateTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The content of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

private (Boolean)

If true, restricts the visibility of this discussion to team members and\norganization admins. If false or not specified, allows any organization member\nto view this discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

teamId (ID!)

The ID of the team to which the discussion belongs.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeclineTopicSuggestionInput

\n

Autogenerated input type of DeclineTopicSuggestion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the suggested topic.

\n\n\n\n\n\n\n\n\n\n\n\n

reason (TopicSuggestionDeclineReason!)

The reason why the suggested topic is declined.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteBranchProtectionRuleInput

\n

Autogenerated input type of DeleteBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branchProtectionRuleId (ID!)

The global relay id of the branch protection rule to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDeploymentInput

\n

Autogenerated input type of DeleteDeployment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the deployment to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDiscussionCommentInput

\n

Autogenerated input type of DeleteDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node id of the discussion comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDiscussionInput

\n

Autogenerated input type of DeleteDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The id of the discussion to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteEnvironmentInput

\n

Autogenerated input type of DeleteEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the environment to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIpAllowListEntryInput

\n

Autogenerated input type of DeleteIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ipAllowListEntryId (ID!)

The ID of the IP allow list entry to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIssueCommentInput

\n

Autogenerated input type of DeleteIssueComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIssueInput

\n

Autogenerated input type of DeleteIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteLabelInput

\n

Autogenerated input type of DeleteLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

DeleteLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the label to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePackageVersionInput

\n

Autogenerated input type of DeletePackageVersion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

packageVersionId (ID!)

The ID of the package version to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectCardInput

\n

Autogenerated input type of DeleteProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

cardId (ID!)

The id of the card to delete.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectColumnInput

\n

Autogenerated input type of DeleteProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectInput

\n

Autogenerated input type of DeleteProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Project ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectNextItemInput

\n

Autogenerated input type of DeleteProjectNextItem.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

itemId (ID!)

The ID of the item to be removed.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project from which the item should be removed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePullRequestReviewCommentInput

\n

Autogenerated input type of DeletePullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePullRequestReviewInput

\n

Autogenerated input type of DeletePullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteRefInput

\n

Autogenerated input type of DeleteRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The Node ID of the Ref to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteTeamDiscussionCommentInput

\n

Autogenerated input type of DeleteTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteTeamDiscussionInput

\n

Autogenerated input type of DeleteTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The discussion ID to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteVerifiableDomainInput

\n

Autogenerated input type of DeleteVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeploymentOrder

\n

Ordering options for deployment connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (DeploymentOrderField!)

The field to order deployments by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDisablePullRequestAutoMergeInput

\n

Autogenerated input type of DisablePullRequestAutoMerge.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to disable auto merge on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDiscussionOrder

\n

Ways in which lists of discussions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order discussions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (DiscussionOrderField!)

The field by which to order discussions.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDismissPullRequestReviewInput

\n

Autogenerated input type of DismissPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String!)

The contents of the pull request review dismissal message.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDismissRepositoryVulnerabilityAlertInput

\n

Autogenerated input type of DismissRepositoryVulnerabilityAlert.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissReason (DismissReason!)

The reason the Dependabot alert is being dismissed.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryVulnerabilityAlertId (ID!)

The Dependabot alert ID to dismiss.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDraftPullRequestReviewComment

\n

Specifies a review comment to be left with a Pull Request Review.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the comment to leave.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int!)

Position in the file to leave a comment on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDraftPullRequestReviewThread

\n

Specifies a review comment thread to be left with a Pull Request Review.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the comment to leave.

\n\n\n\n\n\n\n\n\n\n\n\n

line (Int!)

The line of the blob to which the thread refers. The end of the line range for multi-line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

side (DiffSide)

The side of the diff on which the line resides. For multi-line comments, this is the side for the end of the line range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int)

The first line of the range to which the comment refers.

\n\n\n\n\n\n\n\n\n\n\n\n

startSide (DiffSide)

The side of the diff on which the start line resides.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnablePullRequestAutoMergeInput

\n

Autogenerated input type of EnablePullRequestAutoMerge.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this merge.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitBody (String)

Commit body to use for the commit when the PR is mergable; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

commitHeadline (String)

Commit headline to use for the commit when the PR is mergable; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

mergeMethod (PullRequestMergeMethod)

The merge method to use. If omitted, defaults to 'MERGE'.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to enable auto-merge on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseAdministratorInvitationOrder

\n

Ordering options for enterprise administrator invitation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseAdministratorInvitationOrderField!)

The field to order enterprise administrator invitations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseMemberOrder

\n

Ordering options for enterprise member connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseMemberOrderField!)

The field to order enterprise members by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerInstallationOrder

\n

Ordering options for Enterprise Server installation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerInstallationOrderField!)

The field to order Enterprise Server installations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountEmailOrder

\n

Ordering options for Enterprise Server user account email connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountEmailOrderField!)

The field to order emails by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountOrder

\n

Ordering options for Enterprise Server user account connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountOrderField!)

The field to order user accounts by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountsUploadOrder

\n

Ordering options for Enterprise Server user accounts upload connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountsUploadOrderField!)

The field to order user accounts uploads by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileAddition

\n

A command to add a file at the given path with the given contents as part of a\ncommit. Any existing file at that that path will be replaced.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

contents (Base64String!)

The base64 encoded contents of the file.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path in the repository where the file will be located.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileChanges

\n

A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file additions and zero or more\nfile deletions.

\n

Both fields are optional; omitting both will produce a commit with no\nfile changes.

\n

deletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.

\n

path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.

\n

Encoding

\n

File contents must be provided in full for each FileAddition.

\n

The contents of a FileAddition must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.

\n

The encoded contents may be binary.

\n

For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (\\n or \\r\\n), and that all files end\nwith a newline.

\n

Modeling file changes

\n

Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:

\n
    \n
  1. \n

    New file addition: create file hello world\\n at path docs/README.txt:

    \n

    {\n"additions" [\n{\n"path": "docs/README.txt",\n"contents": base64encode("hello world\\n")\n}\n]\n}

    \n
    2. \n
  2. \n

    Existing file modification: change existing docs/README.txt to have new\ncontent new content here\\n:

    \n
    {\n  "additions" [\n    {\n      "path": "docs/README.txt",\n      "contents": base64encode("new content here\\n")\n    }\n  ]\n}\n
    \n
    3. \n
  3. \n

    Existing file deletion: remove existing file docs/README.txt.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt"\n    }\n  ]\n}\n
    \n
    4. \n
  4. \n

    File rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt",\n    }\n  ],\n  "additions" [\n    {\n      "path": "newdocs/README.txt",\n      "contents": base64encode("hello world\\n")\n    }\n  ]\n}\n
    \n
    5. \n
  5. \n

    File rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt",\n    }\n  ],\n  "additions" [\n    {\n      "path": "newdocs/README.txt",\n      "contents": base64encode("new contents\\n")\n    }\n  ]\n}.\n
    \n
    6. \n
\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

additions ([FileAddition!])

File to add or change.

\n\n\n\n\n\n\n\n\n\n\n\n

deletions ([FileDeletion!])

Files to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileDeletion

\n

A command to delete the file at the given path as part of a commit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n
NameDescription

path (String!)

The path to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFollowOrganizationInput

\n

Autogenerated input type of FollowOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

ID of the organization to follow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFollowUserInput

\n

Autogenerated input type of FollowUser.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

ID of the user to follow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGistOrder

\n

Ordering options for gist connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (GistOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGrantEnterpriseOrganizationsMigratorRoleInput

\n

Autogenerated input type of GrantEnterpriseOrganizationsMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which all organizations managed by it will be granted the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to grant the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGrantMigratorRoleInput

\n

Autogenerated input type of GrantMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actor (String!)

The user login or Team slug to grant the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

actorType (ActorType!)

Specifies the type of the actor, can be either USER or TEAM.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization that the user/team belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nImportProjectInput

\n

Autogenerated input type of ImportProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of Project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnImports ([ProjectColumnImport!]!)

A list of columns containing issues and pull requests.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of Project.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerName (String!)

The name of the Organization or User to create the Project under.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Whether the Project is public or not.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nInviteEnterpriseAdminInput

\n

Autogenerated input type of InviteEnterpriseAdmin.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

email (String)

The email of the person to invite as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which you want to invite an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

invitee (String)

The login of a user to invite as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

role (EnterpriseAdministratorRole)

The role of the administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIpAllowListEntryOrder

\n

Ordering options for IP allow list entry connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IpAllowListEntryOrderField!)

The field to order IP allow list entries by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueCommentOrder

\n

Ways in which lists of issue comments can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order issue comments by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IssueCommentOrderField!)

The field in which to order issue comments by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueFilters

\n

Ways in which to filter lists of issues.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignee (String)

List issues assigned to given name. Pass in null for issues with no assigned\nuser, and * for issues assigned to any user.

\n\n\n\n\n\n\n\n\n\n\n\n

createdBy (String)

List issues created by given name.

\n\n\n\n\n\n\n\n\n\n\n\n

labels ([String!])

List issues where the list of label names exist on the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

mentioned (String)

List issues where the given name is mentioned in the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestone (String)

List issues by given milestone argument. If an string representation of an\ninteger is passed, it should refer to a milestone by its database ID. Pass in\nnull for issues with no milestone, and * for issues that are assigned to any milestone.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneNumber (String)

List issues by given milestone argument. If an string representation of an\ninteger is passed, it should refer to a milestone by its number field. Pass in\nnull for issues with no milestone, and * for issues that are assigned to any milestone.

\n\n\n\n\n\n\n\n\n\n\n\n

since (DateTime)

List issues that have been updated at or after the given date.

\n\n\n\n\n\n\n\n\n\n\n\n

states ([IssueState!])

List issues filtered by the list of states given.

\n\n\n\n\n\n\n\n\n\n\n\n

viewerSubscribed (Boolean)

List issues subscribed to by viewer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueOrder

\n

Ways in which lists of issues can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order issues by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IssueOrderField!)

The field in which to order issues by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLabelOrder

\n

Ways in which lists of labels can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order labels by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (LabelOrderField!)

The field in which to order labels by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLanguageOrder

\n

Ordering options for language connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (LanguageOrderField!)

The field to order languages by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLinkRepositoryToProjectInput

\n

Autogenerated input type of LinkRepositoryToProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to link to a Repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the Repository to link to a Project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLockLockableInput

\n

Autogenerated input type of LockLockable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

lockReason (LockReason)

A reason for why the item will be locked.

\n\n\n\n\n\n\n\n\n\n\n\n

lockableId (ID!)

ID of the item to be locked.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkDiscussionCommentAsAnswerInput

\n

Autogenerated input type of MarkDiscussionCommentAsAnswer.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion comment to mark as an answer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkFileAsViewedInput

\n

Autogenerated input type of MarkFileAsViewed.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to mark as viewed.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkPullRequestReadyForReviewInput

\n

Autogenerated input type of MarkPullRequestReadyForReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be marked as ready for review.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMergeBranchInput

\n

Autogenerated input type of MergeBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this commit.

\n\n\n\n\n\n\n\n\n\n\n\n

base (String!)

The name of the base branch that the provided head will be merged into.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitMessage (String)

Message to use for the merge commit. If omitted, a default will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

head (String!)

The head to merge into the base branch. This can be a branch name or a commit GitObjectID.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the Repository containing the base branch that will be modified.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMergePullRequestInput

\n

Autogenerated input type of MergePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this merge.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitBody (String)

Commit body to use for the merge commit; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

commitHeadline (String)

Commit headline to use for the merge commit; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID)

OID that the pull request head ref must match to allow merge; if omitted, no check is performed.

\n\n\n\n\n\n\n\n\n\n\n\n

mergeMethod (PullRequestMergeMethod)

The merge method to use. If omitted, defaults to 'MERGE'.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be merged.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMilestoneOrder

\n

Ordering options for milestone connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (MilestoneOrderField!)

The field to order milestones by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMinimizeCommentInput

\n

Autogenerated input type of MinimizeComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

classifier (ReportedContentClassifiers!)

The classification of comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMoveProjectCardInput

\n

Autogenerated input type of MoveProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterCardId (ID)

Place the new card after the card with this id. Pass null to place it at the top.

\n\n\n\n\n\n\n\n\n\n\n\n

cardId (ID!)

The id of the card to move.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to move it into.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMoveProjectColumnInput

\n

Autogenerated input type of MoveProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterColumnId (ID)

Place the new column after the column with this id. Pass null to place it at the front.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to move.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nOrgEnterpriseOwnerOrder

\n

Ordering options for an organization's enterprise owner connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (OrgEnterpriseOwnerOrderField!)

The field to order enterprise owners by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nOrganizationOrder

\n

Ordering options for organization connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (OrganizationOrderField!)

The field to order organizations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPackageFileOrder

\n

Ways in which lists of package files can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The direction in which to order package files by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PackageFileOrderField)

The field in which to order package files by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPackageOrder

\n

Ways in which lists of packages can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The direction in which to order packages by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PackageOrderField)

The field in which to order packages by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPackageVersionOrder

\n

Ways in which lists of package versions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The direction in which to order package versions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PackageVersionOrderField)

The field in which to order package versions by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPinIssueInput

\n

Autogenerated input type of PinIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to be pinned.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectCardImport

\n

An issue or PR and its owning repository to be used in a project card.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

number (Int!)

The issue or pull request number.

\n\n\n\n\n\n\n\n\n\n\n\n

repository (String!)

Repository name with owner (owner/repository).

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectColumnImport

\n

A project column and a list of its issues and PRs.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

columnName (String!)

The name of the column.

\n\n\n\n\n\n\n\n\n\n\n\n

issues ([ProjectCardImport!])

A list of issues and pull requests in the column.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int!)

The position of the column, starting from 0.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectOrder

\n

Ways in which lists of projects can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order projects by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ProjectOrderField!)

The field in which to order projects by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPullRequestOrder

\n

Ways in which lists of issues can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order pull requests by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PullRequestOrderField!)

The field in which to order pull requests by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReactionOrder

\n

Ways in which lists of reactions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order reactions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ReactionOrderField!)

The field in which to order reactions by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRefOrder

\n

Ways in which lists of git refs can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order refs by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RefOrderField!)

The field in which to order refs by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRefUpdate

\n

A ref update.

\n
\n\n
\n \n
\n

Preview notice

\n

RefUpdate is available under the Update refs preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterOid (GitObjectID!)

The value this ref should be updated to.

\n\n\n\n\n\n\n\n\n\n\n\n

beforeOid (GitObjectID)

The value this ref needs to point to before the update.

\n\n\n\n\n\n\n\n\n\n\n\n

force (Boolean)

Force a non fast-forward update.

\n\n\n\n\n\n\n\n\n\n\n\n

name (GitRefname!)

The fully qualified name of the ref to be update. For example refs/heads/branch-name.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRegenerateEnterpriseIdentityProviderRecoveryCodesInput

\n

Autogenerated input type of RegenerateEnterpriseIdentityProviderRecoveryCodes.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set an identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRegenerateVerifiableDomainTokenInput

\n

Autogenerated input type of RegenerateVerifiableDomainToken.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to regenerate the verification token of.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRejectDeploymentsInput

\n

Autogenerated input type of RejectDeployments.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comment (String)

Optional comment for rejecting deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentIds ([ID!]!)

The ids of environments to reject deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

workflowRunId (ID!)

The node ID of the workflow run containing the pending deployments.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReleaseOrder

\n

Ways in which lists of releases can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order releases by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ReleaseOrderField!)

The field in which to order releases by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveAssigneesFromAssignableInput

\n

Autogenerated input type of RemoveAssigneesFromAssignable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignableId (ID!)

The id of the assignable object to remove assignees from.

\n\n\n\n\n\n\n\n\n\n\n\n

assigneeIds ([ID!]!)

The id of users to remove as assignees.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseAdminInput

\n

Autogenerated input type of RemoveEnterpriseAdmin.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The Enterprise ID from which to remove the administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to remove as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseIdentityProviderInput

\n

Autogenerated input type of RemoveEnterpriseIdentityProvider.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise from which to remove the identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseOrganizationInput

\n

Autogenerated input type of RemoveEnterpriseOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise from which the organization should be removed.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to remove from the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseSupportEntitlementInput

\n

Autogenerated input type of RemoveEnterpriseSupportEntitlement.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the admin belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of a member who will lose the support entitlement.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveLabelsFromLabelableInput

\n

Autogenerated input type of RemoveLabelsFromLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!]!)

The ids of labels to remove.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the Labelable to remove labels from.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveOutsideCollaboratorInput

\n

Autogenerated input type of RemoveOutsideCollaborator.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to remove the outside collaborator from.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

The ID of the outside collaborator to remove.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveReactionInput

\n

Autogenerated input type of RemoveReaction.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

content (ReactionContent!)

The name of the emoji reaction to remove.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveStarInput

\n

Autogenerated input type of RemoveStar.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

starrableId (ID!)

The Starrable ID to unstar.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveUpvoteInput

\n

Autogenerated input type of RemoveUpvote.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the discussion or comment to remove upvote.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReopenIssueInput

\n

Autogenerated input type of ReopenIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

ID of the issue to be opened.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReopenPullRequestInput

\n

Autogenerated input type of ReopenPullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be reopened.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryInvitationOrder

\n

Ordering options for repository invitation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryInvitationOrderField!)

The field to order repository invitations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryMigrationOrder

\n

Ordering options for repository migrations.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (RepositoryMigrationOrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryMigrationOrderField!)

The field to order repository migrations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryOrder

\n

Ordering options for repository connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRequestReviewsInput

\n

Autogenerated input type of RequestReviews.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

teamIds ([ID!])

The Node IDs of the team to request.

\n\n\n\n\n\n\n\n\n\n\n\n

union (Boolean)

Add users to the set rather than replace.

\n\n\n\n\n\n\n\n\n\n\n\n

userIds ([ID!])

The Node IDs of the user to request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRequiredStatusCheckInput

\n

Specifies the attributes for a new or updated required status check.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (ID)

The ID of the App that must set the status in order for it to be accepted.\nOmit this value to use whichever app has recently been setting this status, or\nuse "any" to allow any app to set the status.

\n\n\n\n\n\n\n\n\n\n\n\n

context (String!)

Status check context that must pass for commits to be accepted to the matching branch.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRerequestCheckSuiteInput

\n

Autogenerated input type of RerequestCheckSuite.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

checkSuiteId (ID!)

The Node ID of the check suite.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nResolveReviewThreadInput

\n

Autogenerated input type of ResolveReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

threadId (ID!)

The ID of the thread to resolve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRevokeEnterpriseOrganizationsMigratorRoleInput

\n

Autogenerated input type of RevokeEnterpriseOrganizationsMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which all organizations managed by it will be granted the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to revoke the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRevokeMigratorRoleInput

\n

Autogenerated input type of RevokeMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actor (String!)

The user login or Team slug to revoke the migrator role from.

\n\n\n\n\n\n\n\n\n\n\n\n

actorType (ActorType!)

Specifies the type of the actor, can be either USER or TEAM.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization that the user/team belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSavedReplyOrder

\n

Ordering options for saved reply connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SavedReplyOrderField!)

The field to order saved replies by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSecurityAdvisoryIdentifierFilter

\n

An advisory identifier to filter results on.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

type (SecurityAdvisoryIdentifierType!)

The identifier type.

\n\n\n\n\n\n\n\n\n\n\n\n

value (String!)

The identifier string. Supports exact or partial matching.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSecurityAdvisoryOrder

\n

Ordering options for security advisory connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SecurityAdvisoryOrderField!)

The field to order security advisories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSecurityVulnerabilityOrder

\n

Ordering options for security vulnerability connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SecurityVulnerabilityOrderField!)

The field to order security vulnerabilities by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetEnterpriseIdentityProviderInput

\n

Autogenerated input type of SetEnterpriseIdentityProvider.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

digestMethod (SamlDigestAlgorithm!)

The digest algorithm used to sign SAML requests for the identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set an identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

idpCertificate (String!)

The x509 certificate used by the identity provider to sign assertions and responses.

\n\n\n\n\n\n\n\n\n\n\n\n

issuer (String)

The Issuer Entity ID for the SAML identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

signatureMethod (SamlSignatureAlgorithm!)

The signature algorithm used to sign SAML requests for the identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

ssoUrl (URI!)

The URL endpoint for the identity provider's SAML SSO.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetOrganizationInteractionLimitInput

\n

Autogenerated input type of SetOrganizationInteractionLimit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expiry (RepositoryInteractionLimitExpiry)

When this limit should expire.

\n\n\n\n\n\n\n\n\n\n\n\n

limit (RepositoryInteractionLimit!)

The limit to set.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to set a limit for.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetRepositoryInteractionLimitInput

\n

Autogenerated input type of SetRepositoryInteractionLimit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expiry (RepositoryInteractionLimitExpiry)

When this limit should expire.

\n\n\n\n\n\n\n\n\n\n\n\n

limit (RepositoryInteractionLimit!)

The limit to set.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to set a limit for.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetUserInteractionLimitInput

\n

Autogenerated input type of SetUserInteractionLimit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expiry (RepositoryInteractionLimitExpiry)

When this limit should expire.

\n\n\n\n\n\n\n\n\n\n\n\n

limit (RepositoryInteractionLimit!)

The limit to set.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

The ID of the user to set a limit for.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorOrder

\n

Ordering options for connections to get sponsor entities for GitHub Sponsors.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorOrderField!)

The field to order sponsor entities by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorableOrder

\n

Ordering options for connections to get sponsorable entities for GitHub Sponsors.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorableOrderField!)

The field to order sponsorable entities by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorsActivityOrder

\n

Ordering options for GitHub Sponsors activity connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorsActivityOrderField!)

The field to order activity by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorsTierOrder

\n

Ordering options for Sponsors tiers connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorsTierOrderField!)

The field to order tiers by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorshipNewsletterOrder

\n

Ordering options for sponsorship newsletter connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorshipNewsletterOrderField!)

The field to order sponsorship newsletters by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorshipOrder

\n

Ordering options for sponsorship connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorshipOrderField!)

The field to order sponsorship by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nStarOrder

\n

Ways in which star connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (StarOrderField!)

The field in which to order nodes by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nStartRepositoryMigrationInput

\n

Autogenerated input type of StartRepositoryMigration.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

accessToken (String)

The Octoshift migration source access token.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

continueOnError (Boolean)

Whether to continue the migration on error.

\n\n\n\n\n\n\n\n\n\n\n\n

gitArchiveUrl (String)

The signed URL to access the user-uploaded git archive.

\n\n\n\n\n\n\n\n\n\n\n\n

githubPat (String)

The GitHub personal access token of the user importing to the target repository.

\n\n\n\n\n\n\n\n\n\n\n\n

metadataArchiveUrl (String)

The signed URL to access the user-uploaded metadata archive.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that will own the imported repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryName (String!)

The name of the imported repository.

\n\n\n\n\n\n\n\n\n\n\n\n

skipReleases (Boolean)

Whether to skip migrating releases for the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

sourceId (ID!)

The ID of the Octoshift migration source.

\n\n\n\n\n\n\n\n\n\n\n\n

sourceRepositoryUrl (URI!)

The Octoshift migration source repository URL.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSubmitPullRequestReviewInput

\n

Autogenerated input type of SubmitPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The text field to set on the Pull Request Review.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

event (PullRequestReviewEvent!)

The event to send to the Pull Request Review.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The Pull Request ID to submit any pending reviews.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Pull Request Review ID to submit.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamDiscussionCommentOrder

\n

Ways in which team discussion comment connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamDiscussionCommentOrderField!)

The field by which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamDiscussionOrder

\n

Ways in which team discussion connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamDiscussionOrderField!)

The field by which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamMemberOrder

\n

Ordering options for team member connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamMemberOrderField!)

The field to order team members by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamOrder

\n

Ways in which team connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamOrderField!)

The field in which to order nodes by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamRepositoryOrder

\n

Ordering options for team repository connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamRepositoryOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTransferIssueInput

\n

Autogenerated input type of TransferIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The Node ID of the issue to be transferred.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository the issue should be transferred to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnarchiveRepositoryInput

\n

Autogenerated input type of UnarchiveRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to unarchive.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnfollowOrganizationInput

\n

Autogenerated input type of UnfollowOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

ID of the organization to unfollow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnfollowUserInput

\n

Autogenerated input type of UnfollowUser.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

ID of the user to unfollow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnlinkRepositoryFromProjectInput

\n

Autogenerated input type of UnlinkRepositoryFromProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project linked to the Repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the Repository linked to the Project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnlockLockableInput

\n

Autogenerated input type of UnlockLockable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

lockableId (ID!)

ID of the item to be unlocked.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkDiscussionCommentAsAnswerInput

\n

Autogenerated input type of UnmarkDiscussionCommentAsAnswer.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion comment to unmark as an answer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkFileAsViewedInput

\n

Autogenerated input type of UnmarkFileAsViewed.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to mark as unviewed.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkIssueAsDuplicateInput

\n

Autogenerated input type of UnmarkIssueAsDuplicate.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

canonicalId (ID!)

ID of the issue or pull request currently considered canonical/authoritative/original.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

duplicateId (ID!)

ID of the issue or pull request currently marked as a duplicate.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnminimizeCommentInput

\n

Autogenerated input type of UnminimizeComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnpinIssueInput

\n

Autogenerated input type of UnpinIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to be unpinned.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnresolveReviewThreadInput

\n

Autogenerated input type of UnresolveReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

threadId (ID!)

The ID of the thread to unresolve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateBranchProtectionRuleInput

\n

Autogenerated input type of UpdateBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowsDeletions (Boolean)

Can this branch be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

allowsForcePushes (Boolean)

Are force pushes allowed on this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

blocksCreations (Boolean)

Is branch creation a protected operation.

\n\n\n\n\n\n\n\n\n\n\n\n

branchProtectionRuleId (ID!)

The global relay id of the branch protection rule to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassForcePushActorIds ([ID!])

A list of User or Team IDs allowed to bypass force push targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassPullRequestActorIds ([ID!])

A list of User or Team IDs allowed to bypass pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissesStaleReviews (Boolean)

Will new commits pushed to matching branches dismiss pull request review approvals.

\n\n\n\n\n\n\n\n\n\n\n\n

isAdminEnforced (Boolean)

Can admins overwrite branch protection.

\n\n\n\n\n\n\n\n\n\n\n\n

pattern (String)

The glob-like pattern used to determine matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

pushActorIds ([ID!])

A list of User, Team or App IDs allowed to push to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredApprovingReviewCount (Int)

Number of approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusCheckContexts ([String!])

List of required status check contexts that must pass for commits to be accepted to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusChecks ([RequiredStatusCheckInput!])

The list of required status checks.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresApprovingReviews (Boolean)

Are approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCodeOwnerReviews (Boolean)

Are reviews from code owners required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCommitSignatures (Boolean)

Are commits required to be signed.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresConversationResolution (Boolean)

Are conversations required to be resolved before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresLinearHistory (Boolean)

Are merge commits prohibited from being pushed to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStatusChecks (Boolean)

Are status checks required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStrictStatusChecks (Boolean)

Are branches required to be up to date before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsPushes (Boolean)

Is pushing to matching branches restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsReviewDismissals (Boolean)

Is dismissal of pull request reviews restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewDismissalActorIds ([ID!])

A list of User or Team IDs allowed to dismiss reviews on pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateCheckRunInput

\n

Autogenerated input type of UpdateCheckRun.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actions ([CheckRunAction!])

Possible further actions the integrator can perform, which a user may trigger.

\n\n\n\n\n\n\n\n\n\n\n\n

checkRunId (ID!)

The node of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

completedAt (DateTime)

The time that the check run finished.

\n\n\n\n\n\n\n\n\n\n\n\n

conclusion (CheckConclusionState)

The final conclusion of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

detailsUrl (URI)

The URL of the integrator's site that has the full details of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

externalId (String)

A reference for the run on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

output (CheckRunOutput)

Descriptive details about the run.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

startedAt (DateTime)

The time that the check run began.

\n\n\n\n\n\n\n\n\n\n\n\n

status (RequestableCheckStatusState)

The current status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateCheckSuitePreferencesInput

\n

Autogenerated input type of UpdateCheckSuitePreferences.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoTriggerPreferences ([CheckSuiteAutoTriggerPreference!]!)

The check suite preferences to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateDiscussionCommentInput

\n

Autogenerated input type of UpdateDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The new contents of the comment body.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commentId (ID!)

The Node ID of the discussion comment to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateDiscussionInput

\n

Autogenerated input type of UpdateDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The new contents of the discussion body.

\n\n\n\n\n\n\n\n\n\n\n\n

categoryId (ID)

The Node ID of a discussion category within the same repository to change this discussion to.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The Node ID of the discussion to update.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The new discussion title.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseAdministratorRoleInput

\n

Autogenerated input type of UpdateEnterpriseAdministratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the admin belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of a administrator whose role is being changed.

\n\n\n\n\n\n\n\n\n\n\n\n

role (EnterpriseAdministratorRole!)

The new role for the Enterprise administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseAllowPrivateRepositoryForkingSettingInput

\n

Autogenerated input type of UpdateEnterpriseAllowPrivateRepositoryForkingSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the allow private repository forking setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the allow private repository forking setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseDefaultRepositoryPermissionSettingInput

\n

Autogenerated input type of UpdateEnterpriseDefaultRepositoryPermissionSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the base repository permission setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseDefaultRepositoryPermissionSettingValue!)

The value for the base repository permission setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanChangeRepositoryVisibilitySettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanChangeRepositoryVisibilitySetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can change repository visibility setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can change repository visibility setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanCreateRepositoriesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanCreateRepositoriesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can create repositories setting.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreateInternalRepositories (Boolean)

Allow members to create internal repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreatePrivateRepositories (Boolean)

Allow members to create private repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreatePublicRepositories (Boolean)

Allow members to create public repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreateRepositoriesPolicyEnabled (Boolean)

When false, allow member organizations to set their own repository creation member privileges.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseMembersCanCreateRepositoriesSettingValue)

Value for the members can create repositories setting on the enterprise. This\nor the granular public/private/internal allowed fields (but not both) must be provided.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanDeleteIssuesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanDeleteIssuesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can delete issues setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can delete issues setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanDeleteRepositoriesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanDeleteRepositoriesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can delete repositories setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can delete repositories setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanInviteCollaboratorsSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanInviteCollaboratorsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can invite collaborators setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can invite collaborators setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanMakePurchasesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanMakePurchasesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can make purchases setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseMembersCanMakePurchasesSettingValue!)

The value for the members can make purchases setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanUpdateProtectedBranchesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanUpdateProtectedBranchesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can update protected branches setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can update protected branches setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanViewDependencyInsightsSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanViewDependencyInsightsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can view dependency insights setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can view dependency insights setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseOrganizationProjectsSettingInput

\n

Autogenerated input type of UpdateEnterpriseOrganizationProjectsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the organization projects setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the organization projects setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseOwnerOrganizationRoleInput

\n

Autogenerated input type of UpdateEnterpriseOwnerOrganizationRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the owner belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization for membership change.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationRole (RoleInOrganization!)

The role to assume in the organization.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseProfileInput

\n

Autogenerated input type of UpdateEnterpriseProfile.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

The description of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The Enterprise ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n

location (String)

The location of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

websiteUrl (String)

The URL of the enterprise's website.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseRepositoryProjectsSettingInput

\n

Autogenerated input type of UpdateEnterpriseRepositoryProjectsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the repository projects setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the repository projects setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseTeamDiscussionsSettingInput

\n

Autogenerated input type of UpdateEnterpriseTeamDiscussionsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the team discussions setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the team discussions setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseTwoFactorAuthenticationRequiredSettingInput

\n

Autogenerated input type of UpdateEnterpriseTwoFactorAuthenticationRequiredSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the two factor authentication required setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledSettingValue!)

The value for the two factor authentication required setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnvironmentInput

\n

Autogenerated input type of UpdateEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentId (ID!)

The node ID of the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewers ([ID!])

The ids of users or teams that can approve deployments to this environment.

\n\n\n\n\n\n\n\n\n\n\n\n

waitTimer (Int)

The wait timer in minutes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListEnabledSettingInput

\n

Autogenerated input type of UpdateIpAllowListEnabledSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner on which to set the IP allow list enabled setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (IpAllowListEnabledSettingValue!)

The value for the IP allow list enabled setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListEntryInput

\n

Autogenerated input type of UpdateIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowListValue (String!)

An IP address or range of addresses in CIDR notation.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ipAllowListEntryId (ID!)

The ID of the IP allow list entry to update.

\n\n\n\n\n\n\n\n\n\n\n\n

isActive (Boolean!)

Whether the IP allow list entry is active when an IP allow list is enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

An optional name for the IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListForInstalledAppsEnabledSettingInput

\n

Autogenerated input type of UpdateIpAllowListForInstalledAppsEnabledSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (IpAllowListForInstalledAppsEnabledSettingValue!)

The value for the IP allow list configuration for installed GitHub Apps setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIssueCommentInput

\n

Autogenerated input type of UpdateIssueComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The updated text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the IssueComment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIssueInput

\n

Autogenerated input type of UpdateIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

An array of Node IDs of users for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body for the issue description.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the Issue to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

state (IssueState)

The desired issue state.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title for the issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateLabelInput

\n

Autogenerated input type of UpdateLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

color (String)

A 6 character hex code, without the leading #, identifying the updated color of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A brief description of the label, such as its purpose.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the label to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The updated name of the label.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateNotificationRestrictionSettingInput

\n

Autogenerated input type of UpdateNotificationRestrictionSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner on which to set the restrict notifications setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (NotificationRestrictionSettingValue!)

The value for the restrict notifications setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateOrganizationAllowPrivateRepositoryForkingSettingInput

\n

Autogenerated input type of UpdateOrganizationAllowPrivateRepositoryForkingSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

forkingEnabled (Boolean!)

Enable forking of private repositories in the organization?.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization on which to set the allow private repository forking setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectCardInput

\n

Autogenerated input type of UpdateProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isArchived (Boolean)

Whether or not the ProjectCard should be archived.

\n\n\n\n\n\n\n\n\n\n\n\n

note (String)

The note of ProjectCard.

\n\n\n\n\n\n\n\n\n\n\n\n

projectCardId (ID!)

The ProjectCard ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectColumnInput

\n

Autogenerated input type of UpdateProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of project column.

\n\n\n\n\n\n\n\n\n\n\n\n

projectColumnId (ID!)

The ProjectColumn ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectDraftIssueInput

\n

Autogenerated input type of UpdateProjectDraftIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The IDs of the assignees of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

draftIssueId (ID!)

The ID of the draft issue to update.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectInput

\n

Autogenerated input type of UpdateProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of project.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Project ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Whether the project is public or not.

\n\n\n\n\n\n\n\n\n\n\n\n

state (ProjectState)

Whether the project is open or closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectNextInput

\n

Autogenerated input type of UpdateProjectNext.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

closed (Boolean)

Set the project to closed or open.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

Set the readme description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to update.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Set the project to public or private.

\n\n\n\n\n\n\n\n\n\n\n\n

shortDescription (String)

Set the short description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

Set the title of the project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectNextItemFieldInput

\n

Autogenerated input type of UpdateProjectNextItemField.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

fieldId (ID)

The id of the field to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

itemId (ID!)

The id of the item to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project.

\n\n\n\n\n\n\n\n\n\n\n\n

value (String!)

The value which will be set on the field.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestBranchInput

\n

Autogenerated input type of UpdatePullRequestBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID)

The head ref oid for the upstream branch.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestInput

\n

Autogenerated input type of UpdatePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

An array of Node IDs of users for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

baseRefName (String)

The name of the branch you want your changes pulled into. This should be an existing branch\non the current repository.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The contents of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

maintainerCanModify (Boolean)

Indicates whether maintainers can modify the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

state (PullRequestUpdateState)

The target state of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestReviewCommentInput

\n

Autogenerated input type of UpdatePullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewCommentId (ID!)

The Node ID of the comment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestReviewInput

\n

Autogenerated input type of UpdatePullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the pull request review body.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRefInput

\n

Autogenerated input type of UpdateRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

force (Boolean)

Permit updates of branch Refs that are not fast-forwards?.

\n\n\n\n\n\n\n\n\n\n\n\n

oid (GitObjectID!)

The GitObjectID that the Ref shall be updated to target.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The Node ID of the Ref to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRefsInput

\n

Autogenerated input type of UpdateRefs.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateRefsInput is available under the Update refs preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

refUpdates ([RefUpdate!]!)

A list of ref updates.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRepositoryInput

\n

Autogenerated input type of UpdateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A new description for the repository. Pass an empty string to erase the existing description.

\n\n\n\n\n\n\n\n\n\n\n\n

hasIssuesEnabled (Boolean)

Indicates if the repository should have the issues feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasProjectsEnabled (Boolean)

Indicates if the repository should have the project boards feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasWikiEnabled (Boolean)

Indicates if the repository should have the wiki feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

homepageUrl (URI)

The URL for a web page about this repository. Pass an empty string to erase the existing URL.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The new name of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to update.

\n\n\n\n\n\n\n\n\n\n\n\n

template (Boolean)

Whether this repository should be marked as a template such that anyone who\ncan access it can create new repositories with the same files and directory structure.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateSponsorshipPreferencesInput

\n

Autogenerated input type of UpdateSponsorshipPreferences.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

privacyLevel (SponsorshipPrivacy)

Specify whether others should be able to see that the sponsor is sponsoring\nthe sponsorable. Public visibility still does not reveal which tier is used.

\n\n\n\n\n\n\n\n\n\n\n\n

receiveEmails (Boolean)

Whether the sponsor should receive email updates from the sponsorable.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorId (ID)

The ID of the user or organization who is acting as the sponsor, paying for\nthe sponsorship. Required if sponsorLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorLogin (String)

The username of the user or organization who is acting as the sponsor, paying\nfor the sponsorship. Required if sponsorId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who is receiving the sponsorship. Required if sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who is receiving the sponsorship. Required if sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateSubscriptionInput

\n

Autogenerated input type of UpdateSubscription.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

state (SubscriptionState!)

The new state of the subscription.

\n\n\n\n\n\n\n\n\n\n\n\n

subscribableId (ID!)

The Node ID of the subscribable object to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamDiscussionCommentInput

\n

Autogenerated input type of UpdateTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The updated text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

bodyVersion (String)

The current version of the body content.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamDiscussionInput

\n

Autogenerated input type of UpdateTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The updated text of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

bodyVersion (String)

The current version of the body content. If provided, this update operation\nwill be rejected if the given version does not match the latest version on the server.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

pinned (Boolean)

If provided, sets the pinned state of the updated discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The updated title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamReviewAssignmentInput

\n

Autogenerated input type of UpdateTeamReviewAssignment.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateTeamReviewAssignmentInput is available under the Team review assignments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

algorithm (TeamReviewAssignmentAlgorithm)

The algorithm to use for review assignment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enabled (Boolean!)

Turn on or off review assignment.

\n\n\n\n\n\n\n\n\n\n\n\n

excludedTeamMemberIds ([ID!])

An array of team member IDs to exclude.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the team to update review assignments of.

\n\n\n\n\n\n\n\n\n\n\n\n

notifyTeam (Boolean)

Notify the entire team of the PR if it is delegated.

\n\n\n\n\n\n\n\n\n\n\n\n

teamMemberCount (Int)

The number of team members to assign.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamsRepositoryInput

\n

Autogenerated input type of UpdateTeamsRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

permission (RepositoryPermission!)

Permission that should be granted to the teams.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

Repository ID being granted access to.

\n\n\n\n\n\n\n\n\n\n\n\n

teamIds ([ID!]!)

A list of teams being granted access. Limit: 10.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTopicsInput

\n

Autogenerated input type of UpdateTopics.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

topicNames ([String!]!)

An array of topic names.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUserStatusOrder

\n

Ordering options for user status connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (UserStatusOrderField!)

The field to order user statuses by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nVerifiableDomainOrder

\n

Ordering options for verifiable domain connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (VerifiableDomainOrderField!)

The field to order verifiable domains by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nVerifyVerifiableDomainInput

\n

Autogenerated input type of VerifyVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to verify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n", + "html": "
\n
\n

\n \n \nAbortQueuedMigrationsInput

\n

Autogenerated input type of AbortQueuedMigrations.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that is running the migrations.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAcceptEnterpriseAdministratorInvitationInput

\n

Autogenerated input type of AcceptEnterpriseAdministratorInvitation.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

invitationId (ID!)

The id of the invitation being accepted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAcceptTopicSuggestionInput

\n

Autogenerated input type of AcceptTopicSuggestion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the suggested topic.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddAssigneesToAssignableInput

\n

Autogenerated input type of AddAssigneesToAssignable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignableId (ID!)

The id of the assignable object to add assignees to.

\n\n\n\n\n\n\n\n\n\n\n\n

assigneeIds ([ID!]!)

The id of users to add as assignees.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddCommentInput

\n

Autogenerated input type of AddComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddDiscussionCommentInput

\n

Autogenerated input type of AddDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The Node ID of the discussion to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

replyToId (ID)

The Node ID of the discussion comment within this discussion to reply to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddEnterpriseSupportEntitlementInput

\n

Autogenerated input type of AddEnterpriseSupportEntitlement.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the admin belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of a member who will receive the support entitlement.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddLabelsToLabelableInput

\n

Autogenerated input type of AddLabelsToLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!]!)

The ids of the labels to add.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the labelable object to add labels to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectCardInput

\n

Autogenerated input type of AddProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

contentId (ID)

The content of the card. Must be a member of the ProjectCardItem union.

\n\n\n\n\n\n\n\n\n\n\n\n

note (String)

The note on the card.

\n\n\n\n\n\n\n\n\n\n\n\n

projectColumnId (ID!)

The Node ID of the ProjectColumn.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectColumnInput

\n

Autogenerated input type of AddProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the column.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Node ID of the project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectDraftIssueInput

\n

Autogenerated input type of AddProjectDraftIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The IDs of the assignees of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to add the draft issue to.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectNextItemInput

\n

Autogenerated input type of AddProjectNextItem.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

contentId (ID!)

The content id of the item (Issue or PullRequest).

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to add the item to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewCommentInput

\n

Autogenerated input type of AddPullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitOID (GitObjectID)

The SHA of the commit to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

inReplyTo (ID)

The comment id to reply to.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String)

The relative path of the file to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int)

The line index in the diff to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The node ID of the pull request reviewing.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Node ID of the review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewInput

\n

Autogenerated input type of AddPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The contents of the review body comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comments ([DraftPullRequestReviewComment])

The review line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

commitOID (GitObjectID)

The commit OID the review pertains to.

\n\n\n\n\n\n\n\n\n\n\n\n

event (PullRequestReviewEvent)

The event to perform on the pull request review.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

threads ([DraftPullRequestReviewThread])

The review line comment threads.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewThreadInput

\n

Autogenerated input type of AddPullRequestReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the thread's first comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

line (Int!)

The line of the blob to which the thread refers. The end of the line range for multi-line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The node ID of the pull request reviewing.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Node ID of the review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

side (DiffSide)

The side of the diff on which the line resides. For multi-line comments, this is the side for the end of the line range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int)

The first line of the range to which the comment refers.

\n\n\n\n\n\n\n\n\n\n\n\n

startSide (DiffSide)

The side of the diff on which the start line resides.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddReactionInput

\n

Autogenerated input type of AddReaction.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

content (ReactionContent!)

The name of the emoji to react with.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddStarInput

\n

Autogenerated input type of AddStar.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

starrableId (ID!)

The Starrable ID to star.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddUpvoteInput

\n

Autogenerated input type of AddUpvote.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the discussion or comment to upvote.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddVerifiableDomainInput

\n

Autogenerated input type of AddVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

domain (URI!)

The URL of the domain.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner to add the domain to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nApproveDeploymentsInput

\n

Autogenerated input type of ApproveDeployments.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comment (String)

Optional comment for approving deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentIds ([ID!]!)

The ids of environments to reject deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

workflowRunId (ID!)

The node ID of the workflow run containing the pending deployments.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nApproveVerifiableDomainInput

\n

Autogenerated input type of ApproveVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to approve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nArchiveRepositoryInput

\n

Autogenerated input type of ArchiveRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to mark as archived.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAuditLogOrder

\n

Ordering options for Audit Log connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (AuditLogOrderField)

The field to order Audit Logs by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCancelEnterpriseAdminInvitationInput

\n

Autogenerated input type of CancelEnterpriseAdminInvitation.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

invitationId (ID!)

The Node ID of the pending enterprise administrator invitation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCancelSponsorshipInput

\n

Autogenerated input type of CancelSponsorship.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorId (ID)

The ID of the user or organization who is acting as the sponsor, paying for\nthe sponsorship. Required if sponsorLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorLogin (String)

The username of the user or organization who is acting as the sponsor, paying\nfor the sponsorship. Required if sponsorId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who is receiving the sponsorship. Required if sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who is receiving the sponsorship. Required if sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nChangeUserStatusInput

\n

Autogenerated input type of ChangeUserStatus.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

emoji (String)

The emoji to represent your status. Can either be a native Unicode emoji or an emoji name with colons, e.g., 😀.

\n\n\n\n\n\n\n\n\n\n\n\n

expiresAt (DateTime)

If set, the user status will not be shown after this date.

\n\n\n\n\n\n\n\n\n\n\n\n

limitedAvailability (Boolean)

Whether this status should indicate you are not fully available on GitHub, e.g., you are away.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String)

A short description of your current status.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID)

The ID of the organization whose members will be allowed to see the status. If\nomitted, the status will be publicly visible.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckAnnotationData

\n

Information from a check run analysis to specific lines of code.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

annotationLevel (CheckAnnotationLevel!)

Represents an annotation's information level.

\n\n\n\n\n\n\n\n\n\n\n\n

location (CheckAnnotationRange!)

The location of the annotation.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String!)

A short description of the feedback for these lines of code.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to add an annotation to.

\n\n\n\n\n\n\n\n\n\n\n\n

rawDetails (String)

Details about this annotation.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title that represents the annotation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckAnnotationRange

\n

Information from a check run analysis to specific lines of code.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

endColumn (Int)

The ending column of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

endLine (Int!)

The ending line of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

startColumn (Int)

The starting column of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int!)

The starting line of the range.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunAction

\n

Possible further actions the integrator can perform.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

description (String!)

A short explanation of what this action would do.

\n\n\n\n\n\n\n\n\n\n\n\n

identifier (String!)

A reference for the action on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

label (String!)

The text to be displayed on a button in the web UI.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunFilter

\n

The filters that are available when fetching check runs.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (Int)

Filters the check runs created by this application ID.

\n\n\n\n\n\n\n\n\n\n\n\n

checkName (String)

Filters the check runs by this name.

\n\n\n\n\n\n\n\n\n\n\n\n

checkType (CheckRunType)

Filters the check runs by this type.

\n\n\n\n\n\n\n\n\n\n\n\n

status (CheckStatusState)

Filters the check runs by this status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunOutput

\n

Descriptive details about the check run.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

annotations ([CheckAnnotationData!])

The annotations that are made as part of the check run.

\n\n\n\n\n\n\n\n\n\n\n\n

images ([CheckRunOutputImage!])

Images attached to the check run output displayed in the GitHub pull request UI.

\n\n\n\n\n\n\n\n\n\n\n\n

summary (String!)

The summary of the check run (supports Commonmark).

\n\n\n\n\n\n\n\n\n\n\n\n

text (String)

The details of the check run (supports Commonmark).

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

A title to provide for this check run.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunOutputImage

\n

Images attached to the check run output displayed in the GitHub pull request UI.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

alt (String!)

The alternative text for the image.

\n\n\n\n\n\n\n\n\n\n\n\n

caption (String)

A short image description.

\n\n\n\n\n\n\n\n\n\n\n\n

imageUrl (URI!)

The full URL of the image.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckSuiteAutoTriggerPreference

\n

The auto-trigger preferences that are available for check suites.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (ID!)

The node ID of the application that owns the check suite.

\n\n\n\n\n\n\n\n\n\n\n\n

setting (Boolean!)

Set to true to enable automatic creation of CheckSuite events upon pushes to the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckSuiteFilter

\n

The filters that are available when fetching check suites.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (Int)

Filters the check suites created by this application ID.

\n\n\n\n\n\n\n\n\n\n\n\n

checkName (String)

Filters the check suites by this name.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nClearLabelsFromLabelableInput

\n

Autogenerated input type of ClearLabelsFromLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the labelable object to clear the labels from.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloneProjectInput

\n

Autogenerated input type of CloneProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

includeWorkflows (Boolean!)

Whether or not to clone the source project's workflows.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

The visibility of the project, defaults to false (private).

\n\n\n\n\n\n\n\n\n\n\n\n

sourceId (ID!)

The source project to clone.

\n\n\n\n\n\n\n\n\n\n\n\n

targetOwnerId (ID!)

The owner ID to create the project under.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloneTemplateRepositoryInput

\n

Autogenerated input type of CloneTemplateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

includeAllBranches (Boolean)

Whether to copy all branches from the template to the new repository. Defaults\nto copying only the default branch of the template.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner for the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the template repository.

\n\n\n\n\n\n\n\n\n\n\n\n

visibility (RepositoryVisibility!)

Indicates the repository's visibility level.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloseIssueInput

\n

Autogenerated input type of CloseIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

ID of the issue to be closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nClosePullRequestInput

\n

Autogenerated input type of ClosePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitAuthor

\n

Specifies an author for filtering Git commits.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

emails ([String!])

Email addresses to filter by. Commits authored by any of the specified email addresses will be returned.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID)

ID of a User to filter by. If non-null, only commits authored by this user\nwill be returned. This field takes precedence over emails.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitContributionOrder

\n

Ordering options for commit contribution connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (CommitContributionOrderField!)

The field by which to order commit contributions.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitMessage

\n

A message to include with a new commit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The body of the message.

\n\n\n\n\n\n\n\n\n\n\n\n

headline (String!)

The headline of the message.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommittableBranch

\n

A git ref for a commit to be appended to.

\n

The ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).

\n

The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.

\n

Examples

\n

Specify a branch using a global node ID:

\n
{ "id": "MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=" }\n
\n

Specify a branch using nameWithOwner and branch name:

\n
{\n  "nameWithOwner": "github/graphql-client",\n  "branchName": "main"\n}.\n
\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branchName (String)

The unqualified name of the branch to append the commit to.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID)

The Node ID of the Ref to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryNameWithOwner (String)

The nameWithOwner of the repository to commit to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nContributionOrder

\n

Ordering options for contribution connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nConvertProjectCardNoteToIssueInput

\n

Autogenerated input type of ConvertProjectCardNoteToIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The body of the newly created issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectCardId (ID!)

The ProjectCard ID to convert.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to create the issue in.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the newly created issue. Defaults to the card's note text.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nConvertPullRequestToDraftInput

\n

Autogenerated input type of ConvertPullRequestToDraft.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to convert to draft.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateBranchProtectionRuleInput

\n

Autogenerated input type of CreateBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowsDeletions (Boolean)

Can this branch be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

allowsForcePushes (Boolean)

Are force pushes allowed on this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

blocksCreations (Boolean)

Is branch creation a protected operation.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassForcePushActorIds ([ID!])

A list of User or Team IDs allowed to bypass force push targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassPullRequestActorIds ([ID!])

A list of User or Team IDs allowed to bypass pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissesStaleReviews (Boolean)

Will new commits pushed to matching branches dismiss pull request review approvals.

\n\n\n\n\n\n\n\n\n\n\n\n

isAdminEnforced (Boolean)

Can admins overwrite branch protection.

\n\n\n\n\n\n\n\n\n\n\n\n

pattern (String!)

The glob-like pattern used to determine matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

pushActorIds ([ID!])

A list of User, Team, or App IDs allowed to push to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The global relay id of the repository in which a new branch protection rule should be created in.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredApprovingReviewCount (Int)

Number of approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusCheckContexts ([String!])

List of required status check contexts that must pass for commits to be accepted to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusChecks ([RequiredStatusCheckInput!])

The list of required status checks.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresApprovingReviews (Boolean)

Are approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCodeOwnerReviews (Boolean)

Are reviews from code owners required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCommitSignatures (Boolean)

Are commits required to be signed.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresConversationResolution (Boolean)

Are conversations required to be resolved before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresLinearHistory (Boolean)

Are merge commits prohibited from being pushed to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStatusChecks (Boolean)

Are status checks required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStrictStatusChecks (Boolean)

Are branches required to be up to date before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsPushes (Boolean)

Is pushing to matching branches restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsReviewDismissals (Boolean)

Is dismissal of pull request reviews restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewDismissalActorIds ([ID!])

A list of User or Team IDs allowed to dismiss reviews on pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCheckRunInput

\n

Autogenerated input type of CreateCheckRun.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actions ([CheckRunAction!])

Possible further actions the integrator can perform, which a user may trigger.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

completedAt (DateTime)

The time that the check run finished.

\n\n\n\n\n\n\n\n\n\n\n\n

conclusion (CheckConclusionState)

The final conclusion of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

detailsUrl (URI)

The URL of the integrator's site that has the full details of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

externalId (String)

A reference for the run on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

headSha (GitObjectID!)

The SHA of the head commit.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

output (CheckRunOutput)

Descriptive details about the run.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

startedAt (DateTime)

The time that the check run began.

\n\n\n\n\n\n\n\n\n\n\n\n

status (RequestableCheckStatusState)

The current status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCheckSuiteInput

\n

Autogenerated input type of CreateCheckSuite.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

headSha (GitObjectID!)

The SHA of the head commit.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCommitOnBranchInput

\n

Autogenerated input type of CreateCommitOnBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branch (CommittableBranch!)

The Ref to be updated. Must be a branch.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID!)

The git commit oid expected at the head of the branch prior to the commit.

\n\n\n\n\n\n\n\n\n\n\n\n

fileChanges (FileChanges)

A description of changes to files in this commit.

\n\n\n\n\n\n\n\n\n\n\n\n

message (CommitMessage!)

The commit message the be included with the commit.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDeploymentInput

\n

Autogenerated input type of CreateDeployment.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateDeploymentInput is available under the Deployments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoMerge (Boolean)

Attempt to automatically merge the default branch into the requested ref, defaults to true.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

Short description of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

environment (String)

Name for the target deployment environment.

\n\n\n\n\n\n\n\n\n\n\n\n

payload (String)

JSON payload with extra information about the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The node ID of the ref to be deployed.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredContexts ([String!])

The status contexts to verify against commit status checks. To bypass required\ncontexts, pass an empty array. Defaults to all unique contexts.

\n\n\n\n\n\n\n\n\n\n\n\n

task (String)

Specifies a task to execute.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDeploymentStatusInput

\n

Autogenerated input type of CreateDeploymentStatus.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateDeploymentStatusInput is available under the Deployments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoInactive (Boolean)

Adds a new inactive status to all non-transient, non-production environment\ndeployments with the same repository and environment name as the created\nstatus's deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

deploymentId (ID!)

The node ID of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the status. Maximum length of 140 characters.

\n\n\n\n\n\n\n\n\n\n\n\n

environment (String)

If provided, updates the environment of the deploy. Otherwise, does not modify the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentUrl (String)

Sets the URL for accessing your environment.

\n\n\n\n\n\n\n\n\n\n\n\n

logUrl (String)

The log URL to associate with this status. This URL should contain\noutput to keep the user updated while the task is running or serve as\nhistorical information for what happened in the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

state (DeploymentStatusState!)

The state of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDiscussionInput

\n

Autogenerated input type of CreateDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The body of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

categoryId (ID!)

The id of the discussion category to associate with this discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The id of the repository on which to create the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateEnterpriseOrganizationInput

\n

Autogenerated input type of CreateEnterpriseOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

adminLogins ([String!]!)

The logins for the administrators of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

billingEmail (String!)

The email used for sending billing receipts.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise owning the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

profileName (String!)

The profile name of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateEnvironmentInput

\n

Autogenerated input type of CreateEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateIpAllowListEntryInput

\n

Autogenerated input type of CreateIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowListValue (String!)

An IP address or range of addresses in CIDR notation.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isActive (Boolean!)

Whether the IP allow list entry is active when an IP allow list is enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

An optional name for the IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner for which to create the new IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateIssueInput

\n

Autogenerated input type of CreateIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The Node ID for the user assignee for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body for the issue description.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueTemplate (String)

The name of an issue template in the repository, assigns labels and assignees from the template to the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title for the issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateLabelInput

\n

Autogenerated input type of CreateLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

color (String!)

A 6 character hex code, without the leading #, identifying the color of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A brief description of the label, such as its purpose.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateMigrationSourceInput

\n

Autogenerated input type of CreateMigrationSource.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

accessToken (String)

The Octoshift migration source access token.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

githubPat (String)

The GitHub personal access token of the user importing to the target repository.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The Octoshift migration source name.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that will own the Octoshift migration source.

\n\n\n\n\n\n\n\n\n\n\n\n

type (MigrationSourceType!)

The Octoshift migration source type.

\n\n\n\n\n\n\n\n\n\n\n\n

url (String!)

The Octoshift migration source URL.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateProjectInput

\n

Autogenerated input type of CreateProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of project.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The owner ID to create the project under.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryIds ([ID!])

A list of repository IDs to create as linked repositories for the project.

\n\n\n\n\n\n\n\n\n\n\n\n

template (ProjectTemplate)

The name of the GitHub-provided template.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreatePullRequestInput

\n

Autogenerated input type of CreatePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

baseRefName (String!)

The name of the branch you want your changes pulled into. This should be an existing branch\non the current repository. You cannot update the base branch on a pull request to point\nto another repository.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The contents of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

draft (Boolean)

Indicates whether this pull request should be a draft.

\n\n\n\n\n\n\n\n\n\n\n\n

headRefName (String!)

The name of the branch where your changes are implemented. For cross-repository pull requests\nin the same network, namespace head_ref_name with a user like this: username:branch.

\n\n\n\n\n\n\n\n\n\n\n\n

maintainerCanModify (Boolean)

Indicates whether maintainers can modify the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateRefInput

\n

Autogenerated input type of CreateRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The fully qualified name of the new Ref (ie: refs/heads/my_new_branch).

\n\n\n\n\n\n\n\n\n\n\n\n

oid (GitObjectID!)

The GitObjectID that the new Ref shall target. Must point to a commit.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the Repository to create the Ref in.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateRepositoryInput

\n

Autogenerated input type of CreateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

hasIssuesEnabled (Boolean)

Indicates if the repository should have the issues feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasWikiEnabled (Boolean)

Indicates if the repository should have the wiki feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

homepageUrl (URI)

The URL for a web page about this repository.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID)

The ID of the owner for the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

teamId (ID)

When an organization is specified as the owner, this ID identifies the team\nthat should be granted access to the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

template (Boolean)

Whether this repository should be marked as a template such that anyone who\ncan access it can create new repositories with the same files and directory structure.

\n\n\n\n\n\n\n\n\n\n\n\n

visibility (RepositoryVisibility!)

Indicates the repository's visibility level.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateSponsorsTierInput

\n

Autogenerated input type of CreateSponsorsTier.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

amount (Int!)

The value of the new tier in US dollars. Valid values: 1-12000.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String!)

A description of what this tier is, what perks sponsors might receive, what a sponsorship at this tier means for you, etc.

\n\n\n\n\n\n\n\n\n\n\n\n

isRecurring (Boolean)

Whether sponsorships using this tier should happen monthly/yearly or just once.

\n\n\n\n\n\n\n\n\n\n\n\n

publish (Boolean)

Whether to make the tier available immediately for sponsors to choose.\nDefaults to creating a draft tier that will not be publicly visible.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID)

Optional ID of the private repository that sponsors at this tier should gain\nread-only access to. Must be owned by an organization.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryName (String)

Optional name of the private repository that sponsors at this tier should gain\nread-only access to. Must be owned by an organization. Necessary if\nrepositoryOwnerLogin is given. Will be ignored if repositoryId is given.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryOwnerLogin (String)

Optional login of the organization owner of the private repository that\nsponsors at this tier should gain read-only access to. Necessary if\nrepositoryName is given. Will be ignored if repositoryId is given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who owns the GitHub Sponsors profile.\nDefaults to the current user if omitted and sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who owns the GitHub Sponsors profile.\nDefaults to the current user if omitted and sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

welcomeMessage (String)

Optional message new sponsors at this tier will receive.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateSponsorshipInput

\n

Autogenerated input type of CreateSponsorship.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

amount (Int)

The amount to pay to the sponsorable in US dollars. Required if a tierId is not specified. Valid values: 1-12000.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isRecurring (Boolean)

Whether the sponsorship should happen monthly/yearly or just this one time. Required if a tierId is not specified.

\n\n\n\n\n\n\n\n\n\n\n\n

privacyLevel (SponsorshipPrivacy)

Specify whether others should be able to see that the sponsor is sponsoring\nthe sponsorable. Public visibility still does not reveal which tier is used.

\n\n\n\n\n\n\n\n\n\n\n\n

receiveEmails (Boolean)

Whether the sponsor should receive email updates from the sponsorable.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorId (ID)

The ID of the user or organization who is acting as the sponsor, paying for\nthe sponsorship. Required if sponsorLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorLogin (String)

The username of the user or organization who is acting as the sponsor, paying\nfor the sponsorship. Required if sponsorId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who is receiving the sponsorship. Required if sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who is receiving the sponsorship. Required if sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

tierId (ID)

The ID of one of sponsorable's existing tiers to sponsor at. Required if amount is not specified.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateTeamDiscussionCommentInput

\n

Autogenerated input type of CreateTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The content of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The ID of the discussion to which the comment belongs.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateTeamDiscussionInput

\n

Autogenerated input type of CreateTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The content of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

private (Boolean)

If true, restricts the visibility of this discussion to team members and\norganization admins. If false or not specified, allows any organization member\nto view this discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

teamId (ID!)

The ID of the team to which the discussion belongs.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeclineTopicSuggestionInput

\n

Autogenerated input type of DeclineTopicSuggestion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the suggested topic.

\n\n\n\n\n\n\n\n\n\n\n\n

reason (TopicSuggestionDeclineReason!)

The reason why the suggested topic is declined.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteBranchProtectionRuleInput

\n

Autogenerated input type of DeleteBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branchProtectionRuleId (ID!)

The global relay id of the branch protection rule to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDeploymentInput

\n

Autogenerated input type of DeleteDeployment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the deployment to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDiscussionCommentInput

\n

Autogenerated input type of DeleteDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node id of the discussion comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDiscussionInput

\n

Autogenerated input type of DeleteDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The id of the discussion to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteEnvironmentInput

\n

Autogenerated input type of DeleteEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the environment to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIpAllowListEntryInput

\n

Autogenerated input type of DeleteIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ipAllowListEntryId (ID!)

The ID of the IP allow list entry to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIssueCommentInput

\n

Autogenerated input type of DeleteIssueComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIssueInput

\n

Autogenerated input type of DeleteIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteLabelInput

\n

Autogenerated input type of DeleteLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

DeleteLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the label to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePackageVersionInput

\n

Autogenerated input type of DeletePackageVersion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

packageVersionId (ID!)

The ID of the package version to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectCardInput

\n

Autogenerated input type of DeleteProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

cardId (ID!)

The id of the card to delete.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectColumnInput

\n

Autogenerated input type of DeleteProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectInput

\n

Autogenerated input type of DeleteProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Project ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectNextItemInput

\n

Autogenerated input type of DeleteProjectNextItem.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

itemId (ID!)

The ID of the item to be removed.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project from which the item should be removed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePullRequestReviewCommentInput

\n

Autogenerated input type of DeletePullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePullRequestReviewInput

\n

Autogenerated input type of DeletePullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteRefInput

\n

Autogenerated input type of DeleteRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The Node ID of the Ref to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteTeamDiscussionCommentInput

\n

Autogenerated input type of DeleteTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteTeamDiscussionInput

\n

Autogenerated input type of DeleteTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The discussion ID to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteVerifiableDomainInput

\n

Autogenerated input type of DeleteVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeploymentOrder

\n

Ordering options for deployment connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (DeploymentOrderField!)

The field to order deployments by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDisablePullRequestAutoMergeInput

\n

Autogenerated input type of DisablePullRequestAutoMerge.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to disable auto merge on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDiscussionOrder

\n

Ways in which lists of discussions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order discussions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (DiscussionOrderField!)

The field by which to order discussions.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDismissPullRequestReviewInput

\n

Autogenerated input type of DismissPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String!)

The contents of the pull request review dismissal message.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDismissRepositoryVulnerabilityAlertInput

\n

Autogenerated input type of DismissRepositoryVulnerabilityAlert.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissReason (DismissReason!)

The reason the Dependabot alert is being dismissed.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryVulnerabilityAlertId (ID!)

The Dependabot alert ID to dismiss.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDraftPullRequestReviewComment

\n

Specifies a review comment to be left with a Pull Request Review.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the comment to leave.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int!)

Position in the file to leave a comment on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDraftPullRequestReviewThread

\n

Specifies a review comment thread to be left with a Pull Request Review.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the comment to leave.

\n\n\n\n\n\n\n\n\n\n\n\n

line (Int!)

The line of the blob to which the thread refers. The end of the line range for multi-line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

side (DiffSide)

The side of the diff on which the line resides. For multi-line comments, this is the side for the end of the line range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int)

The first line of the range to which the comment refers.

\n\n\n\n\n\n\n\n\n\n\n\n

startSide (DiffSide)

The side of the diff on which the start line resides.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnablePullRequestAutoMergeInput

\n

Autogenerated input type of EnablePullRequestAutoMerge.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this merge.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitBody (String)

Commit body to use for the commit when the PR is mergable; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

commitHeadline (String)

Commit headline to use for the commit when the PR is mergable; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

mergeMethod (PullRequestMergeMethod)

The merge method to use. If omitted, defaults to 'MERGE'.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to enable auto-merge on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseAdministratorInvitationOrder

\n

Ordering options for enterprise administrator invitation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseAdministratorInvitationOrderField!)

The field to order enterprise administrator invitations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseMemberOrder

\n

Ordering options for enterprise member connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseMemberOrderField!)

The field to order enterprise members by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerInstallationOrder

\n

Ordering options for Enterprise Server installation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerInstallationOrderField!)

The field to order Enterprise Server installations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountEmailOrder

\n

Ordering options for Enterprise Server user account email connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountEmailOrderField!)

The field to order emails by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountOrder

\n

Ordering options for Enterprise Server user account connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountOrderField!)

The field to order user accounts by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountsUploadOrder

\n

Ordering options for Enterprise Server user accounts upload connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountsUploadOrderField!)

The field to order user accounts uploads by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileAddition

\n

A command to add a file at the given path with the given contents as part of a\ncommit. Any existing file at that that path will be replaced.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

contents (Base64String!)

The base64 encoded contents of the file.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path in the repository where the file will be located.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileChanges

\n

A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file additions and zero or more\nfile deletions.

\n

Both fields are optional; omitting both will produce a commit with no\nfile changes.

\n

deletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.

\n

path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.

\n

Encoding

\n

File contents must be provided in full for each FileAddition.

\n

The contents of a FileAddition must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.

\n

The encoded contents may be binary.

\n

For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (\\n or \\r\\n), and that all files end\nwith a newline.

\n

Modeling file changes

\n

Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:

\n
    \n
  1. \n

    New file addition: create file hello world\\n at path docs/README.txt:

    \n

    {\n"additions" [\n{\n"path": "docs/README.txt",\n"contents": base64encode("hello world\\n")\n}\n]\n}

    \n
    2. \n
  2. \n

    Existing file modification: change existing docs/README.txt to have new\ncontent new content here\\n:

    \n
    {\n  "additions" [\n    {\n      "path": "docs/README.txt",\n      "contents": base64encode("new content here\\n")\n    }\n  ]\n}\n
    \n
    3. \n
  3. \n

    Existing file deletion: remove existing file docs/README.txt.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt"\n    }\n  ]\n}\n
    \n
    4. \n
  4. \n

    File rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt",\n    }\n  ],\n  "additions" [\n    {\n      "path": "newdocs/README.txt",\n      "contents": base64encode("hello world\\n")\n    }\n  ]\n}\n
    \n
    5. \n
  5. \n

    File rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt",\n    }\n  ],\n  "additions" [\n    {\n      "path": "newdocs/README.txt",\n      "contents": base64encode("new contents\\n")\n    }\n  ]\n}.\n
    \n
    6. \n
\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

additions ([FileAddition!])

File to add or change.

\n\n\n\n\n\n\n\n\n\n\n\n

deletions ([FileDeletion!])

Files to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileDeletion

\n

A command to delete the file at the given path as part of a commit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n
NameDescription

path (String!)

The path to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFollowOrganizationInput

\n

Autogenerated input type of FollowOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

ID of the organization to follow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFollowUserInput

\n

Autogenerated input type of FollowUser.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

ID of the user to follow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGistOrder

\n

Ordering options for gist connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (GistOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGrantEnterpriseOrganizationsMigratorRoleInput

\n

Autogenerated input type of GrantEnterpriseOrganizationsMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which all organizations managed by it will be granted the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to grant the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGrantMigratorRoleInput

\n

Autogenerated input type of GrantMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actor (String!)

The user login or Team slug to grant the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

actorType (ActorType!)

Specifies the type of the actor, can be either USER or TEAM.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization that the user/team belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nImportProjectInput

\n

Autogenerated input type of ImportProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of Project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnImports ([ProjectColumnImport!]!)

A list of columns containing issues and pull requests.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of Project.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerName (String!)

The name of the Organization or User to create the Project under.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Whether the Project is public or not.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nInviteEnterpriseAdminInput

\n

Autogenerated input type of InviteEnterpriseAdmin.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

email (String)

The email of the person to invite as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which you want to invite an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

invitee (String)

The login of a user to invite as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

role (EnterpriseAdministratorRole)

The role of the administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIpAllowListEntryOrder

\n

Ordering options for IP allow list entry connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IpAllowListEntryOrderField!)

The field to order IP allow list entries by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueCommentOrder

\n

Ways in which lists of issue comments can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order issue comments by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IssueCommentOrderField!)

The field in which to order issue comments by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueFilters

\n

Ways in which to filter lists of issues.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignee (String)

List issues assigned to given name. Pass in null for issues with no assigned\nuser, and * for issues assigned to any user.

\n\n\n\n\n\n\n\n\n\n\n\n

createdBy (String)

List issues created by given name.

\n\n\n\n\n\n\n\n\n\n\n\n

labels ([String!])

List issues where the list of label names exist on the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

mentioned (String)

List issues where the given name is mentioned in the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestone (String)

List issues by given milestone argument. If an string representation of an\ninteger is passed, it should refer to a milestone by its database ID. Pass in\nnull for issues with no milestone, and * for issues that are assigned to any milestone.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneNumber (String)

List issues by given milestone argument. If an string representation of an\ninteger is passed, it should refer to a milestone by its number field. Pass in\nnull for issues with no milestone, and * for issues that are assigned to any milestone.

\n\n\n\n\n\n\n\n\n\n\n\n

since (DateTime)

List issues that have been updated at or after the given date.

\n\n\n\n\n\n\n\n\n\n\n\n

states ([IssueState!])

List issues filtered by the list of states given.

\n\n\n\n\n\n\n\n\n\n\n\n

viewerSubscribed (Boolean)

List issues subscribed to by viewer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueOrder

\n

Ways in which lists of issues can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order issues by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IssueOrderField!)

The field in which to order issues by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLabelOrder

\n

Ways in which lists of labels can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order labels by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (LabelOrderField!)

The field in which to order labels by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLanguageOrder

\n

Ordering options for language connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (LanguageOrderField!)

The field to order languages by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLinkRepositoryToProjectInput

\n

Autogenerated input type of LinkRepositoryToProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to link to a Repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the Repository to link to a Project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLockLockableInput

\n

Autogenerated input type of LockLockable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

lockReason (LockReason)

A reason for why the item will be locked.

\n\n\n\n\n\n\n\n\n\n\n\n

lockableId (ID!)

ID of the item to be locked.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkDiscussionCommentAsAnswerInput

\n

Autogenerated input type of MarkDiscussionCommentAsAnswer.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion comment to mark as an answer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkFileAsViewedInput

\n

Autogenerated input type of MarkFileAsViewed.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to mark as viewed.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkPullRequestReadyForReviewInput

\n

Autogenerated input type of MarkPullRequestReadyForReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be marked as ready for review.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMergeBranchInput

\n

Autogenerated input type of MergeBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this commit.

\n\n\n\n\n\n\n\n\n\n\n\n

base (String!)

The name of the base branch that the provided head will be merged into.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitMessage (String)

Message to use for the merge commit. If omitted, a default will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

head (String!)

The head to merge into the base branch. This can be a branch name or a commit GitObjectID.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the Repository containing the base branch that will be modified.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMergePullRequestInput

\n

Autogenerated input type of MergePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this merge.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitBody (String)

Commit body to use for the merge commit; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

commitHeadline (String)

Commit headline to use for the merge commit; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID)

OID that the pull request head ref must match to allow merge; if omitted, no check is performed.

\n\n\n\n\n\n\n\n\n\n\n\n

mergeMethod (PullRequestMergeMethod)

The merge method to use. If omitted, defaults to 'MERGE'.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be merged.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMilestoneOrder

\n

Ordering options for milestone connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (MilestoneOrderField!)

The field to order milestones by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMinimizeCommentInput

\n

Autogenerated input type of MinimizeComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

classifier (ReportedContentClassifiers!)

The classification of comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMoveProjectCardInput

\n

Autogenerated input type of MoveProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterCardId (ID)

Place the new card after the card with this id. Pass null to place it at the top.

\n\n\n\n\n\n\n\n\n\n\n\n

cardId (ID!)

The id of the card to move.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to move it into.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMoveProjectColumnInput

\n

Autogenerated input type of MoveProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterColumnId (ID)

Place the new column after the column with this id. Pass null to place it at the front.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to move.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nOrgEnterpriseOwnerOrder

\n

Ordering options for an organization's enterprise owner connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (OrgEnterpriseOwnerOrderField!)

The field to order enterprise owners by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nOrganizationOrder

\n

Ordering options for organization connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (OrganizationOrderField!)

The field to order organizations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPackageFileOrder

\n

Ways in which lists of package files can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The direction in which to order package files by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PackageFileOrderField)

The field in which to order package files by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPackageOrder

\n

Ways in which lists of packages can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The direction in which to order packages by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PackageOrderField)

The field in which to order packages by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPackageVersionOrder

\n

Ways in which lists of package versions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The direction in which to order package versions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PackageVersionOrderField)

The field in which to order package versions by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPinIssueInput

\n

Autogenerated input type of PinIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to be pinned.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectCardImport

\n

An issue or PR and its owning repository to be used in a project card.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

number (Int!)

The issue or pull request number.

\n\n\n\n\n\n\n\n\n\n\n\n

repository (String!)

Repository name with owner (owner/repository).

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectColumnImport

\n

A project column and a list of its issues and PRs.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

columnName (String!)

The name of the column.

\n\n\n\n\n\n\n\n\n\n\n\n

issues ([ProjectCardImport!])

A list of issues and pull requests in the column.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int!)

The position of the column, starting from 0.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectOrder

\n

Ways in which lists of projects can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order projects by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ProjectOrderField!)

The field in which to order projects by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPullRequestOrder

\n

Ways in which lists of issues can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order pull requests by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PullRequestOrderField!)

The field in which to order pull requests by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReactionOrder

\n

Ways in which lists of reactions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order reactions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ReactionOrderField!)

The field in which to order reactions by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRefOrder

\n

Ways in which lists of git refs can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order refs by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RefOrderField!)

The field in which to order refs by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRefUpdate

\n

A ref update.

\n
\n\n
\n \n
\n

Preview notice

\n

RefUpdate is available under the Update refs preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterOid (GitObjectID!)

The value this ref should be updated to.

\n\n\n\n\n\n\n\n\n\n\n\n

beforeOid (GitObjectID)

The value this ref needs to point to before the update.

\n\n\n\n\n\n\n\n\n\n\n\n

force (Boolean)

Force a non fast-forward update.

\n\n\n\n\n\n\n\n\n\n\n\n

name (GitRefname!)

The fully qualified name of the ref to be update. For example refs/heads/branch-name.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRegenerateEnterpriseIdentityProviderRecoveryCodesInput

\n

Autogenerated input type of RegenerateEnterpriseIdentityProviderRecoveryCodes.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set an identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRegenerateVerifiableDomainTokenInput

\n

Autogenerated input type of RegenerateVerifiableDomainToken.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to regenerate the verification token of.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRejectDeploymentsInput

\n

Autogenerated input type of RejectDeployments.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comment (String)

Optional comment for rejecting deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentIds ([ID!]!)

The ids of environments to reject deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

workflowRunId (ID!)

The node ID of the workflow run containing the pending deployments.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReleaseOrder

\n

Ways in which lists of releases can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order releases by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ReleaseOrderField!)

The field in which to order releases by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveAssigneesFromAssignableInput

\n

Autogenerated input type of RemoveAssigneesFromAssignable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignableId (ID!)

The id of the assignable object to remove assignees from.

\n\n\n\n\n\n\n\n\n\n\n\n

assigneeIds ([ID!]!)

The id of users to remove as assignees.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseAdminInput

\n

Autogenerated input type of RemoveEnterpriseAdmin.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The Enterprise ID from which to remove the administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to remove as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseIdentityProviderInput

\n

Autogenerated input type of RemoveEnterpriseIdentityProvider.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise from which to remove the identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseOrganizationInput

\n

Autogenerated input type of RemoveEnterpriseOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise from which the organization should be removed.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to remove from the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseSupportEntitlementInput

\n

Autogenerated input type of RemoveEnterpriseSupportEntitlement.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the admin belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of a member who will lose the support entitlement.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveLabelsFromLabelableInput

\n

Autogenerated input type of RemoveLabelsFromLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!]!)

The ids of labels to remove.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the Labelable to remove labels from.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveOutsideCollaboratorInput

\n

Autogenerated input type of RemoveOutsideCollaborator.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to remove the outside collaborator from.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

The ID of the outside collaborator to remove.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveReactionInput

\n

Autogenerated input type of RemoveReaction.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

content (ReactionContent!)

The name of the emoji reaction to remove.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveStarInput

\n

Autogenerated input type of RemoveStar.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

starrableId (ID!)

The Starrable ID to unstar.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveUpvoteInput

\n

Autogenerated input type of RemoveUpvote.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the discussion or comment to remove upvote.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReopenIssueInput

\n

Autogenerated input type of ReopenIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

ID of the issue to be opened.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReopenPullRequestInput

\n

Autogenerated input type of ReopenPullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be reopened.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryInvitationOrder

\n

Ordering options for repository invitation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryInvitationOrderField!)

The field to order repository invitations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryMigrationOrder

\n

Ordering options for repository migrations.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (RepositoryMigrationOrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryMigrationOrderField!)

The field to order repository migrations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryOrder

\n

Ordering options for repository connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRequestReviewsInput

\n

Autogenerated input type of RequestReviews.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

teamIds ([ID!])

The Node IDs of the team to request.

\n\n\n\n\n\n\n\n\n\n\n\n

union (Boolean)

Add users to the set rather than replace.

\n\n\n\n\n\n\n\n\n\n\n\n

userIds ([ID!])

The Node IDs of the user to request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRequiredStatusCheckInput

\n

Specifies the attributes for a new or updated required status check.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (ID)

The ID of the App that must set the status in order for it to be accepted.\nOmit this value to use whichever app has recently been setting this status, or\nuse "any" to allow any app to set the status.

\n\n\n\n\n\n\n\n\n\n\n\n

context (String!)

Status check context that must pass for commits to be accepted to the matching branch.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRerequestCheckSuiteInput

\n

Autogenerated input type of RerequestCheckSuite.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

checkSuiteId (ID!)

The Node ID of the check suite.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nResolveReviewThreadInput

\n

Autogenerated input type of ResolveReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

threadId (ID!)

The ID of the thread to resolve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRevokeEnterpriseOrganizationsMigratorRoleInput

\n

Autogenerated input type of RevokeEnterpriseOrganizationsMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which all organizations managed by it will be granted the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to revoke the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRevokeMigratorRoleInput

\n

Autogenerated input type of RevokeMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actor (String!)

The user login or Team slug to revoke the migrator role from.

\n\n\n\n\n\n\n\n\n\n\n\n

actorType (ActorType!)

Specifies the type of the actor, can be either USER or TEAM.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization that the user/team belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSavedReplyOrder

\n

Ordering options for saved reply connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SavedReplyOrderField!)

The field to order saved replies by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSecurityAdvisoryIdentifierFilter

\n

An advisory identifier to filter results on.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

type (SecurityAdvisoryIdentifierType!)

The identifier type.

\n\n\n\n\n\n\n\n\n\n\n\n

value (String!)

The identifier string. Supports exact or partial matching.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSecurityAdvisoryOrder

\n

Ordering options for security advisory connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SecurityAdvisoryOrderField!)

The field to order security advisories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSecurityVulnerabilityOrder

\n

Ordering options for security vulnerability connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SecurityVulnerabilityOrderField!)

The field to order security vulnerabilities by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetEnterpriseIdentityProviderInput

\n

Autogenerated input type of SetEnterpriseIdentityProvider.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

digestMethod (SamlDigestAlgorithm!)

The digest algorithm used to sign SAML requests for the identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set an identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

idpCertificate (String!)

The x509 certificate used by the identity provider to sign assertions and responses.

\n\n\n\n\n\n\n\n\n\n\n\n

issuer (String)

The Issuer Entity ID for the SAML identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

signatureMethod (SamlSignatureAlgorithm!)

The signature algorithm used to sign SAML requests for the identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

ssoUrl (URI!)

The URL endpoint for the identity provider's SAML SSO.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetOrganizationInteractionLimitInput

\n

Autogenerated input type of SetOrganizationInteractionLimit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expiry (RepositoryInteractionLimitExpiry)

When this limit should expire.

\n\n\n\n\n\n\n\n\n\n\n\n

limit (RepositoryInteractionLimit!)

The limit to set.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to set a limit for.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetRepositoryInteractionLimitInput

\n

Autogenerated input type of SetRepositoryInteractionLimit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expiry (RepositoryInteractionLimitExpiry)

When this limit should expire.

\n\n\n\n\n\n\n\n\n\n\n\n

limit (RepositoryInteractionLimit!)

The limit to set.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to set a limit for.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetUserInteractionLimitInput

\n

Autogenerated input type of SetUserInteractionLimit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expiry (RepositoryInteractionLimitExpiry)

When this limit should expire.

\n\n\n\n\n\n\n\n\n\n\n\n

limit (RepositoryInteractionLimit!)

The limit to set.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

The ID of the user to set a limit for.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorOrder

\n

Ordering options for connections to get sponsor entities for GitHub Sponsors.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorOrderField!)

The field to order sponsor entities by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorableOrder

\n

Ordering options for connections to get sponsorable entities for GitHub Sponsors.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorableOrderField!)

The field to order sponsorable entities by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorsActivityOrder

\n

Ordering options for GitHub Sponsors activity connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorsActivityOrderField!)

The field to order activity by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorsTierOrder

\n

Ordering options for Sponsors tiers connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorsTierOrderField!)

The field to order tiers by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorshipNewsletterOrder

\n

Ordering options for sponsorship newsletter connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorshipNewsletterOrderField!)

The field to order sponsorship newsletters by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorshipOrder

\n

Ordering options for sponsorship connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorshipOrderField!)

The field to order sponsorship by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nStarOrder

\n

Ways in which star connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (StarOrderField!)

The field in which to order nodes by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nStartRepositoryMigrationInput

\n

Autogenerated input type of StartRepositoryMigration.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

accessToken (String)

The Octoshift migration source access token.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

continueOnError (Boolean)

Whether to continue the migration on error.

\n\n\n\n\n\n\n\n\n\n\n\n

gitArchiveUrl (String)

The signed URL to access the user-uploaded git archive.

\n\n\n\n\n\n\n\n\n\n\n\n

githubPat (String)

The GitHub personal access token of the user importing to the target repository.

\n\n\n\n\n\n\n\n\n\n\n\n

metadataArchiveUrl (String)

The signed URL to access the user-uploaded metadata archive.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that will own the imported repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryName (String!)

The name of the imported repository.

\n\n\n\n\n\n\n\n\n\n\n\n

skipReleases (Boolean)

Whether to skip migrating releases for the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

sourceId (ID!)

The ID of the Octoshift migration source.

\n\n\n\n\n\n\n\n\n\n\n\n

sourceRepositoryUrl (URI!)

The Octoshift migration source repository URL.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSubmitPullRequestReviewInput

\n

Autogenerated input type of SubmitPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The text field to set on the Pull Request Review.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

event (PullRequestReviewEvent!)

The event to send to the Pull Request Review.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The Pull Request ID to submit any pending reviews.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Pull Request Review ID to submit.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamDiscussionCommentOrder

\n

Ways in which team discussion comment connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamDiscussionCommentOrderField!)

The field by which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamDiscussionOrder

\n

Ways in which team discussion connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamDiscussionOrderField!)

The field by which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamMemberOrder

\n

Ordering options for team member connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamMemberOrderField!)

The field to order team members by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamOrder

\n

Ways in which team connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamOrderField!)

The field in which to order nodes by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamRepositoryOrder

\n

Ordering options for team repository connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamRepositoryOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTransferIssueInput

\n

Autogenerated input type of TransferIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The Node ID of the issue to be transferred.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository the issue should be transferred to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnarchiveRepositoryInput

\n

Autogenerated input type of UnarchiveRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to unarchive.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnfollowOrganizationInput

\n

Autogenerated input type of UnfollowOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

ID of the organization to unfollow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnfollowUserInput

\n

Autogenerated input type of UnfollowUser.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

ID of the user to unfollow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnlinkRepositoryFromProjectInput

\n

Autogenerated input type of UnlinkRepositoryFromProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project linked to the Repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the Repository linked to the Project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnlockLockableInput

\n

Autogenerated input type of UnlockLockable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

lockableId (ID!)

ID of the item to be unlocked.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkDiscussionCommentAsAnswerInput

\n

Autogenerated input type of UnmarkDiscussionCommentAsAnswer.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion comment to unmark as an answer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkFileAsViewedInput

\n

Autogenerated input type of UnmarkFileAsViewed.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to mark as unviewed.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkIssueAsDuplicateInput

\n

Autogenerated input type of UnmarkIssueAsDuplicate.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

canonicalId (ID!)

ID of the issue or pull request currently considered canonical/authoritative/original.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

duplicateId (ID!)

ID of the issue or pull request currently marked as a duplicate.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnminimizeCommentInput

\n

Autogenerated input type of UnminimizeComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnpinIssueInput

\n

Autogenerated input type of UnpinIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to be unpinned.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnresolveReviewThreadInput

\n

Autogenerated input type of UnresolveReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

threadId (ID!)

The ID of the thread to unresolve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateBranchProtectionRuleInput

\n

Autogenerated input type of UpdateBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowsDeletions (Boolean)

Can this branch be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

allowsForcePushes (Boolean)

Are force pushes allowed on this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

blocksCreations (Boolean)

Is branch creation a protected operation.

\n\n\n\n\n\n\n\n\n\n\n\n

branchProtectionRuleId (ID!)

The global relay id of the branch protection rule to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassForcePushActorIds ([ID!])

A list of User or Team IDs allowed to bypass force push targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassPullRequestActorIds ([ID!])

A list of User or Team IDs allowed to bypass pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissesStaleReviews (Boolean)

Will new commits pushed to matching branches dismiss pull request review approvals.

\n\n\n\n\n\n\n\n\n\n\n\n

isAdminEnforced (Boolean)

Can admins overwrite branch protection.

\n\n\n\n\n\n\n\n\n\n\n\n

pattern (String)

The glob-like pattern used to determine matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

pushActorIds ([ID!])

A list of User, Team, or App IDs allowed to push to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredApprovingReviewCount (Int)

Number of approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusCheckContexts ([String!])

List of required status check contexts that must pass for commits to be accepted to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusChecks ([RequiredStatusCheckInput!])

The list of required status checks.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresApprovingReviews (Boolean)

Are approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCodeOwnerReviews (Boolean)

Are reviews from code owners required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCommitSignatures (Boolean)

Are commits required to be signed.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresConversationResolution (Boolean)

Are conversations required to be resolved before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresLinearHistory (Boolean)

Are merge commits prohibited from being pushed to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStatusChecks (Boolean)

Are status checks required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStrictStatusChecks (Boolean)

Are branches required to be up to date before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsPushes (Boolean)

Is pushing to matching branches restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsReviewDismissals (Boolean)

Is dismissal of pull request reviews restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewDismissalActorIds ([ID!])

A list of User or Team IDs allowed to dismiss reviews on pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateCheckRunInput

\n

Autogenerated input type of UpdateCheckRun.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actions ([CheckRunAction!])

Possible further actions the integrator can perform, which a user may trigger.

\n\n\n\n\n\n\n\n\n\n\n\n

checkRunId (ID!)

The node of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

completedAt (DateTime)

The time that the check run finished.

\n\n\n\n\n\n\n\n\n\n\n\n

conclusion (CheckConclusionState)

The final conclusion of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

detailsUrl (URI)

The URL of the integrator's site that has the full details of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

externalId (String)

A reference for the run on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

output (CheckRunOutput)

Descriptive details about the run.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

startedAt (DateTime)

The time that the check run began.

\n\n\n\n\n\n\n\n\n\n\n\n

status (RequestableCheckStatusState)

The current status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateCheckSuitePreferencesInput

\n

Autogenerated input type of UpdateCheckSuitePreferences.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoTriggerPreferences ([CheckSuiteAutoTriggerPreference!]!)

The check suite preferences to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateDiscussionCommentInput

\n

Autogenerated input type of UpdateDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The new contents of the comment body.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commentId (ID!)

The Node ID of the discussion comment to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateDiscussionInput

\n

Autogenerated input type of UpdateDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The new contents of the discussion body.

\n\n\n\n\n\n\n\n\n\n\n\n

categoryId (ID)

The Node ID of a discussion category within the same repository to change this discussion to.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The Node ID of the discussion to update.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The new discussion title.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseAdministratorRoleInput

\n

Autogenerated input type of UpdateEnterpriseAdministratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the admin belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of a administrator whose role is being changed.

\n\n\n\n\n\n\n\n\n\n\n\n

role (EnterpriseAdministratorRole!)

The new role for the Enterprise administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseAllowPrivateRepositoryForkingSettingInput

\n

Autogenerated input type of UpdateEnterpriseAllowPrivateRepositoryForkingSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the allow private repository forking setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the allow private repository forking setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseDefaultRepositoryPermissionSettingInput

\n

Autogenerated input type of UpdateEnterpriseDefaultRepositoryPermissionSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the base repository permission setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseDefaultRepositoryPermissionSettingValue!)

The value for the base repository permission setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanChangeRepositoryVisibilitySettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanChangeRepositoryVisibilitySetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can change repository visibility setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can change repository visibility setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanCreateRepositoriesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanCreateRepositoriesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can create repositories setting.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreateInternalRepositories (Boolean)

Allow members to create internal repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreatePrivateRepositories (Boolean)

Allow members to create private repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreatePublicRepositories (Boolean)

Allow members to create public repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreateRepositoriesPolicyEnabled (Boolean)

When false, allow member organizations to set their own repository creation member privileges.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseMembersCanCreateRepositoriesSettingValue)

Value for the members can create repositories setting on the enterprise. This\nor the granular public/private/internal allowed fields (but not both) must be provided.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanDeleteIssuesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanDeleteIssuesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can delete issues setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can delete issues setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanDeleteRepositoriesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanDeleteRepositoriesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can delete repositories setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can delete repositories setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanInviteCollaboratorsSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanInviteCollaboratorsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can invite collaborators setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can invite collaborators setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanMakePurchasesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanMakePurchasesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can make purchases setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseMembersCanMakePurchasesSettingValue!)

The value for the members can make purchases setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanUpdateProtectedBranchesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanUpdateProtectedBranchesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can update protected branches setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can update protected branches setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanViewDependencyInsightsSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanViewDependencyInsightsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can view dependency insights setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can view dependency insights setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseOrganizationProjectsSettingInput

\n

Autogenerated input type of UpdateEnterpriseOrganizationProjectsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the organization projects setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the organization projects setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseOwnerOrganizationRoleInput

\n

Autogenerated input type of UpdateEnterpriseOwnerOrganizationRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the owner belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization for membership change.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationRole (RoleInOrganization!)

The role to assume in the organization.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseProfileInput

\n

Autogenerated input type of UpdateEnterpriseProfile.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

The description of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The Enterprise ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n

location (String)

The location of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

websiteUrl (String)

The URL of the enterprise's website.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseRepositoryProjectsSettingInput

\n

Autogenerated input type of UpdateEnterpriseRepositoryProjectsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the repository projects setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the repository projects setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseTeamDiscussionsSettingInput

\n

Autogenerated input type of UpdateEnterpriseTeamDiscussionsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the team discussions setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the team discussions setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseTwoFactorAuthenticationRequiredSettingInput

\n

Autogenerated input type of UpdateEnterpriseTwoFactorAuthenticationRequiredSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the two factor authentication required setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledSettingValue!)

The value for the two factor authentication required setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnvironmentInput

\n

Autogenerated input type of UpdateEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentId (ID!)

The node ID of the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewers ([ID!])

The ids of users or teams that can approve deployments to this environment.

\n\n\n\n\n\n\n\n\n\n\n\n

waitTimer (Int)

The wait timer in minutes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListEnabledSettingInput

\n

Autogenerated input type of UpdateIpAllowListEnabledSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner on which to set the IP allow list enabled setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (IpAllowListEnabledSettingValue!)

The value for the IP allow list enabled setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListEntryInput

\n

Autogenerated input type of UpdateIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowListValue (String!)

An IP address or range of addresses in CIDR notation.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ipAllowListEntryId (ID!)

The ID of the IP allow list entry to update.

\n\n\n\n\n\n\n\n\n\n\n\n

isActive (Boolean!)

Whether the IP allow list entry is active when an IP allow list is enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

An optional name for the IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListForInstalledAppsEnabledSettingInput

\n

Autogenerated input type of UpdateIpAllowListForInstalledAppsEnabledSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (IpAllowListForInstalledAppsEnabledSettingValue!)

The value for the IP allow list configuration for installed GitHub Apps setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIssueCommentInput

\n

Autogenerated input type of UpdateIssueComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The updated text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the IssueComment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIssueInput

\n

Autogenerated input type of UpdateIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

An array of Node IDs of users for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body for the issue description.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the Issue to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

state (IssueState)

The desired issue state.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title for the issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateLabelInput

\n

Autogenerated input type of UpdateLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

color (String)

A 6 character hex code, without the leading #, identifying the updated color of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A brief description of the label, such as its purpose.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the label to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The updated name of the label.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateNotificationRestrictionSettingInput

\n

Autogenerated input type of UpdateNotificationRestrictionSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner on which to set the restrict notifications setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (NotificationRestrictionSettingValue!)

The value for the restrict notifications setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateOrganizationAllowPrivateRepositoryForkingSettingInput

\n

Autogenerated input type of UpdateOrganizationAllowPrivateRepositoryForkingSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

forkingEnabled (Boolean!)

Enable forking of private repositories in the organization?.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization on which to set the allow private repository forking setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectCardInput

\n

Autogenerated input type of UpdateProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isArchived (Boolean)

Whether or not the ProjectCard should be archived.

\n\n\n\n\n\n\n\n\n\n\n\n

note (String)

The note of ProjectCard.

\n\n\n\n\n\n\n\n\n\n\n\n

projectCardId (ID!)

The ProjectCard ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectColumnInput

\n

Autogenerated input type of UpdateProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of project column.

\n\n\n\n\n\n\n\n\n\n\n\n

projectColumnId (ID!)

The ProjectColumn ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectDraftIssueInput

\n

Autogenerated input type of UpdateProjectDraftIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The IDs of the assignees of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

draftIssueId (ID!)

The ID of the draft issue to update.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectInput

\n

Autogenerated input type of UpdateProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of project.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Project ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Whether the project is public or not.

\n\n\n\n\n\n\n\n\n\n\n\n

state (ProjectState)

Whether the project is open or closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectNextInput

\n

Autogenerated input type of UpdateProjectNext.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

closed (Boolean)

Set the project to closed or open.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

Set the readme description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to update.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Set the project to public or private.

\n\n\n\n\n\n\n\n\n\n\n\n

shortDescription (String)

Set the short description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

Set the title of the project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectNextItemFieldInput

\n

Autogenerated input type of UpdateProjectNextItemField.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

fieldId (ID)

The id of the field to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

itemId (ID!)

The id of the item to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project.

\n\n\n\n\n\n\n\n\n\n\n\n

value (String!)

The value which will be set on the field.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestBranchInput

\n

Autogenerated input type of UpdatePullRequestBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID)

The head ref oid for the upstream branch.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestInput

\n

Autogenerated input type of UpdatePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

An array of Node IDs of users for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

baseRefName (String)

The name of the branch you want your changes pulled into. This should be an existing branch\non the current repository.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The contents of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

maintainerCanModify (Boolean)

Indicates whether maintainers can modify the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

state (PullRequestUpdateState)

The target state of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestReviewCommentInput

\n

Autogenerated input type of UpdatePullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewCommentId (ID!)

The Node ID of the comment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestReviewInput

\n

Autogenerated input type of UpdatePullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the pull request review body.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRefInput

\n

Autogenerated input type of UpdateRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

force (Boolean)

Permit updates of branch Refs that are not fast-forwards?.

\n\n\n\n\n\n\n\n\n\n\n\n

oid (GitObjectID!)

The GitObjectID that the Ref shall be updated to target.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The Node ID of the Ref to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRefsInput

\n

Autogenerated input type of UpdateRefs.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateRefsInput is available under the Update refs preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

refUpdates ([RefUpdate!]!)

A list of ref updates.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRepositoryInput

\n

Autogenerated input type of UpdateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A new description for the repository. Pass an empty string to erase the existing description.

\n\n\n\n\n\n\n\n\n\n\n\n

hasIssuesEnabled (Boolean)

Indicates if the repository should have the issues feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasProjectsEnabled (Boolean)

Indicates if the repository should have the project boards feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasWikiEnabled (Boolean)

Indicates if the repository should have the wiki feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

homepageUrl (URI)

The URL for a web page about this repository. Pass an empty string to erase the existing URL.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The new name of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to update.

\n\n\n\n\n\n\n\n\n\n\n\n

template (Boolean)

Whether this repository should be marked as a template such that anyone who\ncan access it can create new repositories with the same files and directory structure.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateSponsorshipPreferencesInput

\n

Autogenerated input type of UpdateSponsorshipPreferences.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

privacyLevel (SponsorshipPrivacy)

Specify whether others should be able to see that the sponsor is sponsoring\nthe sponsorable. Public visibility still does not reveal which tier is used.

\n\n\n\n\n\n\n\n\n\n\n\n

receiveEmails (Boolean)

Whether the sponsor should receive email updates from the sponsorable.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorId (ID)

The ID of the user or organization who is acting as the sponsor, paying for\nthe sponsorship. Required if sponsorLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorLogin (String)

The username of the user or organization who is acting as the sponsor, paying\nfor the sponsorship. Required if sponsorId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who is receiving the sponsorship. Required if sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who is receiving the sponsorship. Required if sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateSubscriptionInput

\n

Autogenerated input type of UpdateSubscription.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

state (SubscriptionState!)

The new state of the subscription.

\n\n\n\n\n\n\n\n\n\n\n\n

subscribableId (ID!)

The Node ID of the subscribable object to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamDiscussionCommentInput

\n

Autogenerated input type of UpdateTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The updated text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

bodyVersion (String)

The current version of the body content.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamDiscussionInput

\n

Autogenerated input type of UpdateTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The updated text of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

bodyVersion (String)

The current version of the body content. If provided, this update operation\nwill be rejected if the given version does not match the latest version on the server.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

pinned (Boolean)

If provided, sets the pinned state of the updated discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The updated title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamReviewAssignmentInput

\n

Autogenerated input type of UpdateTeamReviewAssignment.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateTeamReviewAssignmentInput is available under the Team review assignments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

algorithm (TeamReviewAssignmentAlgorithm)

The algorithm to use for review assignment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enabled (Boolean!)

Turn on or off review assignment.

\n\n\n\n\n\n\n\n\n\n\n\n

excludedTeamMemberIds ([ID!])

An array of team member IDs to exclude.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the team to update review assignments of.

\n\n\n\n\n\n\n\n\n\n\n\n

notifyTeam (Boolean)

Notify the entire team of the PR if it is delegated.

\n\n\n\n\n\n\n\n\n\n\n\n

teamMemberCount (Int)

The number of team members to assign.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamsRepositoryInput

\n

Autogenerated input type of UpdateTeamsRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

permission (RepositoryPermission!)

Permission that should be granted to the teams.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

Repository ID being granted access to.

\n\n\n\n\n\n\n\n\n\n\n\n

teamIds ([ID!]!)

A list of teams being granted access. Limit: 10.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTopicsInput

\n

Autogenerated input type of UpdateTopics.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

topicNames ([String!]!)

An array of topic names.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUserStatusOrder

\n

Ordering options for user status connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (UserStatusOrderField!)

The field to order user statuses by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nVerifiableDomainOrder

\n

Ordering options for verifiable domain connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (VerifiableDomainOrderField!)

The field to order verifiable domains by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nVerifyVerifiableDomainInput

\n

Autogenerated input type of VerifyVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to verify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n", "miniToc": [ { "contents": "\n AbortQueuedMigrationsInput", @@ -1790,7 +1790,7 @@ ] }, "ghec": { - "html": "
\n
\n

\n \n \nAbortQueuedMigrationsInput

\n

Autogenerated input type of AbortQueuedMigrations.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that is running the migrations.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAcceptEnterpriseAdministratorInvitationInput

\n

Autogenerated input type of AcceptEnterpriseAdministratorInvitation.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

invitationId (ID!)

The id of the invitation being accepted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAcceptTopicSuggestionInput

\n

Autogenerated input type of AcceptTopicSuggestion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the suggested topic.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddAssigneesToAssignableInput

\n

Autogenerated input type of AddAssigneesToAssignable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignableId (ID!)

The id of the assignable object to add assignees to.

\n\n\n\n\n\n\n\n\n\n\n\n

assigneeIds ([ID!]!)

The id of users to add as assignees.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddCommentInput

\n

Autogenerated input type of AddComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddDiscussionCommentInput

\n

Autogenerated input type of AddDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The Node ID of the discussion to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

replyToId (ID)

The Node ID of the discussion comment within this discussion to reply to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddEnterpriseSupportEntitlementInput

\n

Autogenerated input type of AddEnterpriseSupportEntitlement.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the admin belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of a member who will receive the support entitlement.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddLabelsToLabelableInput

\n

Autogenerated input type of AddLabelsToLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!]!)

The ids of the labels to add.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the labelable object to add labels to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectCardInput

\n

Autogenerated input type of AddProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

contentId (ID)

The content of the card. Must be a member of the ProjectCardItem union.

\n\n\n\n\n\n\n\n\n\n\n\n

note (String)

The note on the card.

\n\n\n\n\n\n\n\n\n\n\n\n

projectColumnId (ID!)

The Node ID of the ProjectColumn.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectColumnInput

\n

Autogenerated input type of AddProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the column.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Node ID of the project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectDraftIssueInput

\n

Autogenerated input type of AddProjectDraftIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The IDs of the assignees of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to add the draft issue to.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectNextItemInput

\n

Autogenerated input type of AddProjectNextItem.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

contentId (ID!)

The content id of the item (Issue or PullRequest).

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to add the item to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewCommentInput

\n

Autogenerated input type of AddPullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitOID (GitObjectID)

The SHA of the commit to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

inReplyTo (ID)

The comment id to reply to.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String)

The relative path of the file to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int)

The line index in the diff to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The node ID of the pull request reviewing.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Node ID of the review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewInput

\n

Autogenerated input type of AddPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The contents of the review body comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comments ([DraftPullRequestReviewComment])

The review line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

commitOID (GitObjectID)

The commit OID the review pertains to.

\n\n\n\n\n\n\n\n\n\n\n\n

event (PullRequestReviewEvent)

The event to perform on the pull request review.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

threads ([DraftPullRequestReviewThread])

The review line comment threads.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewThreadInput

\n

Autogenerated input type of AddPullRequestReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the thread's first comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

line (Int!)

The line of the blob to which the thread refers. The end of the line range for multi-line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The node ID of the pull request reviewing.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Node ID of the review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

side (DiffSide)

The side of the diff on which the line resides. For multi-line comments, this is the side for the end of the line range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int)

The first line of the range to which the comment refers.

\n\n\n\n\n\n\n\n\n\n\n\n

startSide (DiffSide)

The side of the diff on which the start line resides.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddReactionInput

\n

Autogenerated input type of AddReaction.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

content (ReactionContent!)

The name of the emoji to react with.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddStarInput

\n

Autogenerated input type of AddStar.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

starrableId (ID!)

The Starrable ID to star.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddUpvoteInput

\n

Autogenerated input type of AddUpvote.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the discussion or comment to upvote.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddVerifiableDomainInput

\n

Autogenerated input type of AddVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

domain (URI!)

The URL of the domain.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner to add the domain to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nApproveDeploymentsInput

\n

Autogenerated input type of ApproveDeployments.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comment (String)

Optional comment for approving deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentIds ([ID!]!)

The ids of environments to reject deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

workflowRunId (ID!)

The node ID of the workflow run containing the pending deployments.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nApproveVerifiableDomainInput

\n

Autogenerated input type of ApproveVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to approve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nArchiveRepositoryInput

\n

Autogenerated input type of ArchiveRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to mark as archived.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAuditLogOrder

\n

Ordering options for Audit Log connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (AuditLogOrderField)

The field to order Audit Logs by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCancelEnterpriseAdminInvitationInput

\n

Autogenerated input type of CancelEnterpriseAdminInvitation.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

invitationId (ID!)

The Node ID of the pending enterprise administrator invitation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCancelSponsorshipInput

\n

Autogenerated input type of CancelSponsorship.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorId (ID)

The ID of the user or organization who is acting as the sponsor, paying for\nthe sponsorship. Required if sponsorLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorLogin (String)

The username of the user or organization who is acting as the sponsor, paying\nfor the sponsorship. Required if sponsorId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who is receiving the sponsorship. Required if sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who is receiving the sponsorship. Required if sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nChangeUserStatusInput

\n

Autogenerated input type of ChangeUserStatus.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

emoji (String)

The emoji to represent your status. Can either be a native Unicode emoji or an emoji name with colons, e.g., 😀.

\n\n\n\n\n\n\n\n\n\n\n\n

expiresAt (DateTime)

If set, the user status will not be shown after this date.

\n\n\n\n\n\n\n\n\n\n\n\n

limitedAvailability (Boolean)

Whether this status should indicate you are not fully available on GitHub, e.g., you are away.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String)

A short description of your current status.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID)

The ID of the organization whose members will be allowed to see the status. If\nomitted, the status will be publicly visible.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckAnnotationData

\n

Information from a check run analysis to specific lines of code.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

annotationLevel (CheckAnnotationLevel!)

Represents an annotation's information level.

\n\n\n\n\n\n\n\n\n\n\n\n

location (CheckAnnotationRange!)

The location of the annotation.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String!)

A short description of the feedback for these lines of code.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to add an annotation to.

\n\n\n\n\n\n\n\n\n\n\n\n

rawDetails (String)

Details about this annotation.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title that represents the annotation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckAnnotationRange

\n

Information from a check run analysis to specific lines of code.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

endColumn (Int)

The ending column of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

endLine (Int!)

The ending line of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

startColumn (Int)

The starting column of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int!)

The starting line of the range.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunAction

\n

Possible further actions the integrator can perform.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

description (String!)

A short explanation of what this action would do.

\n\n\n\n\n\n\n\n\n\n\n\n

identifier (String!)

A reference for the action on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

label (String!)

The text to be displayed on a button in the web UI.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunFilter

\n

The filters that are available when fetching check runs.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (Int)

Filters the check runs created by this application ID.

\n\n\n\n\n\n\n\n\n\n\n\n

checkName (String)

Filters the check runs by this name.

\n\n\n\n\n\n\n\n\n\n\n\n

checkType (CheckRunType)

Filters the check runs by this type.

\n\n\n\n\n\n\n\n\n\n\n\n

status (CheckStatusState)

Filters the check runs by this status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunOutput

\n

Descriptive details about the check run.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

annotations ([CheckAnnotationData!])

The annotations that are made as part of the check run.

\n\n\n\n\n\n\n\n\n\n\n\n

images ([CheckRunOutputImage!])

Images attached to the check run output displayed in the GitHub pull request UI.

\n\n\n\n\n\n\n\n\n\n\n\n

summary (String!)

The summary of the check run (supports Commonmark).

\n\n\n\n\n\n\n\n\n\n\n\n

text (String)

The details of the check run (supports Commonmark).

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

A title to provide for this check run.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunOutputImage

\n

Images attached to the check run output displayed in the GitHub pull request UI.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

alt (String!)

The alternative text for the image.

\n\n\n\n\n\n\n\n\n\n\n\n

caption (String)

A short image description.

\n\n\n\n\n\n\n\n\n\n\n\n

imageUrl (URI!)

The full URL of the image.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckSuiteAutoTriggerPreference

\n

The auto-trigger preferences that are available for check suites.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (ID!)

The node ID of the application that owns the check suite.

\n\n\n\n\n\n\n\n\n\n\n\n

setting (Boolean!)

Set to true to enable automatic creation of CheckSuite events upon pushes to the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckSuiteFilter

\n

The filters that are available when fetching check suites.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (Int)

Filters the check suites created by this application ID.

\n\n\n\n\n\n\n\n\n\n\n\n

checkName (String)

Filters the check suites by this name.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nClearLabelsFromLabelableInput

\n

Autogenerated input type of ClearLabelsFromLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the labelable object to clear the labels from.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloneProjectInput

\n

Autogenerated input type of CloneProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

includeWorkflows (Boolean!)

Whether or not to clone the source project's workflows.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

The visibility of the project, defaults to false (private).

\n\n\n\n\n\n\n\n\n\n\n\n

sourceId (ID!)

The source project to clone.

\n\n\n\n\n\n\n\n\n\n\n\n

targetOwnerId (ID!)

The owner ID to create the project under.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloneTemplateRepositoryInput

\n

Autogenerated input type of CloneTemplateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

includeAllBranches (Boolean)

Whether to copy all branches from the template to the new repository. Defaults\nto copying only the default branch of the template.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner for the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the template repository.

\n\n\n\n\n\n\n\n\n\n\n\n

visibility (RepositoryVisibility!)

Indicates the repository's visibility level.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloseIssueInput

\n

Autogenerated input type of CloseIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

ID of the issue to be closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nClosePullRequestInput

\n

Autogenerated input type of ClosePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitAuthor

\n

Specifies an author for filtering Git commits.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

emails ([String!])

Email addresses to filter by. Commits authored by any of the specified email addresses will be returned.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID)

ID of a User to filter by. If non-null, only commits authored by this user\nwill be returned. This field takes precedence over emails.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitContributionOrder

\n

Ordering options for commit contribution connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (CommitContributionOrderField!)

The field by which to order commit contributions.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitMessage

\n

A message to include with a new commit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The body of the message.

\n\n\n\n\n\n\n\n\n\n\n\n

headline (String!)

The headline of the message.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommittableBranch

\n

A git ref for a commit to be appended to.

\n

The ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).

\n

The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.

\n

Examples

\n

Specify a branch using a global node ID:

\n
{ "id": "MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=" }\n
\n

Specify a branch using nameWithOwner and branch name:

\n
{\n  "nameWithOwner": "github/graphql-client",\n  "branchName": "main"\n}.\n
\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branchName (String)

The unqualified name of the branch to append the commit to.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID)

The Node ID of the Ref to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryNameWithOwner (String)

The nameWithOwner of the repository to commit to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nContributionOrder

\n

Ordering options for contribution connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nConvertProjectCardNoteToIssueInput

\n

Autogenerated input type of ConvertProjectCardNoteToIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The body of the newly created issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectCardId (ID!)

The ProjectCard ID to convert.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to create the issue in.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the newly created issue. Defaults to the card's note text.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nConvertPullRequestToDraftInput

\n

Autogenerated input type of ConvertPullRequestToDraft.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to convert to draft.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateBranchProtectionRuleInput

\n

Autogenerated input type of CreateBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowsDeletions (Boolean)

Can this branch be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

allowsForcePushes (Boolean)

Are force pushes allowed on this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

blocksCreations (Boolean)

Is branch creation a protected operation.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassForcePushActorIds ([ID!])

A list of User or Team IDs allowed to bypass force push targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassPullRequestActorIds ([ID!])

A list of User or Team IDs allowed to bypass pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissesStaleReviews (Boolean)

Will new commits pushed to matching branches dismiss pull request review approvals.

\n\n\n\n\n\n\n\n\n\n\n\n

isAdminEnforced (Boolean)

Can admins overwrite branch protection.

\n\n\n\n\n\n\n\n\n\n\n\n

pattern (String!)

The glob-like pattern used to determine matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

pushActorIds ([ID!])

A list of User, Team or App IDs allowed to push to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The global relay id of the repository in which a new branch protection rule should be created in.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredApprovingReviewCount (Int)

Number of approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusCheckContexts ([String!])

List of required status check contexts that must pass for commits to be accepted to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusChecks ([RequiredStatusCheckInput!])

The list of required status checks.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresApprovingReviews (Boolean)

Are approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCodeOwnerReviews (Boolean)

Are reviews from code owners required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCommitSignatures (Boolean)

Are commits required to be signed.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresConversationResolution (Boolean)

Are conversations required to be resolved before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresLinearHistory (Boolean)

Are merge commits prohibited from being pushed to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStatusChecks (Boolean)

Are status checks required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStrictStatusChecks (Boolean)

Are branches required to be up to date before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsPushes (Boolean)

Is pushing to matching branches restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsReviewDismissals (Boolean)

Is dismissal of pull request reviews restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewDismissalActorIds ([ID!])

A list of User or Team IDs allowed to dismiss reviews on pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCheckRunInput

\n

Autogenerated input type of CreateCheckRun.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actions ([CheckRunAction!])

Possible further actions the integrator can perform, which a user may trigger.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

completedAt (DateTime)

The time that the check run finished.

\n\n\n\n\n\n\n\n\n\n\n\n

conclusion (CheckConclusionState)

The final conclusion of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

detailsUrl (URI)

The URL of the integrator's site that has the full details of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

externalId (String)

A reference for the run on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

headSha (GitObjectID!)

The SHA of the head commit.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

output (CheckRunOutput)

Descriptive details about the run.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

startedAt (DateTime)

The time that the check run began.

\n\n\n\n\n\n\n\n\n\n\n\n

status (RequestableCheckStatusState)

The current status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCheckSuiteInput

\n

Autogenerated input type of CreateCheckSuite.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

headSha (GitObjectID!)

The SHA of the head commit.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCommitOnBranchInput

\n

Autogenerated input type of CreateCommitOnBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branch (CommittableBranch!)

The Ref to be updated. Must be a branch.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID!)

The git commit oid expected at the head of the branch prior to the commit.

\n\n\n\n\n\n\n\n\n\n\n\n

fileChanges (FileChanges)

A description of changes to files in this commit.

\n\n\n\n\n\n\n\n\n\n\n\n

message (CommitMessage!)

The commit message the be included with the commit.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDeploymentInput

\n

Autogenerated input type of CreateDeployment.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateDeploymentInput is available under the Deployments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoMerge (Boolean)

Attempt to automatically merge the default branch into the requested ref, defaults to true.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

Short description of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

environment (String)

Name for the target deployment environment.

\n\n\n\n\n\n\n\n\n\n\n\n

payload (String)

JSON payload with extra information about the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The node ID of the ref to be deployed.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredContexts ([String!])

The status contexts to verify against commit status checks. To bypass required\ncontexts, pass an empty array. Defaults to all unique contexts.

\n\n\n\n\n\n\n\n\n\n\n\n

task (String)

Specifies a task to execute.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDeploymentStatusInput

\n

Autogenerated input type of CreateDeploymentStatus.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateDeploymentStatusInput is available under the Deployments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoInactive (Boolean)

Adds a new inactive status to all non-transient, non-production environment\ndeployments with the same repository and environment name as the created\nstatus's deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

deploymentId (ID!)

The node ID of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the status. Maximum length of 140 characters.

\n\n\n\n\n\n\n\n\n\n\n\n

environment (String)

If provided, updates the environment of the deploy. Otherwise, does not modify the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentUrl (String)

Sets the URL for accessing your environment.

\n\n\n\n\n\n\n\n\n\n\n\n

logUrl (String)

The log URL to associate with this status. This URL should contain\noutput to keep the user updated while the task is running or serve as\nhistorical information for what happened in the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

state (DeploymentStatusState!)

The state of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDiscussionInput

\n

Autogenerated input type of CreateDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The body of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

categoryId (ID!)

The id of the discussion category to associate with this discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The id of the repository on which to create the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateEnterpriseOrganizationInput

\n

Autogenerated input type of CreateEnterpriseOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

adminLogins ([String!]!)

The logins for the administrators of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

billingEmail (String!)

The email used for sending billing receipts.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise owning the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

profileName (String!)

The profile name of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateEnvironmentInput

\n

Autogenerated input type of CreateEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateIpAllowListEntryInput

\n

Autogenerated input type of CreateIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowListValue (String!)

An IP address or range of addresses in CIDR notation.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isActive (Boolean!)

Whether the IP allow list entry is active when an IP allow list is enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

An optional name for the IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner for which to create the new IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateIssueInput

\n

Autogenerated input type of CreateIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The Node ID for the user assignee for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body for the issue description.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueTemplate (String)

The name of an issue template in the repository, assigns labels and assignees from the template to the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title for the issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateLabelInput

\n

Autogenerated input type of CreateLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

color (String!)

A 6 character hex code, without the leading #, identifying the color of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A brief description of the label, such as its purpose.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateMigrationSourceInput

\n

Autogenerated input type of CreateMigrationSource.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

accessToken (String)

The Octoshift migration source access token.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

githubPat (String)

The GitHub personal access token of the user importing to the target repository.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The Octoshift migration source name.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that will own the Octoshift migration source.

\n\n\n\n\n\n\n\n\n\n\n\n

type (MigrationSourceType!)

The Octoshift migration source type.

\n\n\n\n\n\n\n\n\n\n\n\n

url (String!)

The Octoshift migration source URL.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateProjectInput

\n

Autogenerated input type of CreateProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of project.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The owner ID to create the project under.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryIds ([ID!])

A list of repository IDs to create as linked repositories for the project.

\n\n\n\n\n\n\n\n\n\n\n\n

template (ProjectTemplate)

The name of the GitHub-provided template.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreatePullRequestInput

\n

Autogenerated input type of CreatePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

baseRefName (String!)

The name of the branch you want your changes pulled into. This should be an existing branch\non the current repository. You cannot update the base branch on a pull request to point\nto another repository.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The contents of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

draft (Boolean)

Indicates whether this pull request should be a draft.

\n\n\n\n\n\n\n\n\n\n\n\n

headRefName (String!)

The name of the branch where your changes are implemented. For cross-repository pull requests\nin the same network, namespace head_ref_name with a user like this: username:branch.

\n\n\n\n\n\n\n\n\n\n\n\n

maintainerCanModify (Boolean)

Indicates whether maintainers can modify the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateRefInput

\n

Autogenerated input type of CreateRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The fully qualified name of the new Ref (ie: refs/heads/my_new_branch).

\n\n\n\n\n\n\n\n\n\n\n\n

oid (GitObjectID!)

The GitObjectID that the new Ref shall target. Must point to a commit.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the Repository to create the Ref in.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateRepositoryInput

\n

Autogenerated input type of CreateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

hasIssuesEnabled (Boolean)

Indicates if the repository should have the issues feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasWikiEnabled (Boolean)

Indicates if the repository should have the wiki feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

homepageUrl (URI)

The URL for a web page about this repository.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID)

The ID of the owner for the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

teamId (ID)

When an organization is specified as the owner, this ID identifies the team\nthat should be granted access to the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

template (Boolean)

Whether this repository should be marked as a template such that anyone who\ncan access it can create new repositories with the same files and directory structure.

\n\n\n\n\n\n\n\n\n\n\n\n

visibility (RepositoryVisibility!)

Indicates the repository's visibility level.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateSponsorsTierInput

\n

Autogenerated input type of CreateSponsorsTier.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

amount (Int!)

The value of the new tier in US dollars. Valid values: 1-12000.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String!)

A description of what this tier is, what perks sponsors might receive, what a sponsorship at this tier means for you, etc.

\n\n\n\n\n\n\n\n\n\n\n\n

isRecurring (Boolean)

Whether sponsorships using this tier should happen monthly/yearly or just once.

\n\n\n\n\n\n\n\n\n\n\n\n

publish (Boolean)

Whether to make the tier available immediately for sponsors to choose.\nDefaults to creating a draft tier that will not be publicly visible.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID)

Optional ID of the private repository that sponsors at this tier should gain\nread-only access to. Must be owned by an organization.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryName (String)

Optional name of the private repository that sponsors at this tier should gain\nread-only access to. Must be owned by an organization. Necessary if\nrepositoryOwnerLogin is given. Will be ignored if repositoryId is given.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryOwnerLogin (String)

Optional login of the organization owner of the private repository that\nsponsors at this tier should gain read-only access to. Necessary if\nrepositoryName is given. Will be ignored if repositoryId is given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who owns the GitHub Sponsors profile.\nDefaults to the current user if omitted and sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who owns the GitHub Sponsors profile.\nDefaults to the current user if omitted and sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

welcomeMessage (String)

Optional message new sponsors at this tier will receive.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateSponsorshipInput

\n

Autogenerated input type of CreateSponsorship.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

amount (Int)

The amount to pay to the sponsorable in US dollars. Required if a tierId is not specified. Valid values: 1-12000.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isRecurring (Boolean)

Whether the sponsorship should happen monthly/yearly or just this one time. Required if a tierId is not specified.

\n\n\n\n\n\n\n\n\n\n\n\n

privacyLevel (SponsorshipPrivacy)

Specify whether others should be able to see that the sponsor is sponsoring\nthe sponsorable. Public visibility still does not reveal which tier is used.

\n\n\n\n\n\n\n\n\n\n\n\n

receiveEmails (Boolean)

Whether the sponsor should receive email updates from the sponsorable.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorId (ID)

The ID of the user or organization who is acting as the sponsor, paying for\nthe sponsorship. Required if sponsorLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorLogin (String)

The username of the user or organization who is acting as the sponsor, paying\nfor the sponsorship. Required if sponsorId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who is receiving the sponsorship. Required if sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who is receiving the sponsorship. Required if sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

tierId (ID)

The ID of one of sponsorable's existing tiers to sponsor at. Required if amount is not specified.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateTeamDiscussionCommentInput

\n

Autogenerated input type of CreateTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The content of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The ID of the discussion to which the comment belongs.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateTeamDiscussionInput

\n

Autogenerated input type of CreateTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The content of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

private (Boolean)

If true, restricts the visibility of this discussion to team members and\norganization admins. If false or not specified, allows any organization member\nto view this discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

teamId (ID!)

The ID of the team to which the discussion belongs.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeclineTopicSuggestionInput

\n

Autogenerated input type of DeclineTopicSuggestion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the suggested topic.

\n\n\n\n\n\n\n\n\n\n\n\n

reason (TopicSuggestionDeclineReason!)

The reason why the suggested topic is declined.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteBranchProtectionRuleInput

\n

Autogenerated input type of DeleteBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branchProtectionRuleId (ID!)

The global relay id of the branch protection rule to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDeploymentInput

\n

Autogenerated input type of DeleteDeployment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the deployment to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDiscussionCommentInput

\n

Autogenerated input type of DeleteDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node id of the discussion comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDiscussionInput

\n

Autogenerated input type of DeleteDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The id of the discussion to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteEnvironmentInput

\n

Autogenerated input type of DeleteEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the environment to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIpAllowListEntryInput

\n

Autogenerated input type of DeleteIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ipAllowListEntryId (ID!)

The ID of the IP allow list entry to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIssueCommentInput

\n

Autogenerated input type of DeleteIssueComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIssueInput

\n

Autogenerated input type of DeleteIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteLabelInput

\n

Autogenerated input type of DeleteLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

DeleteLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the label to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePackageVersionInput

\n

Autogenerated input type of DeletePackageVersion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

packageVersionId (ID!)

The ID of the package version to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectCardInput

\n

Autogenerated input type of DeleteProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

cardId (ID!)

The id of the card to delete.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectColumnInput

\n

Autogenerated input type of DeleteProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectInput

\n

Autogenerated input type of DeleteProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Project ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectNextItemInput

\n

Autogenerated input type of DeleteProjectNextItem.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

itemId (ID!)

The ID of the item to be removed.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project from which the item should be removed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePullRequestReviewCommentInput

\n

Autogenerated input type of DeletePullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePullRequestReviewInput

\n

Autogenerated input type of DeletePullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteRefInput

\n

Autogenerated input type of DeleteRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The Node ID of the Ref to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteTeamDiscussionCommentInput

\n

Autogenerated input type of DeleteTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteTeamDiscussionInput

\n

Autogenerated input type of DeleteTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The discussion ID to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteVerifiableDomainInput

\n

Autogenerated input type of DeleteVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeploymentOrder

\n

Ordering options for deployment connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (DeploymentOrderField!)

The field to order deployments by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDisablePullRequestAutoMergeInput

\n

Autogenerated input type of DisablePullRequestAutoMerge.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to disable auto merge on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDiscussionOrder

\n

Ways in which lists of discussions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order discussions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (DiscussionOrderField!)

The field by which to order discussions.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDismissPullRequestReviewInput

\n

Autogenerated input type of DismissPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String!)

The contents of the pull request review dismissal message.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDismissRepositoryVulnerabilityAlertInput

\n

Autogenerated input type of DismissRepositoryVulnerabilityAlert.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissReason (DismissReason!)

The reason the Dependabot alert is being dismissed.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryVulnerabilityAlertId (ID!)

The Dependabot alert ID to dismiss.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDraftPullRequestReviewComment

\n

Specifies a review comment to be left with a Pull Request Review.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the comment to leave.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int!)

Position in the file to leave a comment on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDraftPullRequestReviewThread

\n

Specifies a review comment thread to be left with a Pull Request Review.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the comment to leave.

\n\n\n\n\n\n\n\n\n\n\n\n

line (Int!)

The line of the blob to which the thread refers. The end of the line range for multi-line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

side (DiffSide)

The side of the diff on which the line resides. For multi-line comments, this is the side for the end of the line range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int)

The first line of the range to which the comment refers.

\n\n\n\n\n\n\n\n\n\n\n\n

startSide (DiffSide)

The side of the diff on which the start line resides.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnablePullRequestAutoMergeInput

\n

Autogenerated input type of EnablePullRequestAutoMerge.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this merge.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitBody (String)

Commit body to use for the commit when the PR is mergable; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

commitHeadline (String)

Commit headline to use for the commit when the PR is mergable; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

mergeMethod (PullRequestMergeMethod)

The merge method to use. If omitted, defaults to 'MERGE'.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to enable auto-merge on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseAdministratorInvitationOrder

\n

Ordering options for enterprise administrator invitation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseAdministratorInvitationOrderField!)

The field to order enterprise administrator invitations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseMemberOrder

\n

Ordering options for enterprise member connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseMemberOrderField!)

The field to order enterprise members by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerInstallationOrder

\n

Ordering options for Enterprise Server installation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerInstallationOrderField!)

The field to order Enterprise Server installations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountEmailOrder

\n

Ordering options for Enterprise Server user account email connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountEmailOrderField!)

The field to order emails by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountOrder

\n

Ordering options for Enterprise Server user account connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountOrderField!)

The field to order user accounts by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountsUploadOrder

\n

Ordering options for Enterprise Server user accounts upload connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountsUploadOrderField!)

The field to order user accounts uploads by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileAddition

\n

A command to add a file at the given path with the given contents as part of a\ncommit. Any existing file at that that path will be replaced.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

contents (Base64String!)

The base64 encoded contents of the file.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path in the repository where the file will be located.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileChanges

\n

A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file additions and zero or more\nfile deletions.

\n

Both fields are optional; omitting both will produce a commit with no\nfile changes.

\n

deletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.

\n

path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.

\n

Encoding

\n

File contents must be provided in full for each FileAddition.

\n

The contents of a FileAddition must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.

\n

The encoded contents may be binary.

\n

For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (\\n or \\r\\n), and that all files end\nwith a newline.

\n

Modeling file changes

\n

Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:

\n
    \n
  1. \n

    New file addition: create file hello world\\n at path docs/README.txt:

    \n

    {\n"additions" [\n{\n"path": "docs/README.txt",\n"contents": base64encode("hello world\\n")\n}\n]\n}

    \n
    2. \n
  2. \n

    Existing file modification: change existing docs/README.txt to have new\ncontent new content here\\n:

    \n
    {\n  "additions" [\n    {\n      "path": "docs/README.txt",\n      "contents": base64encode("new content here\\n")\n    }\n  ]\n}\n
    \n
    3. \n
  3. \n

    Existing file deletion: remove existing file docs/README.txt.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt"\n    }\n  ]\n}\n
    \n
    4. \n
  4. \n

    File rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt",\n    }\n  ],\n  "additions" [\n    {\n      "path": "newdocs/README.txt",\n      "contents": base64encode("hello world\\n")\n    }\n  ]\n}\n
    \n
    5. \n
  5. \n

    File rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt",\n    }\n  ],\n  "additions" [\n    {\n      "path": "newdocs/README.txt",\n      "contents": base64encode("new contents\\n")\n    }\n  ]\n}.\n
    \n
    6. \n
\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

additions ([FileAddition!])

File to add or change.

\n\n\n\n\n\n\n\n\n\n\n\n

deletions ([FileDeletion!])

Files to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileDeletion

\n

A command to delete the file at the given path as part of a commit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n
NameDescription

path (String!)

The path to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFollowOrganizationInput

\n

Autogenerated input type of FollowOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

ID of the organization to follow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFollowUserInput

\n

Autogenerated input type of FollowUser.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

ID of the user to follow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGistOrder

\n

Ordering options for gist connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (GistOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGrantEnterpriseOrganizationsMigratorRoleInput

\n

Autogenerated input type of GrantEnterpriseOrganizationsMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which all organizations managed by it will be granted the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to grant the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGrantMigratorRoleInput

\n

Autogenerated input type of GrantMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actor (String!)

The user login or Team slug to grant the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

actorType (ActorType!)

Specifies the type of the actor, can be either USER or TEAM.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization that the user/team belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nImportProjectInput

\n

Autogenerated input type of ImportProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of Project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnImports ([ProjectColumnImport!]!)

A list of columns containing issues and pull requests.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of Project.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerName (String!)

The name of the Organization or User to create the Project under.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Whether the Project is public or not.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nInviteEnterpriseAdminInput

\n

Autogenerated input type of InviteEnterpriseAdmin.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

email (String)

The email of the person to invite as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which you want to invite an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

invitee (String)

The login of a user to invite as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

role (EnterpriseAdministratorRole)

The role of the administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIpAllowListEntryOrder

\n

Ordering options for IP allow list entry connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IpAllowListEntryOrderField!)

The field to order IP allow list entries by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueCommentOrder

\n

Ways in which lists of issue comments can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order issue comments by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IssueCommentOrderField!)

The field in which to order issue comments by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueFilters

\n

Ways in which to filter lists of issues.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignee (String)

List issues assigned to given name. Pass in null for issues with no assigned\nuser, and * for issues assigned to any user.

\n\n\n\n\n\n\n\n\n\n\n\n

createdBy (String)

List issues created by given name.

\n\n\n\n\n\n\n\n\n\n\n\n

labels ([String!])

List issues where the list of label names exist on the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

mentioned (String)

List issues where the given name is mentioned in the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestone (String)

List issues by given milestone argument. If an string representation of an\ninteger is passed, it should refer to a milestone by its database ID. Pass in\nnull for issues with no milestone, and * for issues that are assigned to any milestone.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneNumber (String)

List issues by given milestone argument. If an string representation of an\ninteger is passed, it should refer to a milestone by its number field. Pass in\nnull for issues with no milestone, and * for issues that are assigned to any milestone.

\n\n\n\n\n\n\n\n\n\n\n\n

since (DateTime)

List issues that have been updated at or after the given date.

\n\n\n\n\n\n\n\n\n\n\n\n

states ([IssueState!])

List issues filtered by the list of states given.

\n\n\n\n\n\n\n\n\n\n\n\n

viewerSubscribed (Boolean)

List issues subscribed to by viewer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueOrder

\n

Ways in which lists of issues can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order issues by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IssueOrderField!)

The field in which to order issues by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLabelOrder

\n

Ways in which lists of labels can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order labels by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (LabelOrderField!)

The field in which to order labels by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLanguageOrder

\n

Ordering options for language connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (LanguageOrderField!)

The field to order languages by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLinkRepositoryToProjectInput

\n

Autogenerated input type of LinkRepositoryToProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to link to a Repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the Repository to link to a Project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLockLockableInput

\n

Autogenerated input type of LockLockable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

lockReason (LockReason)

A reason for why the item will be locked.

\n\n\n\n\n\n\n\n\n\n\n\n

lockableId (ID!)

ID of the item to be locked.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkDiscussionCommentAsAnswerInput

\n

Autogenerated input type of MarkDiscussionCommentAsAnswer.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion comment to mark as an answer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkFileAsViewedInput

\n

Autogenerated input type of MarkFileAsViewed.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to mark as viewed.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkPullRequestReadyForReviewInput

\n

Autogenerated input type of MarkPullRequestReadyForReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be marked as ready for review.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMergeBranchInput

\n

Autogenerated input type of MergeBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this commit.

\n\n\n\n\n\n\n\n\n\n\n\n

base (String!)

The name of the base branch that the provided head will be merged into.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitMessage (String)

Message to use for the merge commit. If omitted, a default will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

head (String!)

The head to merge into the base branch. This can be a branch name or a commit GitObjectID.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the Repository containing the base branch that will be modified.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMergePullRequestInput

\n

Autogenerated input type of MergePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this merge.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitBody (String)

Commit body to use for the merge commit; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

commitHeadline (String)

Commit headline to use for the merge commit; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID)

OID that the pull request head ref must match to allow merge; if omitted, no check is performed.

\n\n\n\n\n\n\n\n\n\n\n\n

mergeMethod (PullRequestMergeMethod)

The merge method to use. If omitted, defaults to 'MERGE'.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be merged.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMilestoneOrder

\n

Ordering options for milestone connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (MilestoneOrderField!)

The field to order milestones by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMinimizeCommentInput

\n

Autogenerated input type of MinimizeComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

classifier (ReportedContentClassifiers!)

The classification of comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMoveProjectCardInput

\n

Autogenerated input type of MoveProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterCardId (ID)

Place the new card after the card with this id. Pass null to place it at the top.

\n\n\n\n\n\n\n\n\n\n\n\n

cardId (ID!)

The id of the card to move.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to move it into.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMoveProjectColumnInput

\n

Autogenerated input type of MoveProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterColumnId (ID)

Place the new column after the column with this id. Pass null to place it at the front.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to move.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nOrgEnterpriseOwnerOrder

\n

Ordering options for an organization's enterprise owner connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (OrgEnterpriseOwnerOrderField!)

The field to order enterprise owners by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nOrganizationOrder

\n

Ordering options for organization connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (OrganizationOrderField!)

The field to order organizations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPackageFileOrder

\n

Ways in which lists of package files can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The direction in which to order package files by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PackageFileOrderField)

The field in which to order package files by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPackageOrder

\n

Ways in which lists of packages can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The direction in which to order packages by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PackageOrderField)

The field in which to order packages by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPackageVersionOrder

\n

Ways in which lists of package versions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The direction in which to order package versions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PackageVersionOrderField)

The field in which to order package versions by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPinIssueInput

\n

Autogenerated input type of PinIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to be pinned.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectCardImport

\n

An issue or PR and its owning repository to be used in a project card.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

number (Int!)

The issue or pull request number.

\n\n\n\n\n\n\n\n\n\n\n\n

repository (String!)

Repository name with owner (owner/repository).

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectColumnImport

\n

A project column and a list of its issues and PRs.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

columnName (String!)

The name of the column.

\n\n\n\n\n\n\n\n\n\n\n\n

issues ([ProjectCardImport!])

A list of issues and pull requests in the column.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int!)

The position of the column, starting from 0.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectOrder

\n

Ways in which lists of projects can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order projects by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ProjectOrderField!)

The field in which to order projects by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPullRequestOrder

\n

Ways in which lists of issues can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order pull requests by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PullRequestOrderField!)

The field in which to order pull requests by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReactionOrder

\n

Ways in which lists of reactions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order reactions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ReactionOrderField!)

The field in which to order reactions by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRefOrder

\n

Ways in which lists of git refs can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order refs by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RefOrderField!)

The field in which to order refs by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRefUpdate

\n

A ref update.

\n
\n\n
\n \n
\n

Preview notice

\n

RefUpdate is available under the Update refs preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterOid (GitObjectID!)

The value this ref should be updated to.

\n\n\n\n\n\n\n\n\n\n\n\n

beforeOid (GitObjectID)

The value this ref needs to point to before the update.

\n\n\n\n\n\n\n\n\n\n\n\n

force (Boolean)

Force a non fast-forward update.

\n\n\n\n\n\n\n\n\n\n\n\n

name (GitRefname!)

The fully qualified name of the ref to be update. For example refs/heads/branch-name.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRegenerateEnterpriseIdentityProviderRecoveryCodesInput

\n

Autogenerated input type of RegenerateEnterpriseIdentityProviderRecoveryCodes.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set an identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRegenerateVerifiableDomainTokenInput

\n

Autogenerated input type of RegenerateVerifiableDomainToken.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to regenerate the verification token of.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRejectDeploymentsInput

\n

Autogenerated input type of RejectDeployments.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comment (String)

Optional comment for rejecting deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentIds ([ID!]!)

The ids of environments to reject deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

workflowRunId (ID!)

The node ID of the workflow run containing the pending deployments.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReleaseOrder

\n

Ways in which lists of releases can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order releases by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ReleaseOrderField!)

The field in which to order releases by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveAssigneesFromAssignableInput

\n

Autogenerated input type of RemoveAssigneesFromAssignable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignableId (ID!)

The id of the assignable object to remove assignees from.

\n\n\n\n\n\n\n\n\n\n\n\n

assigneeIds ([ID!]!)

The id of users to remove as assignees.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseAdminInput

\n

Autogenerated input type of RemoveEnterpriseAdmin.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The Enterprise ID from which to remove the administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to remove as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseIdentityProviderInput

\n

Autogenerated input type of RemoveEnterpriseIdentityProvider.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise from which to remove the identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseOrganizationInput

\n

Autogenerated input type of RemoveEnterpriseOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise from which the organization should be removed.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to remove from the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseSupportEntitlementInput

\n

Autogenerated input type of RemoveEnterpriseSupportEntitlement.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the admin belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of a member who will lose the support entitlement.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveLabelsFromLabelableInput

\n

Autogenerated input type of RemoveLabelsFromLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!]!)

The ids of labels to remove.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the Labelable to remove labels from.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveOutsideCollaboratorInput

\n

Autogenerated input type of RemoveOutsideCollaborator.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to remove the outside collaborator from.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

The ID of the outside collaborator to remove.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveReactionInput

\n

Autogenerated input type of RemoveReaction.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

content (ReactionContent!)

The name of the emoji reaction to remove.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveStarInput

\n

Autogenerated input type of RemoveStar.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

starrableId (ID!)

The Starrable ID to unstar.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveUpvoteInput

\n

Autogenerated input type of RemoveUpvote.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the discussion or comment to remove upvote.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReopenIssueInput

\n

Autogenerated input type of ReopenIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

ID of the issue to be opened.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReopenPullRequestInput

\n

Autogenerated input type of ReopenPullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be reopened.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryInvitationOrder

\n

Ordering options for repository invitation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryInvitationOrderField!)

The field to order repository invitations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryMigrationOrder

\n

Ordering options for repository migrations.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (RepositoryMigrationOrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryMigrationOrderField!)

The field to order repository migrations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryOrder

\n

Ordering options for repository connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRequestReviewsInput

\n

Autogenerated input type of RequestReviews.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

teamIds ([ID!])

The Node IDs of the team to request.

\n\n\n\n\n\n\n\n\n\n\n\n

union (Boolean)

Add users to the set rather than replace.

\n\n\n\n\n\n\n\n\n\n\n\n

userIds ([ID!])

The Node IDs of the user to request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRequiredStatusCheckInput

\n

Specifies the attributes for a new or updated required status check.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (ID)

The ID of the App that must set the status in order for it to be accepted.\nOmit this value to use whichever app has recently been setting this status, or\nuse "any" to allow any app to set the status.

\n\n\n\n\n\n\n\n\n\n\n\n

context (String!)

Status check context that must pass for commits to be accepted to the matching branch.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRerequestCheckSuiteInput

\n

Autogenerated input type of RerequestCheckSuite.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

checkSuiteId (ID!)

The Node ID of the check suite.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nResolveReviewThreadInput

\n

Autogenerated input type of ResolveReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

threadId (ID!)

The ID of the thread to resolve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRevokeEnterpriseOrganizationsMigratorRoleInput

\n

Autogenerated input type of RevokeEnterpriseOrganizationsMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which all organizations managed by it will be granted the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to revoke the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRevokeMigratorRoleInput

\n

Autogenerated input type of RevokeMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actor (String!)

The user login or Team slug to revoke the migrator role from.

\n\n\n\n\n\n\n\n\n\n\n\n

actorType (ActorType!)

Specifies the type of the actor, can be either USER or TEAM.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization that the user/team belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSavedReplyOrder

\n

Ordering options for saved reply connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SavedReplyOrderField!)

The field to order saved replies by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSecurityAdvisoryIdentifierFilter

\n

An advisory identifier to filter results on.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

type (SecurityAdvisoryIdentifierType!)

The identifier type.

\n\n\n\n\n\n\n\n\n\n\n\n

value (String!)

The identifier string. Supports exact or partial matching.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSecurityAdvisoryOrder

\n

Ordering options for security advisory connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SecurityAdvisoryOrderField!)

The field to order security advisories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSecurityVulnerabilityOrder

\n

Ordering options for security vulnerability connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SecurityVulnerabilityOrderField!)

The field to order security vulnerabilities by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetEnterpriseIdentityProviderInput

\n

Autogenerated input type of SetEnterpriseIdentityProvider.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

digestMethod (SamlDigestAlgorithm!)

The digest algorithm used to sign SAML requests for the identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set an identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

idpCertificate (String!)

The x509 certificate used by the identity provider to sign assertions and responses.

\n\n\n\n\n\n\n\n\n\n\n\n

issuer (String)

The Issuer Entity ID for the SAML identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

signatureMethod (SamlSignatureAlgorithm!)

The signature algorithm used to sign SAML requests for the identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

ssoUrl (URI!)

The URL endpoint for the identity provider's SAML SSO.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetOrganizationInteractionLimitInput

\n

Autogenerated input type of SetOrganizationInteractionLimit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expiry (RepositoryInteractionLimitExpiry)

When this limit should expire.

\n\n\n\n\n\n\n\n\n\n\n\n

limit (RepositoryInteractionLimit!)

The limit to set.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to set a limit for.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetRepositoryInteractionLimitInput

\n

Autogenerated input type of SetRepositoryInteractionLimit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expiry (RepositoryInteractionLimitExpiry)

When this limit should expire.

\n\n\n\n\n\n\n\n\n\n\n\n

limit (RepositoryInteractionLimit!)

The limit to set.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to set a limit for.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetUserInteractionLimitInput

\n

Autogenerated input type of SetUserInteractionLimit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expiry (RepositoryInteractionLimitExpiry)

When this limit should expire.

\n\n\n\n\n\n\n\n\n\n\n\n

limit (RepositoryInteractionLimit!)

The limit to set.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

The ID of the user to set a limit for.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorOrder

\n

Ordering options for connections to get sponsor entities for GitHub Sponsors.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorOrderField!)

The field to order sponsor entities by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorableOrder

\n

Ordering options for connections to get sponsorable entities for GitHub Sponsors.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorableOrderField!)

The field to order sponsorable entities by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorsActivityOrder

\n

Ordering options for GitHub Sponsors activity connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorsActivityOrderField!)

The field to order activity by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorsTierOrder

\n

Ordering options for Sponsors tiers connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorsTierOrderField!)

The field to order tiers by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorshipNewsletterOrder

\n

Ordering options for sponsorship newsletter connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorshipNewsletterOrderField!)

The field to order sponsorship newsletters by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorshipOrder

\n

Ordering options for sponsorship connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorshipOrderField!)

The field to order sponsorship by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nStarOrder

\n

Ways in which star connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (StarOrderField!)

The field in which to order nodes by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nStartRepositoryMigrationInput

\n

Autogenerated input type of StartRepositoryMigration.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

accessToken (String)

The Octoshift migration source access token.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

continueOnError (Boolean)

Whether to continue the migration on error.

\n\n\n\n\n\n\n\n\n\n\n\n

gitArchiveUrl (String)

The signed URL to access the user-uploaded git archive.

\n\n\n\n\n\n\n\n\n\n\n\n

githubPat (String)

The GitHub personal access token of the user importing to the target repository.

\n\n\n\n\n\n\n\n\n\n\n\n

metadataArchiveUrl (String)

The signed URL to access the user-uploaded metadata archive.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that will own the imported repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryName (String!)

The name of the imported repository.

\n\n\n\n\n\n\n\n\n\n\n\n

skipReleases (Boolean)

Whether to skip migrating releases for the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

sourceId (ID!)

The ID of the Octoshift migration source.

\n\n\n\n\n\n\n\n\n\n\n\n

sourceRepositoryUrl (URI!)

The Octoshift migration source repository URL.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSubmitPullRequestReviewInput

\n

Autogenerated input type of SubmitPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The text field to set on the Pull Request Review.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

event (PullRequestReviewEvent!)

The event to send to the Pull Request Review.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The Pull Request ID to submit any pending reviews.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Pull Request Review ID to submit.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamDiscussionCommentOrder

\n

Ways in which team discussion comment connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamDiscussionCommentOrderField!)

The field by which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamDiscussionOrder

\n

Ways in which team discussion connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamDiscussionOrderField!)

The field by which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamMemberOrder

\n

Ordering options for team member connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamMemberOrderField!)

The field to order team members by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamOrder

\n

Ways in which team connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamOrderField!)

The field in which to order nodes by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamRepositoryOrder

\n

Ordering options for team repository connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamRepositoryOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTransferIssueInput

\n

Autogenerated input type of TransferIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The Node ID of the issue to be transferred.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository the issue should be transferred to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnarchiveRepositoryInput

\n

Autogenerated input type of UnarchiveRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to unarchive.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnfollowOrganizationInput

\n

Autogenerated input type of UnfollowOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

ID of the organization to unfollow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnfollowUserInput

\n

Autogenerated input type of UnfollowUser.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

ID of the user to unfollow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnlinkRepositoryFromProjectInput

\n

Autogenerated input type of UnlinkRepositoryFromProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project linked to the Repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the Repository linked to the Project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnlockLockableInput

\n

Autogenerated input type of UnlockLockable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

lockableId (ID!)

ID of the item to be unlocked.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkDiscussionCommentAsAnswerInput

\n

Autogenerated input type of UnmarkDiscussionCommentAsAnswer.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion comment to unmark as an answer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkFileAsViewedInput

\n

Autogenerated input type of UnmarkFileAsViewed.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to mark as unviewed.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkIssueAsDuplicateInput

\n

Autogenerated input type of UnmarkIssueAsDuplicate.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

canonicalId (ID!)

ID of the issue or pull request currently considered canonical/authoritative/original.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

duplicateId (ID!)

ID of the issue or pull request currently marked as a duplicate.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnminimizeCommentInput

\n

Autogenerated input type of UnminimizeComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnpinIssueInput

\n

Autogenerated input type of UnpinIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to be unpinned.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnresolveReviewThreadInput

\n

Autogenerated input type of UnresolveReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

threadId (ID!)

The ID of the thread to unresolve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateBranchProtectionRuleInput

\n

Autogenerated input type of UpdateBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowsDeletions (Boolean)

Can this branch be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

allowsForcePushes (Boolean)

Are force pushes allowed on this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

blocksCreations (Boolean)

Is branch creation a protected operation.

\n\n\n\n\n\n\n\n\n\n\n\n

branchProtectionRuleId (ID!)

The global relay id of the branch protection rule to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassForcePushActorIds ([ID!])

A list of User or Team IDs allowed to bypass force push targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassPullRequestActorIds ([ID!])

A list of User or Team IDs allowed to bypass pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissesStaleReviews (Boolean)

Will new commits pushed to matching branches dismiss pull request review approvals.

\n\n\n\n\n\n\n\n\n\n\n\n

isAdminEnforced (Boolean)

Can admins overwrite branch protection.

\n\n\n\n\n\n\n\n\n\n\n\n

pattern (String)

The glob-like pattern used to determine matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

pushActorIds ([ID!])

A list of User, Team or App IDs allowed to push to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredApprovingReviewCount (Int)

Number of approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusCheckContexts ([String!])

List of required status check contexts that must pass for commits to be accepted to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusChecks ([RequiredStatusCheckInput!])

The list of required status checks.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresApprovingReviews (Boolean)

Are approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCodeOwnerReviews (Boolean)

Are reviews from code owners required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCommitSignatures (Boolean)

Are commits required to be signed.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresConversationResolution (Boolean)

Are conversations required to be resolved before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresLinearHistory (Boolean)

Are merge commits prohibited from being pushed to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStatusChecks (Boolean)

Are status checks required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStrictStatusChecks (Boolean)

Are branches required to be up to date before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsPushes (Boolean)

Is pushing to matching branches restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsReviewDismissals (Boolean)

Is dismissal of pull request reviews restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewDismissalActorIds ([ID!])

A list of User or Team IDs allowed to dismiss reviews on pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateCheckRunInput

\n

Autogenerated input type of UpdateCheckRun.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actions ([CheckRunAction!])

Possible further actions the integrator can perform, which a user may trigger.

\n\n\n\n\n\n\n\n\n\n\n\n

checkRunId (ID!)

The node of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

completedAt (DateTime)

The time that the check run finished.

\n\n\n\n\n\n\n\n\n\n\n\n

conclusion (CheckConclusionState)

The final conclusion of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

detailsUrl (URI)

The URL of the integrator's site that has the full details of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

externalId (String)

A reference for the run on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

output (CheckRunOutput)

Descriptive details about the run.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

startedAt (DateTime)

The time that the check run began.

\n\n\n\n\n\n\n\n\n\n\n\n

status (RequestableCheckStatusState)

The current status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateCheckSuitePreferencesInput

\n

Autogenerated input type of UpdateCheckSuitePreferences.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoTriggerPreferences ([CheckSuiteAutoTriggerPreference!]!)

The check suite preferences to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateDiscussionCommentInput

\n

Autogenerated input type of UpdateDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The new contents of the comment body.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commentId (ID!)

The Node ID of the discussion comment to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateDiscussionInput

\n

Autogenerated input type of UpdateDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The new contents of the discussion body.

\n\n\n\n\n\n\n\n\n\n\n\n

categoryId (ID)

The Node ID of a discussion category within the same repository to change this discussion to.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The Node ID of the discussion to update.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The new discussion title.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseAdministratorRoleInput

\n

Autogenerated input type of UpdateEnterpriseAdministratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the admin belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of a administrator whose role is being changed.

\n\n\n\n\n\n\n\n\n\n\n\n

role (EnterpriseAdministratorRole!)

The new role for the Enterprise administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseAllowPrivateRepositoryForkingSettingInput

\n

Autogenerated input type of UpdateEnterpriseAllowPrivateRepositoryForkingSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the allow private repository forking setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the allow private repository forking setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseDefaultRepositoryPermissionSettingInput

\n

Autogenerated input type of UpdateEnterpriseDefaultRepositoryPermissionSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the base repository permission setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseDefaultRepositoryPermissionSettingValue!)

The value for the base repository permission setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanChangeRepositoryVisibilitySettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanChangeRepositoryVisibilitySetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can change repository visibility setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can change repository visibility setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanCreateRepositoriesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanCreateRepositoriesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can create repositories setting.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreateInternalRepositories (Boolean)

Allow members to create internal repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreatePrivateRepositories (Boolean)

Allow members to create private repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreatePublicRepositories (Boolean)

Allow members to create public repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreateRepositoriesPolicyEnabled (Boolean)

When false, allow member organizations to set their own repository creation member privileges.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseMembersCanCreateRepositoriesSettingValue)

Value for the members can create repositories setting on the enterprise. This\nor the granular public/private/internal allowed fields (but not both) must be provided.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanDeleteIssuesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanDeleteIssuesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can delete issues setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can delete issues setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanDeleteRepositoriesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanDeleteRepositoriesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can delete repositories setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can delete repositories setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanInviteCollaboratorsSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanInviteCollaboratorsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can invite collaborators setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can invite collaborators setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanMakePurchasesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanMakePurchasesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can make purchases setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseMembersCanMakePurchasesSettingValue!)

The value for the members can make purchases setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanUpdateProtectedBranchesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanUpdateProtectedBranchesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can update protected branches setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can update protected branches setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanViewDependencyInsightsSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanViewDependencyInsightsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can view dependency insights setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can view dependency insights setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseOrganizationProjectsSettingInput

\n

Autogenerated input type of UpdateEnterpriseOrganizationProjectsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the organization projects setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the organization projects setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseOwnerOrganizationRoleInput

\n

Autogenerated input type of UpdateEnterpriseOwnerOrganizationRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the owner belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization for membership change.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationRole (RoleInOrganization!)

The role to assume in the organization.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseProfileInput

\n

Autogenerated input type of UpdateEnterpriseProfile.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

The description of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The Enterprise ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n

location (String)

The location of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

websiteUrl (String)

The URL of the enterprise's website.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseRepositoryProjectsSettingInput

\n

Autogenerated input type of UpdateEnterpriseRepositoryProjectsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the repository projects setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the repository projects setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseTeamDiscussionsSettingInput

\n

Autogenerated input type of UpdateEnterpriseTeamDiscussionsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the team discussions setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the team discussions setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseTwoFactorAuthenticationRequiredSettingInput

\n

Autogenerated input type of UpdateEnterpriseTwoFactorAuthenticationRequiredSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the two factor authentication required setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledSettingValue!)

The value for the two factor authentication required setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnvironmentInput

\n

Autogenerated input type of UpdateEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentId (ID!)

The node ID of the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewers ([ID!])

The ids of users or teams that can approve deployments to this environment.

\n\n\n\n\n\n\n\n\n\n\n\n

waitTimer (Int)

The wait timer in minutes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListEnabledSettingInput

\n

Autogenerated input type of UpdateIpAllowListEnabledSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner on which to set the IP allow list enabled setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (IpAllowListEnabledSettingValue!)

The value for the IP allow list enabled setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListEntryInput

\n

Autogenerated input type of UpdateIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowListValue (String!)

An IP address or range of addresses in CIDR notation.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ipAllowListEntryId (ID!)

The ID of the IP allow list entry to update.

\n\n\n\n\n\n\n\n\n\n\n\n

isActive (Boolean!)

Whether the IP allow list entry is active when an IP allow list is enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

An optional name for the IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListForInstalledAppsEnabledSettingInput

\n

Autogenerated input type of UpdateIpAllowListForInstalledAppsEnabledSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (IpAllowListForInstalledAppsEnabledSettingValue!)

The value for the IP allow list configuration for installed GitHub Apps setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIssueCommentInput

\n

Autogenerated input type of UpdateIssueComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The updated text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the IssueComment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIssueInput

\n

Autogenerated input type of UpdateIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

An array of Node IDs of users for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body for the issue description.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the Issue to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

state (IssueState)

The desired issue state.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title for the issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateLabelInput

\n

Autogenerated input type of UpdateLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

color (String)

A 6 character hex code, without the leading #, identifying the updated color of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A brief description of the label, such as its purpose.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the label to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The updated name of the label.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateNotificationRestrictionSettingInput

\n

Autogenerated input type of UpdateNotificationRestrictionSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner on which to set the restrict notifications setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (NotificationRestrictionSettingValue!)

The value for the restrict notifications setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateOrganizationAllowPrivateRepositoryForkingSettingInput

\n

Autogenerated input type of UpdateOrganizationAllowPrivateRepositoryForkingSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

forkingEnabled (Boolean!)

Enable forking of private repositories in the organization?.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization on which to set the allow private repository forking setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectCardInput

\n

Autogenerated input type of UpdateProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isArchived (Boolean)

Whether or not the ProjectCard should be archived.

\n\n\n\n\n\n\n\n\n\n\n\n

note (String)

The note of ProjectCard.

\n\n\n\n\n\n\n\n\n\n\n\n

projectCardId (ID!)

The ProjectCard ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectColumnInput

\n

Autogenerated input type of UpdateProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of project column.

\n\n\n\n\n\n\n\n\n\n\n\n

projectColumnId (ID!)

The ProjectColumn ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectDraftIssueInput

\n

Autogenerated input type of UpdateProjectDraftIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The IDs of the assignees of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

draftIssueId (ID!)

The ID of the draft issue to update.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectInput

\n

Autogenerated input type of UpdateProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of project.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Project ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Whether the project is public or not.

\n\n\n\n\n\n\n\n\n\n\n\n

state (ProjectState)

Whether the project is open or closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectNextInput

\n

Autogenerated input type of UpdateProjectNext.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

closed (Boolean)

Set the project to closed or open.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

Set the readme description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to update.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Set the project to public or private.

\n\n\n\n\n\n\n\n\n\n\n\n

shortDescription (String)

Set the short description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

Set the title of the project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectNextItemFieldInput

\n

Autogenerated input type of UpdateProjectNextItemField.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

fieldId (ID)

The id of the field to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

itemId (ID!)

The id of the item to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project.

\n\n\n\n\n\n\n\n\n\n\n\n

value (String!)

The value which will be set on the field.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestBranchInput

\n

Autogenerated input type of UpdatePullRequestBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID)

The head ref oid for the upstream branch.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestInput

\n

Autogenerated input type of UpdatePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

An array of Node IDs of users for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

baseRefName (String)

The name of the branch you want your changes pulled into. This should be an existing branch\non the current repository.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The contents of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

maintainerCanModify (Boolean)

Indicates whether maintainers can modify the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

state (PullRequestUpdateState)

The target state of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestReviewCommentInput

\n

Autogenerated input type of UpdatePullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewCommentId (ID!)

The Node ID of the comment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestReviewInput

\n

Autogenerated input type of UpdatePullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the pull request review body.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRefInput

\n

Autogenerated input type of UpdateRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

force (Boolean)

Permit updates of branch Refs that are not fast-forwards?.

\n\n\n\n\n\n\n\n\n\n\n\n

oid (GitObjectID!)

The GitObjectID that the Ref shall be updated to target.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The Node ID of the Ref to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRefsInput

\n

Autogenerated input type of UpdateRefs.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateRefsInput is available under the Update refs preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

refUpdates ([RefUpdate!]!)

A list of ref updates.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRepositoryInput

\n

Autogenerated input type of UpdateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A new description for the repository. Pass an empty string to erase the existing description.

\n\n\n\n\n\n\n\n\n\n\n\n

hasIssuesEnabled (Boolean)

Indicates if the repository should have the issues feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasProjectsEnabled (Boolean)

Indicates if the repository should have the project boards feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasWikiEnabled (Boolean)

Indicates if the repository should have the wiki feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

homepageUrl (URI)

The URL for a web page about this repository. Pass an empty string to erase the existing URL.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The new name of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to update.

\n\n\n\n\n\n\n\n\n\n\n\n

template (Boolean)

Whether this repository should be marked as a template such that anyone who\ncan access it can create new repositories with the same files and directory structure.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateSponsorshipPreferencesInput

\n

Autogenerated input type of UpdateSponsorshipPreferences.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

privacyLevel (SponsorshipPrivacy)

Specify whether others should be able to see that the sponsor is sponsoring\nthe sponsorable. Public visibility still does not reveal which tier is used.

\n\n\n\n\n\n\n\n\n\n\n\n

receiveEmails (Boolean)

Whether the sponsor should receive email updates from the sponsorable.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorId (ID)

The ID of the user or organization who is acting as the sponsor, paying for\nthe sponsorship. Required if sponsorLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorLogin (String)

The username of the user or organization who is acting as the sponsor, paying\nfor the sponsorship. Required if sponsorId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who is receiving the sponsorship. Required if sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who is receiving the sponsorship. Required if sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateSubscriptionInput

\n

Autogenerated input type of UpdateSubscription.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

state (SubscriptionState!)

The new state of the subscription.

\n\n\n\n\n\n\n\n\n\n\n\n

subscribableId (ID!)

The Node ID of the subscribable object to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamDiscussionCommentInput

\n

Autogenerated input type of UpdateTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The updated text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

bodyVersion (String)

The current version of the body content.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamDiscussionInput

\n

Autogenerated input type of UpdateTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The updated text of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

bodyVersion (String)

The current version of the body content. If provided, this update operation\nwill be rejected if the given version does not match the latest version on the server.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

pinned (Boolean)

If provided, sets the pinned state of the updated discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The updated title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamReviewAssignmentInput

\n

Autogenerated input type of UpdateTeamReviewAssignment.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateTeamReviewAssignmentInput is available under the Team review assignments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

algorithm (TeamReviewAssignmentAlgorithm)

The algorithm to use for review assignment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enabled (Boolean!)

Turn on or off review assignment.

\n\n\n\n\n\n\n\n\n\n\n\n

excludedTeamMemberIds ([ID!])

An array of team member IDs to exclude.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the team to update review assignments of.

\n\n\n\n\n\n\n\n\n\n\n\n

notifyTeam (Boolean)

Notify the entire team of the PR if it is delegated.

\n\n\n\n\n\n\n\n\n\n\n\n

teamMemberCount (Int)

The number of team members to assign.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamsRepositoryInput

\n

Autogenerated input type of UpdateTeamsRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

permission (RepositoryPermission!)

Permission that should be granted to the teams.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

Repository ID being granted access to.

\n\n\n\n\n\n\n\n\n\n\n\n

teamIds ([ID!]!)

A list of teams being granted access. Limit: 10.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTopicsInput

\n

Autogenerated input type of UpdateTopics.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

topicNames ([String!]!)

An array of topic names.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUserStatusOrder

\n

Ordering options for user status connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (UserStatusOrderField!)

The field to order user statuses by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nVerifiableDomainOrder

\n

Ordering options for verifiable domain connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (VerifiableDomainOrderField!)

The field to order verifiable domains by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nVerifyVerifiableDomainInput

\n

Autogenerated input type of VerifyVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to verify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n", + "html": "
\n
\n

\n \n \nAbortQueuedMigrationsInput

\n

Autogenerated input type of AbortQueuedMigrations.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that is running the migrations.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAcceptEnterpriseAdministratorInvitationInput

\n

Autogenerated input type of AcceptEnterpriseAdministratorInvitation.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

invitationId (ID!)

The id of the invitation being accepted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAcceptTopicSuggestionInput

\n

Autogenerated input type of AcceptTopicSuggestion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the suggested topic.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddAssigneesToAssignableInput

\n

Autogenerated input type of AddAssigneesToAssignable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignableId (ID!)

The id of the assignable object to add assignees to.

\n\n\n\n\n\n\n\n\n\n\n\n

assigneeIds ([ID!]!)

The id of users to add as assignees.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddCommentInput

\n

Autogenerated input type of AddComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddDiscussionCommentInput

\n

Autogenerated input type of AddDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The Node ID of the discussion to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

replyToId (ID)

The Node ID of the discussion comment within this discussion to reply to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddEnterpriseSupportEntitlementInput

\n

Autogenerated input type of AddEnterpriseSupportEntitlement.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the admin belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of a member who will receive the support entitlement.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddLabelsToLabelableInput

\n

Autogenerated input type of AddLabelsToLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!]!)

The ids of the labels to add.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the labelable object to add labels to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectCardInput

\n

Autogenerated input type of AddProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

contentId (ID)

The content of the card. Must be a member of the ProjectCardItem union.

\n\n\n\n\n\n\n\n\n\n\n\n

note (String)

The note on the card.

\n\n\n\n\n\n\n\n\n\n\n\n

projectColumnId (ID!)

The Node ID of the ProjectColumn.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectColumnInput

\n

Autogenerated input type of AddProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the column.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Node ID of the project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectDraftIssueInput

\n

Autogenerated input type of AddProjectDraftIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The IDs of the assignees of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to add the draft issue to.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectNextItemInput

\n

Autogenerated input type of AddProjectNextItem.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

contentId (ID!)

The content id of the item (Issue or PullRequest).

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to add the item to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewCommentInput

\n

Autogenerated input type of AddPullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitOID (GitObjectID)

The SHA of the commit to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

inReplyTo (ID)

The comment id to reply to.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String)

The relative path of the file to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int)

The line index in the diff to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The node ID of the pull request reviewing.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Node ID of the review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewInput

\n

Autogenerated input type of AddPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The contents of the review body comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comments ([DraftPullRequestReviewComment])

The review line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

commitOID (GitObjectID)

The commit OID the review pertains to.

\n\n\n\n\n\n\n\n\n\n\n\n

event (PullRequestReviewEvent)

The event to perform on the pull request review.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

threads ([DraftPullRequestReviewThread])

The review line comment threads.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewThreadInput

\n

Autogenerated input type of AddPullRequestReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the thread's first comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

line (Int!)

The line of the blob to which the thread refers. The end of the line range for multi-line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The node ID of the pull request reviewing.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Node ID of the review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

side (DiffSide)

The side of the diff on which the line resides. For multi-line comments, this is the side for the end of the line range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int)

The first line of the range to which the comment refers.

\n\n\n\n\n\n\n\n\n\n\n\n

startSide (DiffSide)

The side of the diff on which the start line resides.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddReactionInput

\n

Autogenerated input type of AddReaction.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

content (ReactionContent!)

The name of the emoji to react with.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddStarInput

\n

Autogenerated input type of AddStar.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

starrableId (ID!)

The Starrable ID to star.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddUpvoteInput

\n

Autogenerated input type of AddUpvote.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the discussion or comment to upvote.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddVerifiableDomainInput

\n

Autogenerated input type of AddVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

domain (URI!)

The URL of the domain.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner to add the domain to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nApproveDeploymentsInput

\n

Autogenerated input type of ApproveDeployments.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comment (String)

Optional comment for approving deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentIds ([ID!]!)

The ids of environments to reject deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

workflowRunId (ID!)

The node ID of the workflow run containing the pending deployments.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nApproveVerifiableDomainInput

\n

Autogenerated input type of ApproveVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to approve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nArchiveRepositoryInput

\n

Autogenerated input type of ArchiveRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to mark as archived.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAuditLogOrder

\n

Ordering options for Audit Log connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (AuditLogOrderField)

The field to order Audit Logs by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCancelEnterpriseAdminInvitationInput

\n

Autogenerated input type of CancelEnterpriseAdminInvitation.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

invitationId (ID!)

The Node ID of the pending enterprise administrator invitation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCancelSponsorshipInput

\n

Autogenerated input type of CancelSponsorship.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorId (ID)

The ID of the user or organization who is acting as the sponsor, paying for\nthe sponsorship. Required if sponsorLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorLogin (String)

The username of the user or organization who is acting as the sponsor, paying\nfor the sponsorship. Required if sponsorId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who is receiving the sponsorship. Required if sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who is receiving the sponsorship. Required if sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nChangeUserStatusInput

\n

Autogenerated input type of ChangeUserStatus.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

emoji (String)

The emoji to represent your status. Can either be a native Unicode emoji or an emoji name with colons, e.g., 😀.

\n\n\n\n\n\n\n\n\n\n\n\n

expiresAt (DateTime)

If set, the user status will not be shown after this date.

\n\n\n\n\n\n\n\n\n\n\n\n

limitedAvailability (Boolean)

Whether this status should indicate you are not fully available on GitHub, e.g., you are away.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String)

A short description of your current status.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID)

The ID of the organization whose members will be allowed to see the status. If\nomitted, the status will be publicly visible.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckAnnotationData

\n

Information from a check run analysis to specific lines of code.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

annotationLevel (CheckAnnotationLevel!)

Represents an annotation's information level.

\n\n\n\n\n\n\n\n\n\n\n\n

location (CheckAnnotationRange!)

The location of the annotation.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String!)

A short description of the feedback for these lines of code.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to add an annotation to.

\n\n\n\n\n\n\n\n\n\n\n\n

rawDetails (String)

Details about this annotation.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title that represents the annotation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckAnnotationRange

\n

Information from a check run analysis to specific lines of code.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

endColumn (Int)

The ending column of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

endLine (Int!)

The ending line of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

startColumn (Int)

The starting column of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int!)

The starting line of the range.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunAction

\n

Possible further actions the integrator can perform.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

description (String!)

A short explanation of what this action would do.

\n\n\n\n\n\n\n\n\n\n\n\n

identifier (String!)

A reference for the action on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

label (String!)

The text to be displayed on a button in the web UI.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunFilter

\n

The filters that are available when fetching check runs.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (Int)

Filters the check runs created by this application ID.

\n\n\n\n\n\n\n\n\n\n\n\n

checkName (String)

Filters the check runs by this name.

\n\n\n\n\n\n\n\n\n\n\n\n

checkType (CheckRunType)

Filters the check runs by this type.

\n\n\n\n\n\n\n\n\n\n\n\n

status (CheckStatusState)

Filters the check runs by this status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunOutput

\n

Descriptive details about the check run.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

annotations ([CheckAnnotationData!])

The annotations that are made as part of the check run.

\n\n\n\n\n\n\n\n\n\n\n\n

images ([CheckRunOutputImage!])

Images attached to the check run output displayed in the GitHub pull request UI.

\n\n\n\n\n\n\n\n\n\n\n\n

summary (String!)

The summary of the check run (supports Commonmark).

\n\n\n\n\n\n\n\n\n\n\n\n

text (String)

The details of the check run (supports Commonmark).

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

A title to provide for this check run.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunOutputImage

\n

Images attached to the check run output displayed in the GitHub pull request UI.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

alt (String!)

The alternative text for the image.

\n\n\n\n\n\n\n\n\n\n\n\n

caption (String)

A short image description.

\n\n\n\n\n\n\n\n\n\n\n\n

imageUrl (URI!)

The full URL of the image.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckSuiteAutoTriggerPreference

\n

The auto-trigger preferences that are available for check suites.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (ID!)

The node ID of the application that owns the check suite.

\n\n\n\n\n\n\n\n\n\n\n\n

setting (Boolean!)

Set to true to enable automatic creation of CheckSuite events upon pushes to the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckSuiteFilter

\n

The filters that are available when fetching check suites.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (Int)

Filters the check suites created by this application ID.

\n\n\n\n\n\n\n\n\n\n\n\n

checkName (String)

Filters the check suites by this name.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nClearLabelsFromLabelableInput

\n

Autogenerated input type of ClearLabelsFromLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the labelable object to clear the labels from.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloneProjectInput

\n

Autogenerated input type of CloneProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

includeWorkflows (Boolean!)

Whether or not to clone the source project's workflows.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

The visibility of the project, defaults to false (private).

\n\n\n\n\n\n\n\n\n\n\n\n

sourceId (ID!)

The source project to clone.

\n\n\n\n\n\n\n\n\n\n\n\n

targetOwnerId (ID!)

The owner ID to create the project under.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloneTemplateRepositoryInput

\n

Autogenerated input type of CloneTemplateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

includeAllBranches (Boolean)

Whether to copy all branches from the template to the new repository. Defaults\nto copying only the default branch of the template.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner for the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the template repository.

\n\n\n\n\n\n\n\n\n\n\n\n

visibility (RepositoryVisibility!)

Indicates the repository's visibility level.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloseIssueInput

\n

Autogenerated input type of CloseIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

ID of the issue to be closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nClosePullRequestInput

\n

Autogenerated input type of ClosePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitAuthor

\n

Specifies an author for filtering Git commits.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

emails ([String!])

Email addresses to filter by. Commits authored by any of the specified email addresses will be returned.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID)

ID of a User to filter by. If non-null, only commits authored by this user\nwill be returned. This field takes precedence over emails.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitContributionOrder

\n

Ordering options for commit contribution connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (CommitContributionOrderField!)

The field by which to order commit contributions.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitMessage

\n

A message to include with a new commit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The body of the message.

\n\n\n\n\n\n\n\n\n\n\n\n

headline (String!)

The headline of the message.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommittableBranch

\n

A git ref for a commit to be appended to.

\n

The ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).

\n

The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.

\n

Examples

\n

Specify a branch using a global node ID:

\n
{ "id": "MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=" }\n
\n

Specify a branch using nameWithOwner and branch name:

\n
{\n  "nameWithOwner": "github/graphql-client",\n  "branchName": "main"\n}.\n
\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branchName (String)

The unqualified name of the branch to append the commit to.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID)

The Node ID of the Ref to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryNameWithOwner (String)

The nameWithOwner of the repository to commit to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nContributionOrder

\n

Ordering options for contribution connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nConvertProjectCardNoteToIssueInput

\n

Autogenerated input type of ConvertProjectCardNoteToIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The body of the newly created issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectCardId (ID!)

The ProjectCard ID to convert.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to create the issue in.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the newly created issue. Defaults to the card's note text.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nConvertPullRequestToDraftInput

\n

Autogenerated input type of ConvertPullRequestToDraft.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to convert to draft.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateBranchProtectionRuleInput

\n

Autogenerated input type of CreateBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowsDeletions (Boolean)

Can this branch be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

allowsForcePushes (Boolean)

Are force pushes allowed on this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

blocksCreations (Boolean)

Is branch creation a protected operation.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassForcePushActorIds ([ID!])

A list of User or Team IDs allowed to bypass force push targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassPullRequestActorIds ([ID!])

A list of User or Team IDs allowed to bypass pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissesStaleReviews (Boolean)

Will new commits pushed to matching branches dismiss pull request review approvals.

\n\n\n\n\n\n\n\n\n\n\n\n

isAdminEnforced (Boolean)

Can admins overwrite branch protection.

\n\n\n\n\n\n\n\n\n\n\n\n

pattern (String!)

The glob-like pattern used to determine matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

pushActorIds ([ID!])

A list of User, Team, or App IDs allowed to push to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The global relay id of the repository in which a new branch protection rule should be created in.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredApprovingReviewCount (Int)

Number of approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusCheckContexts ([String!])

List of required status check contexts that must pass for commits to be accepted to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusChecks ([RequiredStatusCheckInput!])

The list of required status checks.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresApprovingReviews (Boolean)

Are approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCodeOwnerReviews (Boolean)

Are reviews from code owners required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCommitSignatures (Boolean)

Are commits required to be signed.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresConversationResolution (Boolean)

Are conversations required to be resolved before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresLinearHistory (Boolean)

Are merge commits prohibited from being pushed to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStatusChecks (Boolean)

Are status checks required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStrictStatusChecks (Boolean)

Are branches required to be up to date before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsPushes (Boolean)

Is pushing to matching branches restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsReviewDismissals (Boolean)

Is dismissal of pull request reviews restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewDismissalActorIds ([ID!])

A list of User or Team IDs allowed to dismiss reviews on pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCheckRunInput

\n

Autogenerated input type of CreateCheckRun.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actions ([CheckRunAction!])

Possible further actions the integrator can perform, which a user may trigger.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

completedAt (DateTime)

The time that the check run finished.

\n\n\n\n\n\n\n\n\n\n\n\n

conclusion (CheckConclusionState)

The final conclusion of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

detailsUrl (URI)

The URL of the integrator's site that has the full details of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

externalId (String)

A reference for the run on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

headSha (GitObjectID!)

The SHA of the head commit.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

output (CheckRunOutput)

Descriptive details about the run.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

startedAt (DateTime)

The time that the check run began.

\n\n\n\n\n\n\n\n\n\n\n\n

status (RequestableCheckStatusState)

The current status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCheckSuiteInput

\n

Autogenerated input type of CreateCheckSuite.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

headSha (GitObjectID!)

The SHA of the head commit.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCommitOnBranchInput

\n

Autogenerated input type of CreateCommitOnBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branch (CommittableBranch!)

The Ref to be updated. Must be a branch.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID!)

The git commit oid expected at the head of the branch prior to the commit.

\n\n\n\n\n\n\n\n\n\n\n\n

fileChanges (FileChanges)

A description of changes to files in this commit.

\n\n\n\n\n\n\n\n\n\n\n\n

message (CommitMessage!)

The commit message the be included with the commit.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDeploymentInput

\n

Autogenerated input type of CreateDeployment.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateDeploymentInput is available under the Deployments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoMerge (Boolean)

Attempt to automatically merge the default branch into the requested ref, defaults to true.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

Short description of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

environment (String)

Name for the target deployment environment.

\n\n\n\n\n\n\n\n\n\n\n\n

payload (String)

JSON payload with extra information about the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The node ID of the ref to be deployed.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredContexts ([String!])

The status contexts to verify against commit status checks. To bypass required\ncontexts, pass an empty array. Defaults to all unique contexts.

\n\n\n\n\n\n\n\n\n\n\n\n

task (String)

Specifies a task to execute.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDeploymentStatusInput

\n

Autogenerated input type of CreateDeploymentStatus.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateDeploymentStatusInput is available under the Deployments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoInactive (Boolean)

Adds a new inactive status to all non-transient, non-production environment\ndeployments with the same repository and environment name as the created\nstatus's deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

deploymentId (ID!)

The node ID of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the status. Maximum length of 140 characters.

\n\n\n\n\n\n\n\n\n\n\n\n

environment (String)

If provided, updates the environment of the deploy. Otherwise, does not modify the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentUrl (String)

Sets the URL for accessing your environment.

\n\n\n\n\n\n\n\n\n\n\n\n

logUrl (String)

The log URL to associate with this status. This URL should contain\noutput to keep the user updated while the task is running or serve as\nhistorical information for what happened in the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

state (DeploymentStatusState!)

The state of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDiscussionInput

\n

Autogenerated input type of CreateDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The body of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

categoryId (ID!)

The id of the discussion category to associate with this discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The id of the repository on which to create the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateEnterpriseOrganizationInput

\n

Autogenerated input type of CreateEnterpriseOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

adminLogins ([String!]!)

The logins for the administrators of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

billingEmail (String!)

The email used for sending billing receipts.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise owning the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

profileName (String!)

The profile name of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateEnvironmentInput

\n

Autogenerated input type of CreateEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateIpAllowListEntryInput

\n

Autogenerated input type of CreateIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowListValue (String!)

An IP address or range of addresses in CIDR notation.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isActive (Boolean!)

Whether the IP allow list entry is active when an IP allow list is enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

An optional name for the IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner for which to create the new IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateIssueInput

\n

Autogenerated input type of CreateIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The Node ID for the user assignee for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body for the issue description.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueTemplate (String)

The name of an issue template in the repository, assigns labels and assignees from the template to the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title for the issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateLabelInput

\n

Autogenerated input type of CreateLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

color (String!)

A 6 character hex code, without the leading #, identifying the color of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A brief description of the label, such as its purpose.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateMigrationSourceInput

\n

Autogenerated input type of CreateMigrationSource.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

accessToken (String)

The Octoshift migration source access token.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

githubPat (String)

The GitHub personal access token of the user importing to the target repository.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The Octoshift migration source name.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that will own the Octoshift migration source.

\n\n\n\n\n\n\n\n\n\n\n\n

type (MigrationSourceType!)

The Octoshift migration source type.

\n\n\n\n\n\n\n\n\n\n\n\n

url (String!)

The Octoshift migration source URL.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateProjectInput

\n

Autogenerated input type of CreateProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of project.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The owner ID to create the project under.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryIds ([ID!])

A list of repository IDs to create as linked repositories for the project.

\n\n\n\n\n\n\n\n\n\n\n\n

template (ProjectTemplate)

The name of the GitHub-provided template.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreatePullRequestInput

\n

Autogenerated input type of CreatePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

baseRefName (String!)

The name of the branch you want your changes pulled into. This should be an existing branch\non the current repository. You cannot update the base branch on a pull request to point\nto another repository.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The contents of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

draft (Boolean)

Indicates whether this pull request should be a draft.

\n\n\n\n\n\n\n\n\n\n\n\n

headRefName (String!)

The name of the branch where your changes are implemented. For cross-repository pull requests\nin the same network, namespace head_ref_name with a user like this: username:branch.

\n\n\n\n\n\n\n\n\n\n\n\n

maintainerCanModify (Boolean)

Indicates whether maintainers can modify the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateRefInput

\n

Autogenerated input type of CreateRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The fully qualified name of the new Ref (ie: refs/heads/my_new_branch).

\n\n\n\n\n\n\n\n\n\n\n\n

oid (GitObjectID!)

The GitObjectID that the new Ref shall target. Must point to a commit.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the Repository to create the Ref in.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateRepositoryInput

\n

Autogenerated input type of CreateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

hasIssuesEnabled (Boolean)

Indicates if the repository should have the issues feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasWikiEnabled (Boolean)

Indicates if the repository should have the wiki feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

homepageUrl (URI)

The URL for a web page about this repository.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID)

The ID of the owner for the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

teamId (ID)

When an organization is specified as the owner, this ID identifies the team\nthat should be granted access to the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

template (Boolean)

Whether this repository should be marked as a template such that anyone who\ncan access it can create new repositories with the same files and directory structure.

\n\n\n\n\n\n\n\n\n\n\n\n

visibility (RepositoryVisibility!)

Indicates the repository's visibility level.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateSponsorsTierInput

\n

Autogenerated input type of CreateSponsorsTier.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

amount (Int!)

The value of the new tier in US dollars. Valid values: 1-12000.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String!)

A description of what this tier is, what perks sponsors might receive, what a sponsorship at this tier means for you, etc.

\n\n\n\n\n\n\n\n\n\n\n\n

isRecurring (Boolean)

Whether sponsorships using this tier should happen monthly/yearly or just once.

\n\n\n\n\n\n\n\n\n\n\n\n

publish (Boolean)

Whether to make the tier available immediately for sponsors to choose.\nDefaults to creating a draft tier that will not be publicly visible.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID)

Optional ID of the private repository that sponsors at this tier should gain\nread-only access to. Must be owned by an organization.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryName (String)

Optional name of the private repository that sponsors at this tier should gain\nread-only access to. Must be owned by an organization. Necessary if\nrepositoryOwnerLogin is given. Will be ignored if repositoryId is given.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryOwnerLogin (String)

Optional login of the organization owner of the private repository that\nsponsors at this tier should gain read-only access to. Necessary if\nrepositoryName is given. Will be ignored if repositoryId is given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who owns the GitHub Sponsors profile.\nDefaults to the current user if omitted and sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who owns the GitHub Sponsors profile.\nDefaults to the current user if omitted and sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

welcomeMessage (String)

Optional message new sponsors at this tier will receive.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateSponsorshipInput

\n

Autogenerated input type of CreateSponsorship.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

amount (Int)

The amount to pay to the sponsorable in US dollars. Required if a tierId is not specified. Valid values: 1-12000.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isRecurring (Boolean)

Whether the sponsorship should happen monthly/yearly or just this one time. Required if a tierId is not specified.

\n\n\n\n\n\n\n\n\n\n\n\n

privacyLevel (SponsorshipPrivacy)

Specify whether others should be able to see that the sponsor is sponsoring\nthe sponsorable. Public visibility still does not reveal which tier is used.

\n\n\n\n\n\n\n\n\n\n\n\n

receiveEmails (Boolean)

Whether the sponsor should receive email updates from the sponsorable.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorId (ID)

The ID of the user or organization who is acting as the sponsor, paying for\nthe sponsorship. Required if sponsorLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorLogin (String)

The username of the user or organization who is acting as the sponsor, paying\nfor the sponsorship. Required if sponsorId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who is receiving the sponsorship. Required if sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who is receiving the sponsorship. Required if sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

tierId (ID)

The ID of one of sponsorable's existing tiers to sponsor at. Required if amount is not specified.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateTeamDiscussionCommentInput

\n

Autogenerated input type of CreateTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The content of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The ID of the discussion to which the comment belongs.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateTeamDiscussionInput

\n

Autogenerated input type of CreateTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The content of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

private (Boolean)

If true, restricts the visibility of this discussion to team members and\norganization admins. If false or not specified, allows any organization member\nto view this discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

teamId (ID!)

The ID of the team to which the discussion belongs.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeclineTopicSuggestionInput

\n

Autogenerated input type of DeclineTopicSuggestion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the suggested topic.

\n\n\n\n\n\n\n\n\n\n\n\n

reason (TopicSuggestionDeclineReason!)

The reason why the suggested topic is declined.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteBranchProtectionRuleInput

\n

Autogenerated input type of DeleteBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branchProtectionRuleId (ID!)

The global relay id of the branch protection rule to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDeploymentInput

\n

Autogenerated input type of DeleteDeployment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the deployment to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDiscussionCommentInput

\n

Autogenerated input type of DeleteDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node id of the discussion comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDiscussionInput

\n

Autogenerated input type of DeleteDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The id of the discussion to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteEnvironmentInput

\n

Autogenerated input type of DeleteEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the environment to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIpAllowListEntryInput

\n

Autogenerated input type of DeleteIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ipAllowListEntryId (ID!)

The ID of the IP allow list entry to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIssueCommentInput

\n

Autogenerated input type of DeleteIssueComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIssueInput

\n

Autogenerated input type of DeleteIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteLabelInput

\n

Autogenerated input type of DeleteLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

DeleteLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the label to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePackageVersionInput

\n

Autogenerated input type of DeletePackageVersion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

packageVersionId (ID!)

The ID of the package version to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectCardInput

\n

Autogenerated input type of DeleteProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

cardId (ID!)

The id of the card to delete.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectColumnInput

\n

Autogenerated input type of DeleteProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectInput

\n

Autogenerated input type of DeleteProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Project ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectNextItemInput

\n

Autogenerated input type of DeleteProjectNextItem.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

itemId (ID!)

The ID of the item to be removed.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project from which the item should be removed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePullRequestReviewCommentInput

\n

Autogenerated input type of DeletePullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePullRequestReviewInput

\n

Autogenerated input type of DeletePullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteRefInput

\n

Autogenerated input type of DeleteRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The Node ID of the Ref to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteTeamDiscussionCommentInput

\n

Autogenerated input type of DeleteTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteTeamDiscussionInput

\n

Autogenerated input type of DeleteTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The discussion ID to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteVerifiableDomainInput

\n

Autogenerated input type of DeleteVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeploymentOrder

\n

Ordering options for deployment connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (DeploymentOrderField!)

The field to order deployments by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDisablePullRequestAutoMergeInput

\n

Autogenerated input type of DisablePullRequestAutoMerge.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to disable auto merge on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDiscussionOrder

\n

Ways in which lists of discussions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order discussions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (DiscussionOrderField!)

The field by which to order discussions.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDismissPullRequestReviewInput

\n

Autogenerated input type of DismissPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String!)

The contents of the pull request review dismissal message.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDismissRepositoryVulnerabilityAlertInput

\n

Autogenerated input type of DismissRepositoryVulnerabilityAlert.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissReason (DismissReason!)

The reason the Dependabot alert is being dismissed.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryVulnerabilityAlertId (ID!)

The Dependabot alert ID to dismiss.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDraftPullRequestReviewComment

\n

Specifies a review comment to be left with a Pull Request Review.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the comment to leave.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int!)

Position in the file to leave a comment on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDraftPullRequestReviewThread

\n

Specifies a review comment thread to be left with a Pull Request Review.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the comment to leave.

\n\n\n\n\n\n\n\n\n\n\n\n

line (Int!)

The line of the blob to which the thread refers. The end of the line range for multi-line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

side (DiffSide)

The side of the diff on which the line resides. For multi-line comments, this is the side for the end of the line range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int)

The first line of the range to which the comment refers.

\n\n\n\n\n\n\n\n\n\n\n\n

startSide (DiffSide)

The side of the diff on which the start line resides.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnablePullRequestAutoMergeInput

\n

Autogenerated input type of EnablePullRequestAutoMerge.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this merge.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitBody (String)

Commit body to use for the commit when the PR is mergable; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

commitHeadline (String)

Commit headline to use for the commit when the PR is mergable; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

mergeMethod (PullRequestMergeMethod)

The merge method to use. If omitted, defaults to 'MERGE'.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to enable auto-merge on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseAdministratorInvitationOrder

\n

Ordering options for enterprise administrator invitation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseAdministratorInvitationOrderField!)

The field to order enterprise administrator invitations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseMemberOrder

\n

Ordering options for enterprise member connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseMemberOrderField!)

The field to order enterprise members by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerInstallationOrder

\n

Ordering options for Enterprise Server installation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerInstallationOrderField!)

The field to order Enterprise Server installations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountEmailOrder

\n

Ordering options for Enterprise Server user account email connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountEmailOrderField!)

The field to order emails by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountOrder

\n

Ordering options for Enterprise Server user account connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountOrderField!)

The field to order user accounts by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountsUploadOrder

\n

Ordering options for Enterprise Server user accounts upload connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountsUploadOrderField!)

The field to order user accounts uploads by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileAddition

\n

A command to add a file at the given path with the given contents as part of a\ncommit. Any existing file at that that path will be replaced.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

contents (Base64String!)

The base64 encoded contents of the file.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path in the repository where the file will be located.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileChanges

\n

A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file additions and zero or more\nfile deletions.

\n

Both fields are optional; omitting both will produce a commit with no\nfile changes.

\n

deletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.

\n

path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.

\n

Encoding

\n

File contents must be provided in full for each FileAddition.

\n

The contents of a FileAddition must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.

\n

The encoded contents may be binary.

\n

For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (\\n or \\r\\n), and that all files end\nwith a newline.

\n

Modeling file changes

\n

Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:

\n
    \n
  1. \n

    New file addition: create file hello world\\n at path docs/README.txt:

    \n

    {\n"additions" [\n{\n"path": "docs/README.txt",\n"contents": base64encode("hello world\\n")\n}\n]\n}

    \n
    2. \n
  2. \n

    Existing file modification: change existing docs/README.txt to have new\ncontent new content here\\n:

    \n
    {\n  "additions" [\n    {\n      "path": "docs/README.txt",\n      "contents": base64encode("new content here\\n")\n    }\n  ]\n}\n
    \n
    3. \n
  3. \n

    Existing file deletion: remove existing file docs/README.txt.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt"\n    }\n  ]\n}\n
    \n
    4. \n
  4. \n

    File rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt",\n    }\n  ],\n  "additions" [\n    {\n      "path": "newdocs/README.txt",\n      "contents": base64encode("hello world\\n")\n    }\n  ]\n}\n
    \n
    5. \n
  5. \n

    File rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt",\n    }\n  ],\n  "additions" [\n    {\n      "path": "newdocs/README.txt",\n      "contents": base64encode("new contents\\n")\n    }\n  ]\n}.\n
    \n
    6. \n
\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

additions ([FileAddition!])

File to add or change.

\n\n\n\n\n\n\n\n\n\n\n\n

deletions ([FileDeletion!])

Files to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileDeletion

\n

A command to delete the file at the given path as part of a commit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n
NameDescription

path (String!)

The path to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFollowOrganizationInput

\n

Autogenerated input type of FollowOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

ID of the organization to follow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFollowUserInput

\n

Autogenerated input type of FollowUser.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

ID of the user to follow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGistOrder

\n

Ordering options for gist connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (GistOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGrantEnterpriseOrganizationsMigratorRoleInput

\n

Autogenerated input type of GrantEnterpriseOrganizationsMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which all organizations managed by it will be granted the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to grant the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGrantMigratorRoleInput

\n

Autogenerated input type of GrantMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actor (String!)

The user login or Team slug to grant the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

actorType (ActorType!)

Specifies the type of the actor, can be either USER or TEAM.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization that the user/team belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nImportProjectInput

\n

Autogenerated input type of ImportProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of Project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnImports ([ProjectColumnImport!]!)

A list of columns containing issues and pull requests.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of Project.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerName (String!)

The name of the Organization or User to create the Project under.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Whether the Project is public or not.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nInviteEnterpriseAdminInput

\n

Autogenerated input type of InviteEnterpriseAdmin.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

email (String)

The email of the person to invite as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which you want to invite an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

invitee (String)

The login of a user to invite as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

role (EnterpriseAdministratorRole)

The role of the administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIpAllowListEntryOrder

\n

Ordering options for IP allow list entry connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IpAllowListEntryOrderField!)

The field to order IP allow list entries by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueCommentOrder

\n

Ways in which lists of issue comments can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order issue comments by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IssueCommentOrderField!)

The field in which to order issue comments by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueFilters

\n

Ways in which to filter lists of issues.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignee (String)

List issues assigned to given name. Pass in null for issues with no assigned\nuser, and * for issues assigned to any user.

\n\n\n\n\n\n\n\n\n\n\n\n

createdBy (String)

List issues created by given name.

\n\n\n\n\n\n\n\n\n\n\n\n

labels ([String!])

List issues where the list of label names exist on the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

mentioned (String)

List issues where the given name is mentioned in the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestone (String)

List issues by given milestone argument. If an string representation of an\ninteger is passed, it should refer to a milestone by its database ID. Pass in\nnull for issues with no milestone, and * for issues that are assigned to any milestone.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneNumber (String)

List issues by given milestone argument. If an string representation of an\ninteger is passed, it should refer to a milestone by its number field. Pass in\nnull for issues with no milestone, and * for issues that are assigned to any milestone.

\n\n\n\n\n\n\n\n\n\n\n\n

since (DateTime)

List issues that have been updated at or after the given date.

\n\n\n\n\n\n\n\n\n\n\n\n

states ([IssueState!])

List issues filtered by the list of states given.

\n\n\n\n\n\n\n\n\n\n\n\n

viewerSubscribed (Boolean)

List issues subscribed to by viewer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueOrder

\n

Ways in which lists of issues can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order issues by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IssueOrderField!)

The field in which to order issues by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLabelOrder

\n

Ways in which lists of labels can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order labels by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (LabelOrderField!)

The field in which to order labels by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLanguageOrder

\n

Ordering options for language connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (LanguageOrderField!)

The field to order languages by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLinkRepositoryToProjectInput

\n

Autogenerated input type of LinkRepositoryToProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to link to a Repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the Repository to link to a Project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLockLockableInput

\n

Autogenerated input type of LockLockable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

lockReason (LockReason)

A reason for why the item will be locked.

\n\n\n\n\n\n\n\n\n\n\n\n

lockableId (ID!)

ID of the item to be locked.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkDiscussionCommentAsAnswerInput

\n

Autogenerated input type of MarkDiscussionCommentAsAnswer.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion comment to mark as an answer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkFileAsViewedInput

\n

Autogenerated input type of MarkFileAsViewed.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to mark as viewed.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkPullRequestReadyForReviewInput

\n

Autogenerated input type of MarkPullRequestReadyForReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be marked as ready for review.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMergeBranchInput

\n

Autogenerated input type of MergeBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this commit.

\n\n\n\n\n\n\n\n\n\n\n\n

base (String!)

The name of the base branch that the provided head will be merged into.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitMessage (String)

Message to use for the merge commit. If omitted, a default will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

head (String!)

The head to merge into the base branch. This can be a branch name or a commit GitObjectID.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the Repository containing the base branch that will be modified.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMergePullRequestInput

\n

Autogenerated input type of MergePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this merge.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitBody (String)

Commit body to use for the merge commit; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

commitHeadline (String)

Commit headline to use for the merge commit; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID)

OID that the pull request head ref must match to allow merge; if omitted, no check is performed.

\n\n\n\n\n\n\n\n\n\n\n\n

mergeMethod (PullRequestMergeMethod)

The merge method to use. If omitted, defaults to 'MERGE'.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be merged.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMilestoneOrder

\n

Ordering options for milestone connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (MilestoneOrderField!)

The field to order milestones by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMinimizeCommentInput

\n

Autogenerated input type of MinimizeComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

classifier (ReportedContentClassifiers!)

The classification of comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMoveProjectCardInput

\n

Autogenerated input type of MoveProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterCardId (ID)

Place the new card after the card with this id. Pass null to place it at the top.

\n\n\n\n\n\n\n\n\n\n\n\n

cardId (ID!)

The id of the card to move.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to move it into.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMoveProjectColumnInput

\n

Autogenerated input type of MoveProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterColumnId (ID)

Place the new column after the column with this id. Pass null to place it at the front.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to move.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nOrgEnterpriseOwnerOrder

\n

Ordering options for an organization's enterprise owner connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (OrgEnterpriseOwnerOrderField!)

The field to order enterprise owners by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nOrganizationOrder

\n

Ordering options for organization connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (OrganizationOrderField!)

The field to order organizations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPackageFileOrder

\n

Ways in which lists of package files can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The direction in which to order package files by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PackageFileOrderField)

The field in which to order package files by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPackageOrder

\n

Ways in which lists of packages can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The direction in which to order packages by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PackageOrderField)

The field in which to order packages by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPackageVersionOrder

\n

Ways in which lists of package versions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The direction in which to order package versions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PackageVersionOrderField)

The field in which to order package versions by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPinIssueInput

\n

Autogenerated input type of PinIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to be pinned.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectCardImport

\n

An issue or PR and its owning repository to be used in a project card.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

number (Int!)

The issue or pull request number.

\n\n\n\n\n\n\n\n\n\n\n\n

repository (String!)

Repository name with owner (owner/repository).

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectColumnImport

\n

A project column and a list of its issues and PRs.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

columnName (String!)

The name of the column.

\n\n\n\n\n\n\n\n\n\n\n\n

issues ([ProjectCardImport!])

A list of issues and pull requests in the column.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int!)

The position of the column, starting from 0.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectOrder

\n

Ways in which lists of projects can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order projects by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ProjectOrderField!)

The field in which to order projects by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPullRequestOrder

\n

Ways in which lists of issues can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order pull requests by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PullRequestOrderField!)

The field in which to order pull requests by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReactionOrder

\n

Ways in which lists of reactions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order reactions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ReactionOrderField!)

The field in which to order reactions by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRefOrder

\n

Ways in which lists of git refs can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order refs by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RefOrderField!)

The field in which to order refs by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRefUpdate

\n

A ref update.

\n
\n\n
\n \n
\n

Preview notice

\n

RefUpdate is available under the Update refs preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterOid (GitObjectID!)

The value this ref should be updated to.

\n\n\n\n\n\n\n\n\n\n\n\n

beforeOid (GitObjectID)

The value this ref needs to point to before the update.

\n\n\n\n\n\n\n\n\n\n\n\n

force (Boolean)

Force a non fast-forward update.

\n\n\n\n\n\n\n\n\n\n\n\n

name (GitRefname!)

The fully qualified name of the ref to be update. For example refs/heads/branch-name.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRegenerateEnterpriseIdentityProviderRecoveryCodesInput

\n

Autogenerated input type of RegenerateEnterpriseIdentityProviderRecoveryCodes.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set an identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRegenerateVerifiableDomainTokenInput

\n

Autogenerated input type of RegenerateVerifiableDomainToken.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to regenerate the verification token of.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRejectDeploymentsInput

\n

Autogenerated input type of RejectDeployments.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comment (String)

Optional comment for rejecting deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentIds ([ID!]!)

The ids of environments to reject deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

workflowRunId (ID!)

The node ID of the workflow run containing the pending deployments.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReleaseOrder

\n

Ways in which lists of releases can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order releases by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ReleaseOrderField!)

The field in which to order releases by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveAssigneesFromAssignableInput

\n

Autogenerated input type of RemoveAssigneesFromAssignable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignableId (ID!)

The id of the assignable object to remove assignees from.

\n\n\n\n\n\n\n\n\n\n\n\n

assigneeIds ([ID!]!)

The id of users to remove as assignees.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseAdminInput

\n

Autogenerated input type of RemoveEnterpriseAdmin.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The Enterprise ID from which to remove the administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to remove as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseIdentityProviderInput

\n

Autogenerated input type of RemoveEnterpriseIdentityProvider.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise from which to remove the identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseOrganizationInput

\n

Autogenerated input type of RemoveEnterpriseOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise from which the organization should be removed.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to remove from the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseSupportEntitlementInput

\n

Autogenerated input type of RemoveEnterpriseSupportEntitlement.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the admin belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of a member who will lose the support entitlement.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveLabelsFromLabelableInput

\n

Autogenerated input type of RemoveLabelsFromLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!]!)

The ids of labels to remove.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the Labelable to remove labels from.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveOutsideCollaboratorInput

\n

Autogenerated input type of RemoveOutsideCollaborator.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to remove the outside collaborator from.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

The ID of the outside collaborator to remove.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveReactionInput

\n

Autogenerated input type of RemoveReaction.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

content (ReactionContent!)

The name of the emoji reaction to remove.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveStarInput

\n

Autogenerated input type of RemoveStar.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

starrableId (ID!)

The Starrable ID to unstar.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveUpvoteInput

\n

Autogenerated input type of RemoveUpvote.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the discussion or comment to remove upvote.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReopenIssueInput

\n

Autogenerated input type of ReopenIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

ID of the issue to be opened.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReopenPullRequestInput

\n

Autogenerated input type of ReopenPullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be reopened.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryInvitationOrder

\n

Ordering options for repository invitation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryInvitationOrderField!)

The field to order repository invitations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryMigrationOrder

\n

Ordering options for repository migrations.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (RepositoryMigrationOrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryMigrationOrderField!)

The field to order repository migrations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryOrder

\n

Ordering options for repository connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRequestReviewsInput

\n

Autogenerated input type of RequestReviews.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

teamIds ([ID!])

The Node IDs of the team to request.

\n\n\n\n\n\n\n\n\n\n\n\n

union (Boolean)

Add users to the set rather than replace.

\n\n\n\n\n\n\n\n\n\n\n\n

userIds ([ID!])

The Node IDs of the user to request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRequiredStatusCheckInput

\n

Specifies the attributes for a new or updated required status check.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (ID)

The ID of the App that must set the status in order for it to be accepted.\nOmit this value to use whichever app has recently been setting this status, or\nuse "any" to allow any app to set the status.

\n\n\n\n\n\n\n\n\n\n\n\n

context (String!)

Status check context that must pass for commits to be accepted to the matching branch.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRerequestCheckSuiteInput

\n

Autogenerated input type of RerequestCheckSuite.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

checkSuiteId (ID!)

The Node ID of the check suite.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nResolveReviewThreadInput

\n

Autogenerated input type of ResolveReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

threadId (ID!)

The ID of the thread to resolve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRevokeEnterpriseOrganizationsMigratorRoleInput

\n

Autogenerated input type of RevokeEnterpriseOrganizationsMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which all organizations managed by it will be granted the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to revoke the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRevokeMigratorRoleInput

\n

Autogenerated input type of RevokeMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actor (String!)

The user login or Team slug to revoke the migrator role from.

\n\n\n\n\n\n\n\n\n\n\n\n

actorType (ActorType!)

Specifies the type of the actor, can be either USER or TEAM.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization that the user/team belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSavedReplyOrder

\n

Ordering options for saved reply connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SavedReplyOrderField!)

The field to order saved replies by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSecurityAdvisoryIdentifierFilter

\n

An advisory identifier to filter results on.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

type (SecurityAdvisoryIdentifierType!)

The identifier type.

\n\n\n\n\n\n\n\n\n\n\n\n

value (String!)

The identifier string. Supports exact or partial matching.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSecurityAdvisoryOrder

\n

Ordering options for security advisory connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SecurityAdvisoryOrderField!)

The field to order security advisories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSecurityVulnerabilityOrder

\n

Ordering options for security vulnerability connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SecurityVulnerabilityOrderField!)

The field to order security vulnerabilities by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetEnterpriseIdentityProviderInput

\n

Autogenerated input type of SetEnterpriseIdentityProvider.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

digestMethod (SamlDigestAlgorithm!)

The digest algorithm used to sign SAML requests for the identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set an identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

idpCertificate (String!)

The x509 certificate used by the identity provider to sign assertions and responses.

\n\n\n\n\n\n\n\n\n\n\n\n

issuer (String)

The Issuer Entity ID for the SAML identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

signatureMethod (SamlSignatureAlgorithm!)

The signature algorithm used to sign SAML requests for the identity provider.

\n\n\n\n\n\n\n\n\n\n\n\n

ssoUrl (URI!)

The URL endpoint for the identity provider's SAML SSO.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetOrganizationInteractionLimitInput

\n

Autogenerated input type of SetOrganizationInteractionLimit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expiry (RepositoryInteractionLimitExpiry)

When this limit should expire.

\n\n\n\n\n\n\n\n\n\n\n\n

limit (RepositoryInteractionLimit!)

The limit to set.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to set a limit for.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetRepositoryInteractionLimitInput

\n

Autogenerated input type of SetRepositoryInteractionLimit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expiry (RepositoryInteractionLimitExpiry)

When this limit should expire.

\n\n\n\n\n\n\n\n\n\n\n\n

limit (RepositoryInteractionLimit!)

The limit to set.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to set a limit for.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSetUserInteractionLimitInput

\n

Autogenerated input type of SetUserInteractionLimit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expiry (RepositoryInteractionLimitExpiry)

When this limit should expire.

\n\n\n\n\n\n\n\n\n\n\n\n

limit (RepositoryInteractionLimit!)

The limit to set.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

The ID of the user to set a limit for.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorOrder

\n

Ordering options for connections to get sponsor entities for GitHub Sponsors.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorOrderField!)

The field to order sponsor entities by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorableOrder

\n

Ordering options for connections to get sponsorable entities for GitHub Sponsors.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorableOrderField!)

The field to order sponsorable entities by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorsActivityOrder

\n

Ordering options for GitHub Sponsors activity connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorsActivityOrderField!)

The field to order activity by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorsTierOrder

\n

Ordering options for Sponsors tiers connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorsTierOrderField!)

The field to order tiers by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorshipNewsletterOrder

\n

Ordering options for sponsorship newsletter connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorshipNewsletterOrderField!)

The field to order sponsorship newsletters by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSponsorshipOrder

\n

Ordering options for sponsorship connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SponsorshipOrderField!)

The field to order sponsorship by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nStarOrder

\n

Ways in which star connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (StarOrderField!)

The field in which to order nodes by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nStartRepositoryMigrationInput

\n

Autogenerated input type of StartRepositoryMigration.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

accessToken (String)

The Octoshift migration source access token.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

continueOnError (Boolean)

Whether to continue the migration on error.

\n\n\n\n\n\n\n\n\n\n\n\n

gitArchiveUrl (String)

The signed URL to access the user-uploaded git archive.

\n\n\n\n\n\n\n\n\n\n\n\n

githubPat (String)

The GitHub personal access token of the user importing to the target repository.

\n\n\n\n\n\n\n\n\n\n\n\n

metadataArchiveUrl (String)

The signed URL to access the user-uploaded metadata archive.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that will own the imported repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryName (String!)

The name of the imported repository.

\n\n\n\n\n\n\n\n\n\n\n\n

skipReleases (Boolean)

Whether to skip migrating releases for the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

sourceId (ID!)

The ID of the Octoshift migration source.

\n\n\n\n\n\n\n\n\n\n\n\n

sourceRepositoryUrl (URI!)

The Octoshift migration source repository URL.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSubmitPullRequestReviewInput

\n

Autogenerated input type of SubmitPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The text field to set on the Pull Request Review.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

event (PullRequestReviewEvent!)

The event to send to the Pull Request Review.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The Pull Request ID to submit any pending reviews.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Pull Request Review ID to submit.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamDiscussionCommentOrder

\n

Ways in which team discussion comment connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamDiscussionCommentOrderField!)

The field by which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamDiscussionOrder

\n

Ways in which team discussion connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamDiscussionOrderField!)

The field by which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamMemberOrder

\n

Ordering options for team member connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamMemberOrderField!)

The field to order team members by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamOrder

\n

Ways in which team connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamOrderField!)

The field in which to order nodes by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamRepositoryOrder

\n

Ordering options for team repository connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamRepositoryOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTransferIssueInput

\n

Autogenerated input type of TransferIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The Node ID of the issue to be transferred.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository the issue should be transferred to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnarchiveRepositoryInput

\n

Autogenerated input type of UnarchiveRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to unarchive.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnfollowOrganizationInput

\n

Autogenerated input type of UnfollowOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

ID of the organization to unfollow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnfollowUserInput

\n

Autogenerated input type of UnfollowUser.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

ID of the user to unfollow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnlinkRepositoryFromProjectInput

\n

Autogenerated input type of UnlinkRepositoryFromProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project linked to the Repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the Repository linked to the Project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnlockLockableInput

\n

Autogenerated input type of UnlockLockable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

lockableId (ID!)

ID of the item to be unlocked.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkDiscussionCommentAsAnswerInput

\n

Autogenerated input type of UnmarkDiscussionCommentAsAnswer.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion comment to unmark as an answer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkFileAsViewedInput

\n

Autogenerated input type of UnmarkFileAsViewed.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to mark as unviewed.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkIssueAsDuplicateInput

\n

Autogenerated input type of UnmarkIssueAsDuplicate.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

canonicalId (ID!)

ID of the issue or pull request currently considered canonical/authoritative/original.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

duplicateId (ID!)

ID of the issue or pull request currently marked as a duplicate.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnminimizeCommentInput

\n

Autogenerated input type of UnminimizeComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnpinIssueInput

\n

Autogenerated input type of UnpinIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to be unpinned.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnresolveReviewThreadInput

\n

Autogenerated input type of UnresolveReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

threadId (ID!)

The ID of the thread to unresolve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateBranchProtectionRuleInput

\n

Autogenerated input type of UpdateBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowsDeletions (Boolean)

Can this branch be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

allowsForcePushes (Boolean)

Are force pushes allowed on this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

blocksCreations (Boolean)

Is branch creation a protected operation.

\n\n\n\n\n\n\n\n\n\n\n\n

branchProtectionRuleId (ID!)

The global relay id of the branch protection rule to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassForcePushActorIds ([ID!])

A list of User or Team IDs allowed to bypass force push targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassPullRequestActorIds ([ID!])

A list of User or Team IDs allowed to bypass pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissesStaleReviews (Boolean)

Will new commits pushed to matching branches dismiss pull request review approvals.

\n\n\n\n\n\n\n\n\n\n\n\n

isAdminEnforced (Boolean)

Can admins overwrite branch protection.

\n\n\n\n\n\n\n\n\n\n\n\n

pattern (String)

The glob-like pattern used to determine matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

pushActorIds ([ID!])

A list of User, Team, or App IDs allowed to push to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredApprovingReviewCount (Int)

Number of approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusCheckContexts ([String!])

List of required status check contexts that must pass for commits to be accepted to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusChecks ([RequiredStatusCheckInput!])

The list of required status checks.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresApprovingReviews (Boolean)

Are approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCodeOwnerReviews (Boolean)

Are reviews from code owners required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCommitSignatures (Boolean)

Are commits required to be signed.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresConversationResolution (Boolean)

Are conversations required to be resolved before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresLinearHistory (Boolean)

Are merge commits prohibited from being pushed to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStatusChecks (Boolean)

Are status checks required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStrictStatusChecks (Boolean)

Are branches required to be up to date before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsPushes (Boolean)

Is pushing to matching branches restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsReviewDismissals (Boolean)

Is dismissal of pull request reviews restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewDismissalActorIds ([ID!])

A list of User or Team IDs allowed to dismiss reviews on pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateCheckRunInput

\n

Autogenerated input type of UpdateCheckRun.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actions ([CheckRunAction!])

Possible further actions the integrator can perform, which a user may trigger.

\n\n\n\n\n\n\n\n\n\n\n\n

checkRunId (ID!)

The node of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

completedAt (DateTime)

The time that the check run finished.

\n\n\n\n\n\n\n\n\n\n\n\n

conclusion (CheckConclusionState)

The final conclusion of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

detailsUrl (URI)

The URL of the integrator's site that has the full details of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

externalId (String)

A reference for the run on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

output (CheckRunOutput)

Descriptive details about the run.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

startedAt (DateTime)

The time that the check run began.

\n\n\n\n\n\n\n\n\n\n\n\n

status (RequestableCheckStatusState)

The current status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateCheckSuitePreferencesInput

\n

Autogenerated input type of UpdateCheckSuitePreferences.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoTriggerPreferences ([CheckSuiteAutoTriggerPreference!]!)

The check suite preferences to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateDiscussionCommentInput

\n

Autogenerated input type of UpdateDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The new contents of the comment body.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commentId (ID!)

The Node ID of the discussion comment to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateDiscussionInput

\n

Autogenerated input type of UpdateDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The new contents of the discussion body.

\n\n\n\n\n\n\n\n\n\n\n\n

categoryId (ID)

The Node ID of a discussion category within the same repository to change this discussion to.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The Node ID of the discussion to update.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The new discussion title.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseAdministratorRoleInput

\n

Autogenerated input type of UpdateEnterpriseAdministratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the admin belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of a administrator whose role is being changed.

\n\n\n\n\n\n\n\n\n\n\n\n

role (EnterpriseAdministratorRole!)

The new role for the Enterprise administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseAllowPrivateRepositoryForkingSettingInput

\n

Autogenerated input type of UpdateEnterpriseAllowPrivateRepositoryForkingSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the allow private repository forking setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the allow private repository forking setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseDefaultRepositoryPermissionSettingInput

\n

Autogenerated input type of UpdateEnterpriseDefaultRepositoryPermissionSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the base repository permission setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseDefaultRepositoryPermissionSettingValue!)

The value for the base repository permission setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanChangeRepositoryVisibilitySettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanChangeRepositoryVisibilitySetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can change repository visibility setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can change repository visibility setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanCreateRepositoriesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanCreateRepositoriesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can create repositories setting.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreateInternalRepositories (Boolean)

Allow members to create internal repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreatePrivateRepositories (Boolean)

Allow members to create private repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreatePublicRepositories (Boolean)

Allow members to create public repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreateRepositoriesPolicyEnabled (Boolean)

When false, allow member organizations to set their own repository creation member privileges.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseMembersCanCreateRepositoriesSettingValue)

Value for the members can create repositories setting on the enterprise. This\nor the granular public/private/internal allowed fields (but not both) must be provided.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanDeleteIssuesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanDeleteIssuesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can delete issues setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can delete issues setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanDeleteRepositoriesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanDeleteRepositoriesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can delete repositories setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can delete repositories setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanInviteCollaboratorsSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanInviteCollaboratorsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can invite collaborators setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can invite collaborators setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanMakePurchasesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanMakePurchasesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can make purchases setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseMembersCanMakePurchasesSettingValue!)

The value for the members can make purchases setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanUpdateProtectedBranchesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanUpdateProtectedBranchesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can update protected branches setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can update protected branches setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanViewDependencyInsightsSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanViewDependencyInsightsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can view dependency insights setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can view dependency insights setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseOrganizationProjectsSettingInput

\n

Autogenerated input type of UpdateEnterpriseOrganizationProjectsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the organization projects setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the organization projects setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseOwnerOrganizationRoleInput

\n

Autogenerated input type of UpdateEnterpriseOwnerOrganizationRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the owner belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization for membership change.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationRole (RoleInOrganization!)

The role to assume in the organization.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseProfileInput

\n

Autogenerated input type of UpdateEnterpriseProfile.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

The description of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The Enterprise ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n

location (String)

The location of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

websiteUrl (String)

The URL of the enterprise's website.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseRepositoryProjectsSettingInput

\n

Autogenerated input type of UpdateEnterpriseRepositoryProjectsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the repository projects setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the repository projects setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseTeamDiscussionsSettingInput

\n

Autogenerated input type of UpdateEnterpriseTeamDiscussionsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the team discussions setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the team discussions setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseTwoFactorAuthenticationRequiredSettingInput

\n

Autogenerated input type of UpdateEnterpriseTwoFactorAuthenticationRequiredSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the two factor authentication required setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledSettingValue!)

The value for the two factor authentication required setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnvironmentInput

\n

Autogenerated input type of UpdateEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentId (ID!)

The node ID of the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewers ([ID!])

The ids of users or teams that can approve deployments to this environment.

\n\n\n\n\n\n\n\n\n\n\n\n

waitTimer (Int)

The wait timer in minutes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListEnabledSettingInput

\n

Autogenerated input type of UpdateIpAllowListEnabledSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner on which to set the IP allow list enabled setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (IpAllowListEnabledSettingValue!)

The value for the IP allow list enabled setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListEntryInput

\n

Autogenerated input type of UpdateIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowListValue (String!)

An IP address or range of addresses in CIDR notation.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ipAllowListEntryId (ID!)

The ID of the IP allow list entry to update.

\n\n\n\n\n\n\n\n\n\n\n\n

isActive (Boolean!)

Whether the IP allow list entry is active when an IP allow list is enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

An optional name for the IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListForInstalledAppsEnabledSettingInput

\n

Autogenerated input type of UpdateIpAllowListForInstalledAppsEnabledSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (IpAllowListForInstalledAppsEnabledSettingValue!)

The value for the IP allow list configuration for installed GitHub Apps setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIssueCommentInput

\n

Autogenerated input type of UpdateIssueComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The updated text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the IssueComment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIssueInput

\n

Autogenerated input type of UpdateIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

An array of Node IDs of users for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body for the issue description.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the Issue to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

state (IssueState)

The desired issue state.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title for the issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateLabelInput

\n

Autogenerated input type of UpdateLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

color (String)

A 6 character hex code, without the leading #, identifying the updated color of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A brief description of the label, such as its purpose.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the label to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The updated name of the label.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateNotificationRestrictionSettingInput

\n

Autogenerated input type of UpdateNotificationRestrictionSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner on which to set the restrict notifications setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (NotificationRestrictionSettingValue!)

The value for the restrict notifications setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateOrganizationAllowPrivateRepositoryForkingSettingInput

\n

Autogenerated input type of UpdateOrganizationAllowPrivateRepositoryForkingSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

forkingEnabled (Boolean!)

Enable forking of private repositories in the organization?.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization on which to set the allow private repository forking setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectCardInput

\n

Autogenerated input type of UpdateProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isArchived (Boolean)

Whether or not the ProjectCard should be archived.

\n\n\n\n\n\n\n\n\n\n\n\n

note (String)

The note of ProjectCard.

\n\n\n\n\n\n\n\n\n\n\n\n

projectCardId (ID!)

The ProjectCard ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectColumnInput

\n

Autogenerated input type of UpdateProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of project column.

\n\n\n\n\n\n\n\n\n\n\n\n

projectColumnId (ID!)

The ProjectColumn ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectDraftIssueInput

\n

Autogenerated input type of UpdateProjectDraftIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The IDs of the assignees of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

draftIssueId (ID!)

The ID of the draft issue to update.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the draft issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectInput

\n

Autogenerated input type of UpdateProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of project.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Project ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Whether the project is public or not.

\n\n\n\n\n\n\n\n\n\n\n\n

state (ProjectState)

Whether the project is open or closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectNextInput

\n

Autogenerated input type of UpdateProjectNext.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

closed (Boolean)

Set the project to closed or open.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

Set the readme description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to update.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Set the project to public or private.

\n\n\n\n\n\n\n\n\n\n\n\n

shortDescription (String)

Set the short description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

Set the title of the project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectNextItemFieldInput

\n

Autogenerated input type of UpdateProjectNextItemField.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

fieldId (ID)

The id of the field to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

itemId (ID!)

The id of the item to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project.

\n\n\n\n\n\n\n\n\n\n\n\n

value (String!)

The value which will be set on the field.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestBranchInput

\n

Autogenerated input type of UpdatePullRequestBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID)

The head ref oid for the upstream branch.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestInput

\n

Autogenerated input type of UpdatePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

An array of Node IDs of users for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

baseRefName (String)

The name of the branch you want your changes pulled into. This should be an existing branch\non the current repository.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The contents of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

maintainerCanModify (Boolean)

Indicates whether maintainers can modify the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

state (PullRequestUpdateState)

The target state of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestReviewCommentInput

\n

Autogenerated input type of UpdatePullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewCommentId (ID!)

The Node ID of the comment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestReviewInput

\n

Autogenerated input type of UpdatePullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the pull request review body.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRefInput

\n

Autogenerated input type of UpdateRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

force (Boolean)

Permit updates of branch Refs that are not fast-forwards?.

\n\n\n\n\n\n\n\n\n\n\n\n

oid (GitObjectID!)

The GitObjectID that the Ref shall be updated to target.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The Node ID of the Ref to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRefsInput

\n

Autogenerated input type of UpdateRefs.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateRefsInput is available under the Update refs preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

refUpdates ([RefUpdate!]!)

A list of ref updates.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRepositoryInput

\n

Autogenerated input type of UpdateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A new description for the repository. Pass an empty string to erase the existing description.

\n\n\n\n\n\n\n\n\n\n\n\n

hasIssuesEnabled (Boolean)

Indicates if the repository should have the issues feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasProjectsEnabled (Boolean)

Indicates if the repository should have the project boards feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasWikiEnabled (Boolean)

Indicates if the repository should have the wiki feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

homepageUrl (URI)

The URL for a web page about this repository. Pass an empty string to erase the existing URL.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The new name of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to update.

\n\n\n\n\n\n\n\n\n\n\n\n

template (Boolean)

Whether this repository should be marked as a template such that anyone who\ncan access it can create new repositories with the same files and directory structure.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateSponsorshipPreferencesInput

\n

Autogenerated input type of UpdateSponsorshipPreferences.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

privacyLevel (SponsorshipPrivacy)

Specify whether others should be able to see that the sponsor is sponsoring\nthe sponsorable. Public visibility still does not reveal which tier is used.

\n\n\n\n\n\n\n\n\n\n\n\n

receiveEmails (Boolean)

Whether the sponsor should receive email updates from the sponsorable.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorId (ID)

The ID of the user or organization who is acting as the sponsor, paying for\nthe sponsorship. Required if sponsorLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorLogin (String)

The username of the user or organization who is acting as the sponsor, paying\nfor the sponsorship. Required if sponsorId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableId (ID)

The ID of the user or organization who is receiving the sponsorship. Required if sponsorableLogin is not given.

\n\n\n\n\n\n\n\n\n\n\n\n

sponsorableLogin (String)

The username of the user or organization who is receiving the sponsorship. Required if sponsorableId is not given.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateSubscriptionInput

\n

Autogenerated input type of UpdateSubscription.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

state (SubscriptionState!)

The new state of the subscription.

\n\n\n\n\n\n\n\n\n\n\n\n

subscribableId (ID!)

The Node ID of the subscribable object to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamDiscussionCommentInput

\n

Autogenerated input type of UpdateTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The updated text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

bodyVersion (String)

The current version of the body content.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamDiscussionInput

\n

Autogenerated input type of UpdateTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The updated text of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

bodyVersion (String)

The current version of the body content. If provided, this update operation\nwill be rejected if the given version does not match the latest version on the server.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

pinned (Boolean)

If provided, sets the pinned state of the updated discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The updated title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamReviewAssignmentInput

\n

Autogenerated input type of UpdateTeamReviewAssignment.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateTeamReviewAssignmentInput is available under the Team review assignments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

algorithm (TeamReviewAssignmentAlgorithm)

The algorithm to use for review assignment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enabled (Boolean!)

Turn on or off review assignment.

\n\n\n\n\n\n\n\n\n\n\n\n

excludedTeamMemberIds ([ID!])

An array of team member IDs to exclude.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the team to update review assignments of.

\n\n\n\n\n\n\n\n\n\n\n\n

notifyTeam (Boolean)

Notify the entire team of the PR if it is delegated.

\n\n\n\n\n\n\n\n\n\n\n\n

teamMemberCount (Int)

The number of team members to assign.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamsRepositoryInput

\n

Autogenerated input type of UpdateTeamsRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

permission (RepositoryPermission!)

Permission that should be granted to the teams.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

Repository ID being granted access to.

\n\n\n\n\n\n\n\n\n\n\n\n

teamIds ([ID!]!)

A list of teams being granted access. Limit: 10.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTopicsInput

\n

Autogenerated input type of UpdateTopics.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

topicNames ([String!]!)

An array of topic names.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUserStatusOrder

\n

Ordering options for user status connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (UserStatusOrderField!)

The field to order user statuses by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nVerifiableDomainOrder

\n

Ordering options for verifiable domain connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (VerifiableDomainOrderField!)

The field to order verifiable domains by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nVerifyVerifiableDomainInput

\n

Autogenerated input type of VerifyVerifiableDomain.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the verifiable domain to verify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n", "miniToc": [ { "contents": "\n AbortQueuedMigrationsInput", @@ -10654,7 +10654,7 @@ ] }, "ghae": { - "html": "
\n
\n

\n \n \nAbortQueuedMigrationsInput

\n

Autogenerated input type of AbortQueuedMigrations.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that is running the migrations.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddAssigneesToAssignableInput

\n

Autogenerated input type of AddAssigneesToAssignable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignableId (ID!)

The id of the assignable object to add assignees to.

\n\n\n\n\n\n\n\n\n\n\n\n

assigneeIds ([ID!]!)

The id of users to add as assignees.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddCommentInput

\n

Autogenerated input type of AddComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddDiscussionCommentInput

\n

Autogenerated input type of AddDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The Node ID of the discussion to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

replyToId (ID)

The Node ID of the discussion comment within this discussion to reply to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddEnterpriseAdminInput

\n

Autogenerated input type of AddEnterpriseAdmin.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise account to which the administrator should be added.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to add as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddLabelsToLabelableInput

\n

Autogenerated input type of AddLabelsToLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!]!)

The ids of the labels to add.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the labelable object to add labels to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectCardInput

\n

Autogenerated input type of AddProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

contentId (ID)

The content of the card. Must be a member of the ProjectCardItem union.

\n\n\n\n\n\n\n\n\n\n\n\n

note (String)

The note on the card.

\n\n\n\n\n\n\n\n\n\n\n\n

projectColumnId (ID!)

The Node ID of the ProjectColumn.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectColumnInput

\n

Autogenerated input type of AddProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the column.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Node ID of the project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewCommentInput

\n

Autogenerated input type of AddPullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitOID (GitObjectID)

The SHA of the commit to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

inReplyTo (ID)

The comment id to reply to.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String)

The relative path of the file to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int)

The line index in the diff to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The node ID of the pull request reviewing.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Node ID of the review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewInput

\n

Autogenerated input type of AddPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The contents of the review body comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comments ([DraftPullRequestReviewComment])

The review line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

commitOID (GitObjectID)

The commit OID the review pertains to.

\n\n\n\n\n\n\n\n\n\n\n\n

event (PullRequestReviewEvent)

The event to perform on the pull request review.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

threads ([DraftPullRequestReviewThread])

The review line comment threads.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewThreadInput

\n

Autogenerated input type of AddPullRequestReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the thread's first comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

line (Int!)

The line of the blob to which the thread refers. The end of the line range for multi-line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The node ID of the pull request reviewing.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Node ID of the review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

side (DiffSide)

The side of the diff on which the line resides. For multi-line comments, this is the side for the end of the line range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int)

The first line of the range to which the comment refers.

\n\n\n\n\n\n\n\n\n\n\n\n

startSide (DiffSide)

The side of the diff on which the start line resides.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddReactionInput

\n

Autogenerated input type of AddReaction.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

content (ReactionContent!)

The name of the emoji to react with.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddStarInput

\n

Autogenerated input type of AddStar.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

starrableId (ID!)

The Starrable ID to star.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddUpvoteInput

\n

Autogenerated input type of AddUpvote.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the discussion or comment to upvote.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nApproveDeploymentsInput

\n

Autogenerated input type of ApproveDeployments.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comment (String)

Optional comment for approving deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentIds ([ID!]!)

The ids of environments to reject deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

workflowRunId (ID!)

The node ID of the workflow run containing the pending deployments.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nArchiveRepositoryInput

\n

Autogenerated input type of ArchiveRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to mark as archived.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAuditLogOrder

\n

Ordering options for Audit Log connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (AuditLogOrderField)

The field to order Audit Logs by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nChangeUserStatusInput

\n

Autogenerated input type of ChangeUserStatus.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

emoji (String)

The emoji to represent your status. Can either be a native Unicode emoji or an emoji name with colons, e.g., 😀.

\n\n\n\n\n\n\n\n\n\n\n\n

expiresAt (DateTime)

If set, the user status will not be shown after this date.

\n\n\n\n\n\n\n\n\n\n\n\n

limitedAvailability (Boolean)

Whether this status should indicate you are not fully available on GitHub, e.g., you are away.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String)

A short description of your current status.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID)

The ID of the organization whose members will be allowed to see the status. If\nomitted, the status will be publicly visible.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckAnnotationData

\n

Information from a check run analysis to specific lines of code.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

annotationLevel (CheckAnnotationLevel!)

Represents an annotation's information level.

\n\n\n\n\n\n\n\n\n\n\n\n

location (CheckAnnotationRange!)

The location of the annotation.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String!)

A short description of the feedback for these lines of code.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to add an annotation to.

\n\n\n\n\n\n\n\n\n\n\n\n

rawDetails (String)

Details about this annotation.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title that represents the annotation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckAnnotationRange

\n

Information from a check run analysis to specific lines of code.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

endColumn (Int)

The ending column of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

endLine (Int!)

The ending line of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

startColumn (Int)

The starting column of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int!)

The starting line of the range.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunAction

\n

Possible further actions the integrator can perform.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

description (String!)

A short explanation of what this action would do.

\n\n\n\n\n\n\n\n\n\n\n\n

identifier (String!)

A reference for the action on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

label (String!)

The text to be displayed on a button in the web UI.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunFilter

\n

The filters that are available when fetching check runs.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (Int)

Filters the check runs created by this application ID.

\n\n\n\n\n\n\n\n\n\n\n\n

checkName (String)

Filters the check runs by this name.

\n\n\n\n\n\n\n\n\n\n\n\n

checkType (CheckRunType)

Filters the check runs by this type.

\n\n\n\n\n\n\n\n\n\n\n\n

status (CheckStatusState)

Filters the check runs by this status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunOutput

\n

Descriptive details about the check run.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

annotations ([CheckAnnotationData!])

The annotations that are made as part of the check run.

\n\n\n\n\n\n\n\n\n\n\n\n

images ([CheckRunOutputImage!])

Images attached to the check run output displayed in the GitHub pull request UI.

\n\n\n\n\n\n\n\n\n\n\n\n

summary (String!)

The summary of the check run (supports Commonmark).

\n\n\n\n\n\n\n\n\n\n\n\n

text (String)

The details of the check run (supports Commonmark).

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

A title to provide for this check run.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunOutputImage

\n

Images attached to the check run output displayed in the GitHub pull request UI.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

alt (String!)

The alternative text for the image.

\n\n\n\n\n\n\n\n\n\n\n\n

caption (String)

A short image description.

\n\n\n\n\n\n\n\n\n\n\n\n

imageUrl (URI!)

The full URL of the image.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckSuiteAutoTriggerPreference

\n

The auto-trigger preferences that are available for check suites.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (ID!)

The node ID of the application that owns the check suite.

\n\n\n\n\n\n\n\n\n\n\n\n

setting (Boolean!)

Set to true to enable automatic creation of CheckSuite events upon pushes to the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckSuiteFilter

\n

The filters that are available when fetching check suites.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (Int)

Filters the check suites created by this application ID.

\n\n\n\n\n\n\n\n\n\n\n\n

checkName (String)

Filters the check suites by this name.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nClearLabelsFromLabelableInput

\n

Autogenerated input type of ClearLabelsFromLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the labelable object to clear the labels from.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloneProjectInput

\n

Autogenerated input type of CloneProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

includeWorkflows (Boolean!)

Whether or not to clone the source project's workflows.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

The visibility of the project, defaults to false (private).

\n\n\n\n\n\n\n\n\n\n\n\n

sourceId (ID!)

The source project to clone.

\n\n\n\n\n\n\n\n\n\n\n\n

targetOwnerId (ID!)

The owner ID to create the project under.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloneTemplateRepositoryInput

\n

Autogenerated input type of CloneTemplateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

includeAllBranches (Boolean)

Whether to copy all branches from the template to the new repository. Defaults\nto copying only the default branch of the template.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner for the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the template repository.

\n\n\n\n\n\n\n\n\n\n\n\n

visibility (RepositoryVisibility!)

Indicates the repository's visibility level.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloseIssueInput

\n

Autogenerated input type of CloseIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

ID of the issue to be closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nClosePullRequestInput

\n

Autogenerated input type of ClosePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitAuthor

\n

Specifies an author for filtering Git commits.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

emails ([String!])

Email addresses to filter by. Commits authored by any of the specified email addresses will be returned.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID)

ID of a User to filter by. If non-null, only commits authored by this user\nwill be returned. This field takes precedence over emails.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitContributionOrder

\n

Ordering options for commit contribution connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (CommitContributionOrderField!)

The field by which to order commit contributions.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitMessage

\n

A message to include with a new commit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The body of the message.

\n\n\n\n\n\n\n\n\n\n\n\n

headline (String!)

The headline of the message.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommittableBranch

\n

A git ref for a commit to be appended to.

\n

The ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).

\n

The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.

\n

Examples

\n

Specify a branch using a global node ID:

\n
{ "id": "MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=" }\n
\n

Specify a branch using nameWithOwner and branch name:

\n
{\n  "nameWithOwner": "github/graphql-client",\n  "branchName": "main"\n}.\n
\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branchName (String)

The unqualified name of the branch to append the commit to.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID)

The Node ID of the Ref to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryNameWithOwner (String)

The nameWithOwner of the repository to commit to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nContributionOrder

\n

Ordering options for contribution connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nConvertProjectCardNoteToIssueInput

\n

Autogenerated input type of ConvertProjectCardNoteToIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The body of the newly created issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectCardId (ID!)

The ProjectCard ID to convert.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to create the issue in.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the newly created issue. Defaults to the card's note text.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nConvertPullRequestToDraftInput

\n

Autogenerated input type of ConvertPullRequestToDraft.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to convert to draft.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateBranchProtectionRuleInput

\n

Autogenerated input type of CreateBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowsDeletions (Boolean)

Can this branch be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

allowsForcePushes (Boolean)

Are force pushes allowed on this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

blocksCreations (Boolean)

Is branch creation a protected operation.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassForcePushActorIds ([ID!])

A list of User or Team IDs allowed to bypass force push targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassPullRequestActorIds ([ID!])

A list of User or Team IDs allowed to bypass pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissesStaleReviews (Boolean)

Will new commits pushed to matching branches dismiss pull request review approvals.

\n\n\n\n\n\n\n\n\n\n\n\n

isAdminEnforced (Boolean)

Can admins overwrite branch protection.

\n\n\n\n\n\n\n\n\n\n\n\n

pattern (String!)

The glob-like pattern used to determine matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

pushActorIds ([ID!])

A list of User, Team or App IDs allowed to push to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The global relay id of the repository in which a new branch protection rule should be created in.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredApprovingReviewCount (Int)

Number of approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusCheckContexts ([String!])

List of required status check contexts that must pass for commits to be accepted to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusChecks ([RequiredStatusCheckInput!])

The list of required status checks.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresApprovingReviews (Boolean)

Are approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCodeOwnerReviews (Boolean)

Are reviews from code owners required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCommitSignatures (Boolean)

Are commits required to be signed.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresConversationResolution (Boolean)

Are conversations required to be resolved before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresLinearHistory (Boolean)

Are merge commits prohibited from being pushed to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStatusChecks (Boolean)

Are status checks required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStrictStatusChecks (Boolean)

Are branches required to be up to date before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsPushes (Boolean)

Is pushing to matching branches restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsReviewDismissals (Boolean)

Is dismissal of pull request reviews restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewDismissalActorIds ([ID!])

A list of User or Team IDs allowed to dismiss reviews on pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCheckRunInput

\n

Autogenerated input type of CreateCheckRun.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actions ([CheckRunAction!])

Possible further actions the integrator can perform, which a user may trigger.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

completedAt (DateTime)

The time that the check run finished.

\n\n\n\n\n\n\n\n\n\n\n\n

conclusion (CheckConclusionState)

The final conclusion of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

detailsUrl (URI)

The URL of the integrator's site that has the full details of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

externalId (String)

A reference for the run on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

headSha (GitObjectID!)

The SHA of the head commit.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

output (CheckRunOutput)

Descriptive details about the run.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

startedAt (DateTime)

The time that the check run began.

\n\n\n\n\n\n\n\n\n\n\n\n

status (RequestableCheckStatusState)

The current status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCheckSuiteInput

\n

Autogenerated input type of CreateCheckSuite.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

headSha (GitObjectID!)

The SHA of the head commit.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCommitOnBranchInput

\n

Autogenerated input type of CreateCommitOnBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branch (CommittableBranch!)

The Ref to be updated. Must be a branch.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID!)

The git commit oid expected at the head of the branch prior to the commit.

\n\n\n\n\n\n\n\n\n\n\n\n

fileChanges (FileChanges)

A description of changes to files in this commit.

\n\n\n\n\n\n\n\n\n\n\n\n

message (CommitMessage!)

The commit message the be included with the commit.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDeploymentInput

\n

Autogenerated input type of CreateDeployment.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateDeploymentInput is available under the Deployments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoMerge (Boolean)

Attempt to automatically merge the default branch into the requested ref, defaults to true.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

Short description of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

environment (String)

Name for the target deployment environment.

\n\n\n\n\n\n\n\n\n\n\n\n

payload (String)

JSON payload with extra information about the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The node ID of the ref to be deployed.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredContexts ([String!])

The status contexts to verify against commit status checks. To bypass required\ncontexts, pass an empty array. Defaults to all unique contexts.

\n\n\n\n\n\n\n\n\n\n\n\n

task (String)

Specifies a task to execute.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDeploymentStatusInput

\n

Autogenerated input type of CreateDeploymentStatus.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateDeploymentStatusInput is available under the Deployments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoInactive (Boolean)

Adds a new inactive status to all non-transient, non-production environment\ndeployments with the same repository and environment name as the created\nstatus's deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

deploymentId (ID!)

The node ID of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the status. Maximum length of 140 characters.

\n\n\n\n\n\n\n\n\n\n\n\n

environment (String)

If provided, updates the environment of the deploy. Otherwise, does not modify the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentUrl (String)

Sets the URL for accessing your environment.

\n\n\n\n\n\n\n\n\n\n\n\n

logUrl (String)

The log URL to associate with this status. This URL should contain\noutput to keep the user updated while the task is running or serve as\nhistorical information for what happened in the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

state (DeploymentStatusState!)

The state of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDiscussionInput

\n

Autogenerated input type of CreateDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The body of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

categoryId (ID!)

The id of the discussion category to associate with this discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The id of the repository on which to create the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateEnterpriseOrganizationInput

\n

Autogenerated input type of CreateEnterpriseOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

adminLogins ([String!]!)

The logins for the administrators of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

billingEmail (String!)

The email used for sending billing receipts.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise owning the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

profileName (String!)

The profile name of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateEnvironmentInput

\n

Autogenerated input type of CreateEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateIpAllowListEntryInput

\n

Autogenerated input type of CreateIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowListValue (String!)

An IP address or range of addresses in CIDR notation.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isActive (Boolean!)

Whether the IP allow list entry is active when an IP allow list is enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

An optional name for the IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner for which to create the new IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateIssueInput

\n

Autogenerated input type of CreateIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The Node ID for the user assignee for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body for the issue description.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueTemplate (String)

The name of an issue template in the repository, assigns labels and assignees from the template to the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title for the issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateLabelInput

\n

Autogenerated input type of CreateLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

color (String!)

A 6 character hex code, without the leading #, identifying the color of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A brief description of the label, such as its purpose.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateMigrationSourceInput

\n

Autogenerated input type of CreateMigrationSource.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

accessToken (String)

The Octoshift migration source access token.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

githubPat (String)

The GitHub personal access token of the user importing to the target repository.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The Octoshift migration source name.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that will own the Octoshift migration source.

\n\n\n\n\n\n\n\n\n\n\n\n

type (MigrationSourceType!)

The Octoshift migration source type.

\n\n\n\n\n\n\n\n\n\n\n\n

url (String!)

The Octoshift migration source URL.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateProjectInput

\n

Autogenerated input type of CreateProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of project.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The owner ID to create the project under.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryIds ([ID!])

A list of repository IDs to create as linked repositories for the project.

\n\n\n\n\n\n\n\n\n\n\n\n

template (ProjectTemplate)

The name of the GitHub-provided template.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreatePullRequestInput

\n

Autogenerated input type of CreatePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

baseRefName (String!)

The name of the branch you want your changes pulled into. This should be an existing branch\non the current repository. You cannot update the base branch on a pull request to point\nto another repository.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The contents of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

draft (Boolean)

Indicates whether this pull request should be a draft.

\n\n\n\n\n\n\n\n\n\n\n\n

headRefName (String!)

The name of the branch where your changes are implemented. For cross-repository pull requests\nin the same network, namespace head_ref_name with a user like this: username:branch.

\n\n\n\n\n\n\n\n\n\n\n\n

maintainerCanModify (Boolean)

Indicates whether maintainers can modify the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateRefInput

\n

Autogenerated input type of CreateRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The fully qualified name of the new Ref (ie: refs/heads/my_new_branch).

\n\n\n\n\n\n\n\n\n\n\n\n

oid (GitObjectID!)

The GitObjectID that the new Ref shall target. Must point to a commit.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the Repository to create the Ref in.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateRepositoryInput

\n

Autogenerated input type of CreateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

hasIssuesEnabled (Boolean)

Indicates if the repository should have the issues feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasWikiEnabled (Boolean)

Indicates if the repository should have the wiki feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

homepageUrl (URI)

The URL for a web page about this repository.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID)

The ID of the owner for the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

teamId (ID)

When an organization is specified as the owner, this ID identifies the team\nthat should be granted access to the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

template (Boolean)

Whether this repository should be marked as a template such that anyone who\ncan access it can create new repositories with the same files and directory structure.

\n\n\n\n\n\n\n\n\n\n\n\n

visibility (RepositoryVisibility!)

Indicates the repository's visibility level.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateTeamDiscussionCommentInput

\n

Autogenerated input type of CreateTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The content of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The ID of the discussion to which the comment belongs.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateTeamDiscussionInput

\n

Autogenerated input type of CreateTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The content of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

private (Boolean)

If true, restricts the visibility of this discussion to team members and\norganization admins. If false or not specified, allows any organization member\nto view this discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

teamId (ID!)

The ID of the team to which the discussion belongs.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteBranchProtectionRuleInput

\n

Autogenerated input type of DeleteBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branchProtectionRuleId (ID!)

The global relay id of the branch protection rule to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDeploymentInput

\n

Autogenerated input type of DeleteDeployment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the deployment to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDiscussionCommentInput

\n

Autogenerated input type of DeleteDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node id of the discussion comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDiscussionInput

\n

Autogenerated input type of DeleteDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The id of the discussion to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteEnvironmentInput

\n

Autogenerated input type of DeleteEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the environment to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIpAllowListEntryInput

\n

Autogenerated input type of DeleteIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ipAllowListEntryId (ID!)

The ID of the IP allow list entry to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIssueCommentInput

\n

Autogenerated input type of DeleteIssueComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIssueInput

\n

Autogenerated input type of DeleteIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteLabelInput

\n

Autogenerated input type of DeleteLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

DeleteLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the label to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectCardInput

\n

Autogenerated input type of DeleteProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

cardId (ID!)

The id of the card to delete.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectColumnInput

\n

Autogenerated input type of DeleteProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectInput

\n

Autogenerated input type of DeleteProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Project ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePullRequestReviewCommentInput

\n

Autogenerated input type of DeletePullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePullRequestReviewInput

\n

Autogenerated input type of DeletePullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteRefInput

\n

Autogenerated input type of DeleteRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The Node ID of the Ref to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteTeamDiscussionCommentInput

\n

Autogenerated input type of DeleteTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteTeamDiscussionInput

\n

Autogenerated input type of DeleteTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The discussion ID to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeploymentOrder

\n

Ordering options for deployment connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (DeploymentOrderField!)

The field to order deployments by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDisablePullRequestAutoMergeInput

\n

Autogenerated input type of DisablePullRequestAutoMerge.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to disable auto merge on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDiscussionOrder

\n

Ways in which lists of discussions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order discussions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (DiscussionOrderField!)

The field by which to order discussions.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDismissPullRequestReviewInput

\n

Autogenerated input type of DismissPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String!)

The contents of the pull request review dismissal message.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDismissRepositoryVulnerabilityAlertInput

\n

Autogenerated input type of DismissRepositoryVulnerabilityAlert.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissReason (DismissReason!)

The reason the Dependabot alert is being dismissed.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryVulnerabilityAlertId (ID!)

The Dependabot alert ID to dismiss.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDraftPullRequestReviewComment

\n

Specifies a review comment to be left with a Pull Request Review.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the comment to leave.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int!)

Position in the file to leave a comment on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDraftPullRequestReviewThread

\n

Specifies a review comment thread to be left with a Pull Request Review.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the comment to leave.

\n\n\n\n\n\n\n\n\n\n\n\n

line (Int!)

The line of the blob to which the thread refers. The end of the line range for multi-line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

side (DiffSide)

The side of the diff on which the line resides. For multi-line comments, this is the side for the end of the line range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int)

The first line of the range to which the comment refers.

\n\n\n\n\n\n\n\n\n\n\n\n

startSide (DiffSide)

The side of the diff on which the start line resides.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnablePullRequestAutoMergeInput

\n

Autogenerated input type of EnablePullRequestAutoMerge.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this merge.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitBody (String)

Commit body to use for the commit when the PR is mergable; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

commitHeadline (String)

Commit headline to use for the commit when the PR is mergable; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

mergeMethod (PullRequestMergeMethod)

The merge method to use. If omitted, defaults to 'MERGE'.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to enable auto-merge on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseAdministratorInvitationOrder

\n

Ordering options for enterprise administrator invitation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseAdministratorInvitationOrderField!)

The field to order enterprise administrator invitations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseMemberOrder

\n

Ordering options for enterprise member connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseMemberOrderField!)

The field to order enterprise members by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountEmailOrder

\n

Ordering options for Enterprise Server user account email connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountEmailOrderField!)

The field to order emails by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountOrder

\n

Ordering options for Enterprise Server user account connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountOrderField!)

The field to order user accounts by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountsUploadOrder

\n

Ordering options for Enterprise Server user accounts upload connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountsUploadOrderField!)

The field to order user accounts uploads by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileAddition

\n

A command to add a file at the given path with the given contents as part of a\ncommit. Any existing file at that that path will be replaced.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

contents (Base64String!)

The base64 encoded contents of the file.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path in the repository where the file will be located.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileChanges

\n

A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file additions and zero or more\nfile deletions.

\n

Both fields are optional; omitting both will produce a commit with no\nfile changes.

\n

deletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.

\n

path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.

\n

Encoding

\n

File contents must be provided in full for each FileAddition.

\n

The contents of a FileAddition must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.

\n

The encoded contents may be binary.

\n

For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (\\n or \\r\\n), and that all files end\nwith a newline.

\n

Modeling file changes

\n

Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:

\n
    \n
  1. \n

    New file addition: create file hello world\\n at path docs/README.txt:

    \n

    {\n"additions" [\n{\n"path": "docs/README.txt",\n"contents": base64encode("hello world\\n")\n}\n]\n}

    \n
    2. \n
  2. \n

    Existing file modification: change existing docs/README.txt to have new\ncontent new content here\\n:

    \n
    {\n  "additions" [\n    {\n      "path": "docs/README.txt",\n      "contents": base64encode("new content here\\n")\n    }\n  ]\n}\n
    \n
    3. \n
  3. \n

    Existing file deletion: remove existing file docs/README.txt.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt"\n    }\n  ]\n}\n
    \n
    4. \n
  4. \n

    File rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt",\n    }\n  ],\n  "additions" [\n    {\n      "path": "newdocs/README.txt",\n      "contents": base64encode("hello world\\n")\n    }\n  ]\n}\n
    \n
    5. \n
  5. \n

    File rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt",\n    }\n  ],\n  "additions" [\n    {\n      "path": "newdocs/README.txt",\n      "contents": base64encode("new contents\\n")\n    }\n  ]\n}.\n
    \n
    6. \n
\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

additions ([FileAddition!])

File to add or change.

\n\n\n\n\n\n\n\n\n\n\n\n

deletions ([FileDeletion!])

Files to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileDeletion

\n

A command to delete the file at the given path as part of a commit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n
NameDescription

path (String!)

The path to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFollowOrganizationInput

\n

Autogenerated input type of FollowOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

ID of the organization to follow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFollowUserInput

\n

Autogenerated input type of FollowUser.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

ID of the user to follow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGistOrder

\n

Ordering options for gist connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (GistOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGrantEnterpriseOrganizationsMigratorRoleInput

\n

Autogenerated input type of GrantEnterpriseOrganizationsMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which all organizations managed by it will be granted the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to grant the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGrantMigratorRoleInput

\n

Autogenerated input type of GrantMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actor (String!)

The user login or Team slug to grant the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

actorType (ActorType!)

Specifies the type of the actor, can be either USER or TEAM.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization that the user/team belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nImportProjectInput

\n

Autogenerated input type of ImportProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of Project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnImports ([ProjectColumnImport!]!)

A list of columns containing issues and pull requests.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of Project.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerName (String!)

The name of the Organization or User to create the Project under.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Whether the Project is public or not.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIpAllowListEntryOrder

\n

Ordering options for IP allow list entry connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IpAllowListEntryOrderField!)

The field to order IP allow list entries by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueCommentOrder

\n

Ways in which lists of issue comments can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order issue comments by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IssueCommentOrderField!)

The field in which to order issue comments by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueFilters

\n

Ways in which to filter lists of issues.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignee (String)

List issues assigned to given name. Pass in null for issues with no assigned\nuser, and * for issues assigned to any user.

\n\n\n\n\n\n\n\n\n\n\n\n

createdBy (String)

List issues created by given name.

\n\n\n\n\n\n\n\n\n\n\n\n

labels ([String!])

List issues where the list of label names exist on the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

mentioned (String)

List issues where the given name is mentioned in the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestone (String)

List issues by given milestone argument. If an string representation of an\ninteger is passed, it should refer to a milestone by its database ID. Pass in\nnull for issues with no milestone, and * for issues that are assigned to any milestone.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneNumber (String)

List issues by given milestone argument. If an string representation of an\ninteger is passed, it should refer to a milestone by its number field. Pass in\nnull for issues with no milestone, and * for issues that are assigned to any milestone.

\n\n\n\n\n\n\n\n\n\n\n\n

since (DateTime)

List issues that have been updated at or after the given date.

\n\n\n\n\n\n\n\n\n\n\n\n

states ([IssueState!])

List issues filtered by the list of states given.

\n\n\n\n\n\n\n\n\n\n\n\n

viewerSubscribed (Boolean)

List issues subscribed to by viewer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueOrder

\n

Ways in which lists of issues can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order issues by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IssueOrderField!)

The field in which to order issues by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLabelOrder

\n

Ways in which lists of labels can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order labels by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (LabelOrderField!)

The field in which to order labels by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLanguageOrder

\n

Ordering options for language connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (LanguageOrderField!)

The field to order languages by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLinkRepositoryToProjectInput

\n

Autogenerated input type of LinkRepositoryToProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to link to a Repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the Repository to link to a Project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLockLockableInput

\n

Autogenerated input type of LockLockable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

lockReason (LockReason)

A reason for why the item will be locked.

\n\n\n\n\n\n\n\n\n\n\n\n

lockableId (ID!)

ID of the item to be locked.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkDiscussionCommentAsAnswerInput

\n

Autogenerated input type of MarkDiscussionCommentAsAnswer.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion comment to mark as an answer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkFileAsViewedInput

\n

Autogenerated input type of MarkFileAsViewed.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to mark as viewed.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkPullRequestReadyForReviewInput

\n

Autogenerated input type of MarkPullRequestReadyForReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be marked as ready for review.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMergeBranchInput

\n

Autogenerated input type of MergeBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

base (String!)

The name of the base branch that the provided head will be merged into.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitMessage (String)

Message to use for the merge commit. If omitted, a default will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

head (String!)

The head to merge into the base branch. This can be a branch name or a commit GitObjectID.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the Repository containing the base branch that will be modified.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMergePullRequestInput

\n

Autogenerated input type of MergePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this merge.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitBody (String)

Commit body to use for the merge commit; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

commitHeadline (String)

Commit headline to use for the merge commit; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID)

OID that the pull request head ref must match to allow merge; if omitted, no check is performed.

\n\n\n\n\n\n\n\n\n\n\n\n

mergeMethod (PullRequestMergeMethod)

The merge method to use. If omitted, defaults to 'MERGE'.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be merged.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMilestoneOrder

\n

Ordering options for milestone connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (MilestoneOrderField!)

The field to order milestones by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMinimizeCommentInput

\n

Autogenerated input type of MinimizeComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

classifier (ReportedContentClassifiers!)

The classification of comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMoveProjectCardInput

\n

Autogenerated input type of MoveProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterCardId (ID)

Place the new card after the card with this id. Pass null to place it at the top.

\n\n\n\n\n\n\n\n\n\n\n\n

cardId (ID!)

The id of the card to move.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to move it into.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMoveProjectColumnInput

\n

Autogenerated input type of MoveProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterColumnId (ID)

Place the new column after the column with this id. Pass null to place it at the front.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to move.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nOrgEnterpriseOwnerOrder

\n

Ordering options for an organization's enterprise owner connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (OrgEnterpriseOwnerOrderField!)

The field to order enterprise owners by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nOrganizationOrder

\n

Ordering options for organization connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (OrganizationOrderField!)

The field to order organizations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPinIssueInput

\n

Autogenerated input type of PinIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to be pinned.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectCardImport

\n

An issue or PR and its owning repository to be used in a project card.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

number (Int!)

The issue or pull request number.

\n\n\n\n\n\n\n\n\n\n\n\n

repository (String!)

Repository name with owner (owner/repository).

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectColumnImport

\n

A project column and a list of its issues and PRs.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

columnName (String!)

The name of the column.

\n\n\n\n\n\n\n\n\n\n\n\n

issues ([ProjectCardImport!])

A list of issues and pull requests in the column.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int!)

The position of the column, starting from 0.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectOrder

\n

Ways in which lists of projects can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order projects by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ProjectOrderField!)

The field in which to order projects by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPullRequestOrder

\n

Ways in which lists of issues can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order pull requests by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PullRequestOrderField!)

The field in which to order pull requests by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReactionOrder

\n

Ways in which lists of reactions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order reactions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ReactionOrderField!)

The field in which to order reactions by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRefOrder

\n

Ways in which lists of git refs can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order refs by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RefOrderField!)

The field in which to order refs by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRefUpdate

\n

A ref update.

\n
\n\n
\n \n
\n

Preview notice

\n

RefUpdate is available under the Update refs preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterOid (GitObjectID!)

The value this ref should be updated to.

\n\n\n\n\n\n\n\n\n\n\n\n

beforeOid (GitObjectID)

The value this ref needs to point to before the update.

\n\n\n\n\n\n\n\n\n\n\n\n

force (Boolean)

Force a non fast-forward update.

\n\n\n\n\n\n\n\n\n\n\n\n

name (GitRefname!)

The fully qualified name of the ref to be update. For example refs/heads/branch-name.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRejectDeploymentsInput

\n

Autogenerated input type of RejectDeployments.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comment (String)

Optional comment for rejecting deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentIds ([ID!]!)

The ids of environments to reject deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

workflowRunId (ID!)

The node ID of the workflow run containing the pending deployments.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReleaseOrder

\n

Ways in which lists of releases can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order releases by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ReleaseOrderField!)

The field in which to order releases by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveAssigneesFromAssignableInput

\n

Autogenerated input type of RemoveAssigneesFromAssignable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignableId (ID!)

The id of the assignable object to remove assignees from.

\n\n\n\n\n\n\n\n\n\n\n\n

assigneeIds ([ID!]!)

The id of users to remove as assignees.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseAdminInput

\n

Autogenerated input type of RemoveEnterpriseAdmin.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The Enterprise ID from which to remove the administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to remove as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveLabelsFromLabelableInput

\n

Autogenerated input type of RemoveLabelsFromLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!]!)

The ids of labels to remove.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the Labelable to remove labels from.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveOutsideCollaboratorInput

\n

Autogenerated input type of RemoveOutsideCollaborator.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to remove the outside collaborator from.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

The ID of the outside collaborator to remove.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveReactionInput

\n

Autogenerated input type of RemoveReaction.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

content (ReactionContent!)

The name of the emoji reaction to remove.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveStarInput

\n

Autogenerated input type of RemoveStar.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

starrableId (ID!)

The Starrable ID to unstar.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveUpvoteInput

\n

Autogenerated input type of RemoveUpvote.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the discussion or comment to remove upvote.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReopenIssueInput

\n

Autogenerated input type of ReopenIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

ID of the issue to be opened.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReopenPullRequestInput

\n

Autogenerated input type of ReopenPullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be reopened.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryInvitationOrder

\n

Ordering options for repository invitation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryInvitationOrderField!)

The field to order repository invitations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryMigrationOrder

\n

Ordering options for repository migrations.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (RepositoryMigrationOrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryMigrationOrderField!)

The field to order repository migrations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryOrder

\n

Ordering options for repository connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRequestReviewsInput

\n

Autogenerated input type of RequestReviews.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

teamIds ([ID!])

The Node IDs of the team to request.

\n\n\n\n\n\n\n\n\n\n\n\n

union (Boolean)

Add users to the set rather than replace.

\n\n\n\n\n\n\n\n\n\n\n\n

userIds ([ID!])

The Node IDs of the user to request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRequiredStatusCheckInput

\n

Specifies the attributes for a new or updated required status check.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (ID)

The ID of the App that must set the status in order for it to be accepted.\nOmit this value to use whichever app has recently been setting this status, or\nuse "any" to allow any app to set the status.

\n\n\n\n\n\n\n\n\n\n\n\n

context (String!)

Status check context that must pass for commits to be accepted to the matching branch.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRerequestCheckSuiteInput

\n

Autogenerated input type of RerequestCheckSuite.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

checkSuiteId (ID!)

The Node ID of the check suite.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nResolveReviewThreadInput

\n

Autogenerated input type of ResolveReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

threadId (ID!)

The ID of the thread to resolve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRevokeEnterpriseOrganizationsMigratorRoleInput

\n

Autogenerated input type of RevokeEnterpriseOrganizationsMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which all organizations managed by it will be granted the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to revoke the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRevokeMigratorRoleInput

\n

Autogenerated input type of RevokeMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actor (String!)

The user login or Team slug to revoke the migrator role from.

\n\n\n\n\n\n\n\n\n\n\n\n

actorType (ActorType!)

Specifies the type of the actor, can be either USER or TEAM.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization that the user/team belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSavedReplyOrder

\n

Ordering options for saved reply connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SavedReplyOrderField!)

The field to order saved replies by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nStarOrder

\n

Ways in which star connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (StarOrderField!)

The field in which to order nodes by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nStartRepositoryMigrationInput

\n

Autogenerated input type of StartRepositoryMigration.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

accessToken (String)

The Octoshift migration source access token.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

continueOnError (Boolean)

Whether to continue the migration on error.

\n\n\n\n\n\n\n\n\n\n\n\n

gitArchiveUrl (String)

The signed URL to access the user-uploaded git archive.

\n\n\n\n\n\n\n\n\n\n\n\n

githubPat (String)

The GitHub personal access token of the user importing to the target repository.

\n\n\n\n\n\n\n\n\n\n\n\n

metadataArchiveUrl (String)

The signed URL to access the user-uploaded metadata archive.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that will own the imported repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryName (String!)

The name of the imported repository.

\n\n\n\n\n\n\n\n\n\n\n\n

skipReleases (Boolean)

Whether to skip migrating releases for the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

sourceId (ID!)

The ID of the Octoshift migration source.

\n\n\n\n\n\n\n\n\n\n\n\n

sourceRepositoryUrl (URI!)

The Octoshift migration source repository URL.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSubmitPullRequestReviewInput

\n

Autogenerated input type of SubmitPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The text field to set on the Pull Request Review.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

event (PullRequestReviewEvent!)

The event to send to the Pull Request Review.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The Pull Request ID to submit any pending reviews.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Pull Request Review ID to submit.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamDiscussionCommentOrder

\n

Ways in which team discussion comment connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamDiscussionCommentOrderField!)

The field by which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamDiscussionOrder

\n

Ways in which team discussion connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamDiscussionOrderField!)

The field by which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamMemberOrder

\n

Ordering options for team member connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamMemberOrderField!)

The field to order team members by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamOrder

\n

Ways in which team connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamOrderField!)

The field in which to order nodes by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamRepositoryOrder

\n

Ordering options for team repository connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamRepositoryOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTransferIssueInput

\n

Autogenerated input type of TransferIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The Node ID of the issue to be transferred.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository the issue should be transferred to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnarchiveRepositoryInput

\n

Autogenerated input type of UnarchiveRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to unarchive.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnfollowOrganizationInput

\n

Autogenerated input type of UnfollowOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

ID of the organization to unfollow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnfollowUserInput

\n

Autogenerated input type of UnfollowUser.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

ID of the user to unfollow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnlinkRepositoryFromProjectInput

\n

Autogenerated input type of UnlinkRepositoryFromProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project linked to the Repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the Repository linked to the Project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnlockLockableInput

\n

Autogenerated input type of UnlockLockable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

lockableId (ID!)

ID of the item to be unlocked.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkDiscussionCommentAsAnswerInput

\n

Autogenerated input type of UnmarkDiscussionCommentAsAnswer.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion comment to unmark as an answer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkFileAsViewedInput

\n

Autogenerated input type of UnmarkFileAsViewed.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to mark as unviewed.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkIssueAsDuplicateInput

\n

Autogenerated input type of UnmarkIssueAsDuplicate.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

canonicalId (ID!)

ID of the issue or pull request currently considered canonical/authoritative/original.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

duplicateId (ID!)

ID of the issue or pull request currently marked as a duplicate.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnminimizeCommentInput

\n

Autogenerated input type of UnminimizeComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnpinIssueInput

\n

Autogenerated input type of UnpinIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to be unpinned.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnresolveReviewThreadInput

\n

Autogenerated input type of UnresolveReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

threadId (ID!)

The ID of the thread to unresolve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateBranchProtectionRuleInput

\n

Autogenerated input type of UpdateBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowsDeletions (Boolean)

Can this branch be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

allowsForcePushes (Boolean)

Are force pushes allowed on this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

blocksCreations (Boolean)

Is branch creation a protected operation.

\n\n\n\n\n\n\n\n\n\n\n\n

branchProtectionRuleId (ID!)

The global relay id of the branch protection rule to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassForcePushActorIds ([ID!])

A list of User or Team IDs allowed to bypass force push targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassPullRequestActorIds ([ID!])

A list of User or Team IDs allowed to bypass pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissesStaleReviews (Boolean)

Will new commits pushed to matching branches dismiss pull request review approvals.

\n\n\n\n\n\n\n\n\n\n\n\n

isAdminEnforced (Boolean)

Can admins overwrite branch protection.

\n\n\n\n\n\n\n\n\n\n\n\n

pattern (String)

The glob-like pattern used to determine matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

pushActorIds ([ID!])

A list of User, Team or App IDs allowed to push to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredApprovingReviewCount (Int)

Number of approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusCheckContexts ([String!])

List of required status check contexts that must pass for commits to be accepted to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusChecks ([RequiredStatusCheckInput!])

The list of required status checks.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresApprovingReviews (Boolean)

Are approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCodeOwnerReviews (Boolean)

Are reviews from code owners required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCommitSignatures (Boolean)

Are commits required to be signed.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresConversationResolution (Boolean)

Are conversations required to be resolved before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresLinearHistory (Boolean)

Are merge commits prohibited from being pushed to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStatusChecks (Boolean)

Are status checks required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStrictStatusChecks (Boolean)

Are branches required to be up to date before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsPushes (Boolean)

Is pushing to matching branches restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsReviewDismissals (Boolean)

Is dismissal of pull request reviews restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewDismissalActorIds ([ID!])

A list of User or Team IDs allowed to dismiss reviews on pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateCheckRunInput

\n

Autogenerated input type of UpdateCheckRun.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actions ([CheckRunAction!])

Possible further actions the integrator can perform, which a user may trigger.

\n\n\n\n\n\n\n\n\n\n\n\n

checkRunId (ID!)

The node of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

completedAt (DateTime)

The time that the check run finished.

\n\n\n\n\n\n\n\n\n\n\n\n

conclusion (CheckConclusionState)

The final conclusion of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

detailsUrl (URI)

The URL of the integrator's site that has the full details of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

externalId (String)

A reference for the run on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

output (CheckRunOutput)

Descriptive details about the run.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

startedAt (DateTime)

The time that the check run began.

\n\n\n\n\n\n\n\n\n\n\n\n

status (RequestableCheckStatusState)

The current status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateCheckSuitePreferencesInput

\n

Autogenerated input type of UpdateCheckSuitePreferences.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoTriggerPreferences ([CheckSuiteAutoTriggerPreference!]!)

The check suite preferences to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateDiscussionCommentInput

\n

Autogenerated input type of UpdateDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The new contents of the comment body.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commentId (ID!)

The Node ID of the discussion comment to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateDiscussionInput

\n

Autogenerated input type of UpdateDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The new contents of the discussion body.

\n\n\n\n\n\n\n\n\n\n\n\n

categoryId (ID)

The Node ID of a discussion category within the same repository to change this discussion to.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The Node ID of the discussion to update.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The new discussion title.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseAllowPrivateRepositoryForkingSettingInput

\n

Autogenerated input type of UpdateEnterpriseAllowPrivateRepositoryForkingSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the allow private repository forking setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the allow private repository forking setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseDefaultRepositoryPermissionSettingInput

\n

Autogenerated input type of UpdateEnterpriseDefaultRepositoryPermissionSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the base repository permission setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseDefaultRepositoryPermissionSettingValue!)

The value for the base repository permission setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanChangeRepositoryVisibilitySettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanChangeRepositoryVisibilitySetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can change repository visibility setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can change repository visibility setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanCreateRepositoriesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanCreateRepositoriesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can create repositories setting.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreateInternalRepositories (Boolean)

Allow members to create internal repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreatePrivateRepositories (Boolean)

Allow members to create private repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreatePublicRepositories (Boolean)

Allow members to create public repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreateRepositoriesPolicyEnabled (Boolean)

When false, allow member organizations to set their own repository creation member privileges.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseMembersCanCreateRepositoriesSettingValue)

Value for the members can create repositories setting on the enterprise. This\nor the granular public/private/internal allowed fields (but not both) must be provided.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanDeleteIssuesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanDeleteIssuesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can delete issues setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can delete issues setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanDeleteRepositoriesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanDeleteRepositoriesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can delete repositories setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can delete repositories setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanInviteCollaboratorsSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanInviteCollaboratorsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can invite collaborators setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can invite collaborators setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanMakePurchasesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanMakePurchasesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can make purchases setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseMembersCanMakePurchasesSettingValue!)

The value for the members can make purchases setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanUpdateProtectedBranchesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanUpdateProtectedBranchesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can update protected branches setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can update protected branches setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanViewDependencyInsightsSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanViewDependencyInsightsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can view dependency insights setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can view dependency insights setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseOrganizationProjectsSettingInput

\n

Autogenerated input type of UpdateEnterpriseOrganizationProjectsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the organization projects setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the organization projects setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseOwnerOrganizationRoleInput

\n

Autogenerated input type of UpdateEnterpriseOwnerOrganizationRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the owner belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization for membership change.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationRole (RoleInOrganization!)

The role to assume in the organization.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseProfileInput

\n

Autogenerated input type of UpdateEnterpriseProfile.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

The description of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The Enterprise ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n

location (String)

The location of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

websiteUrl (String)

The URL of the enterprise's website.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseRepositoryProjectsSettingInput

\n

Autogenerated input type of UpdateEnterpriseRepositoryProjectsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the repository projects setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the repository projects setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseTeamDiscussionsSettingInput

\n

Autogenerated input type of UpdateEnterpriseTeamDiscussionsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the team discussions setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the team discussions setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseTwoFactorAuthenticationRequiredSettingInput

\n

Autogenerated input type of UpdateEnterpriseTwoFactorAuthenticationRequiredSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the two factor authentication required setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledSettingValue!)

The value for the two factor authentication required setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnvironmentInput

\n

Autogenerated input type of UpdateEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentId (ID!)

The node ID of the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewers ([ID!])

The ids of users or teams that can approve deployments to this environment.

\n\n\n\n\n\n\n\n\n\n\n\n

waitTimer (Int)

The wait timer in minutes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListEnabledSettingInput

\n

Autogenerated input type of UpdateIpAllowListEnabledSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner on which to set the IP allow list enabled setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (IpAllowListEnabledSettingValue!)

The value for the IP allow list enabled setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListEntryInput

\n

Autogenerated input type of UpdateIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowListValue (String!)

An IP address or range of addresses in CIDR notation.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ipAllowListEntryId (ID!)

The ID of the IP allow list entry to update.

\n\n\n\n\n\n\n\n\n\n\n\n

isActive (Boolean!)

Whether the IP allow list entry is active when an IP allow list is enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

An optional name for the IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListForInstalledAppsEnabledSettingInput

\n

Autogenerated input type of UpdateIpAllowListForInstalledAppsEnabledSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (IpAllowListForInstalledAppsEnabledSettingValue!)

The value for the IP allow list configuration for installed GitHub Apps setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIssueCommentInput

\n

Autogenerated input type of UpdateIssueComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The updated text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the IssueComment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIssueInput

\n

Autogenerated input type of UpdateIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

An array of Node IDs of users for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body for the issue description.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the Issue to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

state (IssueState)

The desired issue state.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title for the issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateLabelInput

\n

Autogenerated input type of UpdateLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

color (String)

A 6 character hex code, without the leading #, identifying the updated color of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A brief description of the label, such as its purpose.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the label to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The updated name of the label.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateOrganizationAllowPrivateRepositoryForkingSettingInput

\n

Autogenerated input type of UpdateOrganizationAllowPrivateRepositoryForkingSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

forkingEnabled (Boolean!)

Enable forking of private repositories in the organization?.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization on which to set the allow private repository forking setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectCardInput

\n

Autogenerated input type of UpdateProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isArchived (Boolean)

Whether or not the ProjectCard should be archived.

\n\n\n\n\n\n\n\n\n\n\n\n

note (String)

The note of ProjectCard.

\n\n\n\n\n\n\n\n\n\n\n\n

projectCardId (ID!)

The ProjectCard ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectColumnInput

\n

Autogenerated input type of UpdateProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of project column.

\n\n\n\n\n\n\n\n\n\n\n\n

projectColumnId (ID!)

The ProjectColumn ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectInput

\n

Autogenerated input type of UpdateProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of project.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Project ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Whether the project is public or not.

\n\n\n\n\n\n\n\n\n\n\n\n

state (ProjectState)

Whether the project is open or closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestBranchInput

\n

Autogenerated input type of UpdatePullRequestBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID)

The head ref oid for the upstream branch.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestInput

\n

Autogenerated input type of UpdatePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

An array of Node IDs of users for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

baseRefName (String)

The name of the branch you want your changes pulled into. This should be an existing branch\non the current repository.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The contents of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

maintainerCanModify (Boolean)

Indicates whether maintainers can modify the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

state (PullRequestUpdateState)

The target state of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestReviewCommentInput

\n

Autogenerated input type of UpdatePullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewCommentId (ID!)

The Node ID of the comment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestReviewInput

\n

Autogenerated input type of UpdatePullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the pull request review body.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRefInput

\n

Autogenerated input type of UpdateRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

force (Boolean)

Permit updates of branch Refs that are not fast-forwards?.

\n\n\n\n\n\n\n\n\n\n\n\n

oid (GitObjectID!)

The GitObjectID that the Ref shall be updated to target.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The Node ID of the Ref to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRefsInput

\n

Autogenerated input type of UpdateRefs.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateRefsInput is available under the Update refs preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

refUpdates ([RefUpdate!]!)

A list of ref updates.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRepositoryInput

\n

Autogenerated input type of UpdateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A new description for the repository. Pass an empty string to erase the existing description.

\n\n\n\n\n\n\n\n\n\n\n\n

hasIssuesEnabled (Boolean)

Indicates if the repository should have the issues feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasProjectsEnabled (Boolean)

Indicates if the repository should have the project boards feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasWikiEnabled (Boolean)

Indicates if the repository should have the wiki feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

homepageUrl (URI)

The URL for a web page about this repository. Pass an empty string to erase the existing URL.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The new name of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to update.

\n\n\n\n\n\n\n\n\n\n\n\n

template (Boolean)

Whether this repository should be marked as a template such that anyone who\ncan access it can create new repositories with the same files and directory structure.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateSubscriptionInput

\n

Autogenerated input type of UpdateSubscription.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

state (SubscriptionState!)

The new state of the subscription.

\n\n\n\n\n\n\n\n\n\n\n\n

subscribableId (ID!)

The Node ID of the subscribable object to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamDiscussionCommentInput

\n

Autogenerated input type of UpdateTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The updated text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

bodyVersion (String)

The current version of the body content.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamDiscussionInput

\n

Autogenerated input type of UpdateTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The updated text of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

bodyVersion (String)

The current version of the body content. If provided, this update operation\nwill be rejected if the given version does not match the latest version on the server.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

pinned (Boolean)

If provided, sets the pinned state of the updated discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The updated title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamReviewAssignmentInput

\n

Autogenerated input type of UpdateTeamReviewAssignment.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateTeamReviewAssignmentInput is available under the Team review assignments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

algorithm (TeamReviewAssignmentAlgorithm)

The algorithm to use for review assignment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enabled (Boolean!)

Turn on or off review assignment.

\n\n\n\n\n\n\n\n\n\n\n\n

excludedTeamMemberIds ([ID!])

An array of team member IDs to exclude.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the team to update review assignments of.

\n\n\n\n\n\n\n\n\n\n\n\n

notifyTeam (Boolean)

Notify the entire team of the PR if it is delegated.

\n\n\n\n\n\n\n\n\n\n\n\n

teamMemberCount (Int)

The number of team members to assign.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamsRepositoryInput

\n

Autogenerated input type of UpdateTeamsRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

permission (RepositoryPermission!)

Permission that should be granted to the teams.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

Repository ID being granted access to.

\n\n\n\n\n\n\n\n\n\n\n\n

teamIds ([ID!]!)

A list of teams being granted access. Limit: 10.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTopicsInput

\n

Autogenerated input type of UpdateTopics.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

topicNames ([String!]!)

An array of topic names.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUserStatusOrder

\n

Ordering options for user status connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (UserStatusOrderField!)

The field to order user statuses by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n", + "html": "
\n
\n

\n \n \nAbortQueuedMigrationsInput

\n

Autogenerated input type of AbortQueuedMigrations.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that is running the migrations.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddAssigneesToAssignableInput

\n

Autogenerated input type of AddAssigneesToAssignable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignableId (ID!)

The id of the assignable object to add assignees to.

\n\n\n\n\n\n\n\n\n\n\n\n

assigneeIds ([ID!]!)

The id of users to add as assignees.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddCommentInput

\n

Autogenerated input type of AddComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddDiscussionCommentInput

\n

Autogenerated input type of AddDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The Node ID of the discussion to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

replyToId (ID)

The Node ID of the discussion comment within this discussion to reply to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddEnterpriseAdminInput

\n

Autogenerated input type of AddEnterpriseAdmin.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise account to which the administrator should be added.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to add as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddLabelsToLabelableInput

\n

Autogenerated input type of AddLabelsToLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!]!)

The ids of the labels to add.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the labelable object to add labels to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectCardInput

\n

Autogenerated input type of AddProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

contentId (ID)

The content of the card. Must be a member of the ProjectCardItem union.

\n\n\n\n\n\n\n\n\n\n\n\n

note (String)

The note on the card.

\n\n\n\n\n\n\n\n\n\n\n\n

projectColumnId (ID!)

The Node ID of the ProjectColumn.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddProjectColumnInput

\n

Autogenerated input type of AddProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the column.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Node ID of the project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewCommentInput

\n

Autogenerated input type of AddPullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitOID (GitObjectID)

The SHA of the commit to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

inReplyTo (ID)

The comment id to reply to.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String)

The relative path of the file to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int)

The line index in the diff to comment on.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The node ID of the pull request reviewing.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Node ID of the review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewInput

\n

Autogenerated input type of AddPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The contents of the review body comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comments ([DraftPullRequestReviewComment])

The review line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

commitOID (GitObjectID)

The commit OID the review pertains to.

\n\n\n\n\n\n\n\n\n\n\n\n

event (PullRequestReviewEvent)

The event to perform on the pull request review.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

threads ([DraftPullRequestReviewThread])

The review line comment threads.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddPullRequestReviewThreadInput

\n

Autogenerated input type of AddPullRequestReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the thread's first comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

line (Int!)

The line of the blob to which the thread refers. The end of the line range for multi-line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The node ID of the pull request reviewing.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Node ID of the review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

side (DiffSide)

The side of the diff on which the line resides. For multi-line comments, this is the side for the end of the line range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int)

The first line of the range to which the comment refers.

\n\n\n\n\n\n\n\n\n\n\n\n

startSide (DiffSide)

The side of the diff on which the start line resides.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddReactionInput

\n

Autogenerated input type of AddReaction.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

content (ReactionContent!)

The name of the emoji to react with.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddStarInput

\n

Autogenerated input type of AddStar.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

starrableId (ID!)

The Starrable ID to star.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAddUpvoteInput

\n

Autogenerated input type of AddUpvote.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the discussion or comment to upvote.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nApproveDeploymentsInput

\n

Autogenerated input type of ApproveDeployments.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comment (String)

Optional comment for approving deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentIds ([ID!]!)

The ids of environments to reject deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

workflowRunId (ID!)

The node ID of the workflow run containing the pending deployments.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nArchiveRepositoryInput

\n

Autogenerated input type of ArchiveRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to mark as archived.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nAuditLogOrder

\n

Ordering options for Audit Log connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (AuditLogOrderField)

The field to order Audit Logs by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nChangeUserStatusInput

\n

Autogenerated input type of ChangeUserStatus.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

emoji (String)

The emoji to represent your status. Can either be a native Unicode emoji or an emoji name with colons, e.g., 😀.

\n\n\n\n\n\n\n\n\n\n\n\n

expiresAt (DateTime)

If set, the user status will not be shown after this date.

\n\n\n\n\n\n\n\n\n\n\n\n

limitedAvailability (Boolean)

Whether this status should indicate you are not fully available on GitHub, e.g., you are away.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String)

A short description of your current status.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID)

The ID of the organization whose members will be allowed to see the status. If\nomitted, the status will be publicly visible.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckAnnotationData

\n

Information from a check run analysis to specific lines of code.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

annotationLevel (CheckAnnotationLevel!)

Represents an annotation's information level.

\n\n\n\n\n\n\n\n\n\n\n\n

location (CheckAnnotationRange!)

The location of the annotation.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String!)

A short description of the feedback for these lines of code.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to add an annotation to.

\n\n\n\n\n\n\n\n\n\n\n\n

rawDetails (String)

Details about this annotation.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title that represents the annotation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckAnnotationRange

\n

Information from a check run analysis to specific lines of code.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

endColumn (Int)

The ending column of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

endLine (Int!)

The ending line of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

startColumn (Int)

The starting column of the range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int!)

The starting line of the range.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunAction

\n

Possible further actions the integrator can perform.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

description (String!)

A short explanation of what this action would do.

\n\n\n\n\n\n\n\n\n\n\n\n

identifier (String!)

A reference for the action on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

label (String!)

The text to be displayed on a button in the web UI.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunFilter

\n

The filters that are available when fetching check runs.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (Int)

Filters the check runs created by this application ID.

\n\n\n\n\n\n\n\n\n\n\n\n

checkName (String)

Filters the check runs by this name.

\n\n\n\n\n\n\n\n\n\n\n\n

checkType (CheckRunType)

Filters the check runs by this type.

\n\n\n\n\n\n\n\n\n\n\n\n

status (CheckStatusState)

Filters the check runs by this status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunOutput

\n

Descriptive details about the check run.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

annotations ([CheckAnnotationData!])

The annotations that are made as part of the check run.

\n\n\n\n\n\n\n\n\n\n\n\n

images ([CheckRunOutputImage!])

Images attached to the check run output displayed in the GitHub pull request UI.

\n\n\n\n\n\n\n\n\n\n\n\n

summary (String!)

The summary of the check run (supports Commonmark).

\n\n\n\n\n\n\n\n\n\n\n\n

text (String)

The details of the check run (supports Commonmark).

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

A title to provide for this check run.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckRunOutputImage

\n

Images attached to the check run output displayed in the GitHub pull request UI.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

alt (String!)

The alternative text for the image.

\n\n\n\n\n\n\n\n\n\n\n\n

caption (String)

A short image description.

\n\n\n\n\n\n\n\n\n\n\n\n

imageUrl (URI!)

The full URL of the image.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckSuiteAutoTriggerPreference

\n

The auto-trigger preferences that are available for check suites.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (ID!)

The node ID of the application that owns the check suite.

\n\n\n\n\n\n\n\n\n\n\n\n

setting (Boolean!)

Set to true to enable automatic creation of CheckSuite events upon pushes to the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCheckSuiteFilter

\n

The filters that are available when fetching check suites.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (Int)

Filters the check suites created by this application ID.

\n\n\n\n\n\n\n\n\n\n\n\n

checkName (String)

Filters the check suites by this name.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nClearLabelsFromLabelableInput

\n

Autogenerated input type of ClearLabelsFromLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the labelable object to clear the labels from.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloneProjectInput

\n

Autogenerated input type of CloneProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

includeWorkflows (Boolean!)

Whether or not to clone the source project's workflows.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the project.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

The visibility of the project, defaults to false (private).

\n\n\n\n\n\n\n\n\n\n\n\n

sourceId (ID!)

The source project to clone.

\n\n\n\n\n\n\n\n\n\n\n\n

targetOwnerId (ID!)

The owner ID to create the project under.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloneTemplateRepositoryInput

\n

Autogenerated input type of CloneTemplateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

includeAllBranches (Boolean)

Whether to copy all branches from the template to the new repository. Defaults\nto copying only the default branch of the template.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner for the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the template repository.

\n\n\n\n\n\n\n\n\n\n\n\n

visibility (RepositoryVisibility!)

Indicates the repository's visibility level.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCloseIssueInput

\n

Autogenerated input type of CloseIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

ID of the issue to be closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nClosePullRequestInput

\n

Autogenerated input type of ClosePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitAuthor

\n

Specifies an author for filtering Git commits.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

emails ([String!])

Email addresses to filter by. Commits authored by any of the specified email addresses will be returned.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID)

ID of a User to filter by. If non-null, only commits authored by this user\nwill be returned. This field takes precedence over emails.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitContributionOrder

\n

Ordering options for commit contribution connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (CommitContributionOrderField!)

The field by which to order commit contributions.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommitMessage

\n

A message to include with a new commit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The body of the message.

\n\n\n\n\n\n\n\n\n\n\n\n

headline (String!)

The headline of the message.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCommittableBranch

\n

A git ref for a commit to be appended to.

\n

The ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).

\n

The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.

\n

Examples

\n

Specify a branch using a global node ID:

\n
{ "id": "MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=" }\n
\n

Specify a branch using nameWithOwner and branch name:

\n
{\n  "nameWithOwner": "github/graphql-client",\n  "branchName": "main"\n}.\n
\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branchName (String)

The unqualified name of the branch to append the commit to.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID)

The Node ID of the Ref to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryNameWithOwner (String)

The nameWithOwner of the repository to commit to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nContributionOrder

\n

Ordering options for contribution connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nConvertProjectCardNoteToIssueInput

\n

Autogenerated input type of ConvertProjectCardNoteToIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The body of the newly created issue.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectCardId (ID!)

The ProjectCard ID to convert.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to create the issue in.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the newly created issue. Defaults to the card's note text.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nConvertPullRequestToDraftInput

\n

Autogenerated input type of ConvertPullRequestToDraft.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to convert to draft.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateBranchProtectionRuleInput

\n

Autogenerated input type of CreateBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowsDeletions (Boolean)

Can this branch be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

allowsForcePushes (Boolean)

Are force pushes allowed on this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

blocksCreations (Boolean)

Is branch creation a protected operation.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassForcePushActorIds ([ID!])

A list of User or Team IDs allowed to bypass force push targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassPullRequestActorIds ([ID!])

A list of User or Team IDs allowed to bypass pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissesStaleReviews (Boolean)

Will new commits pushed to matching branches dismiss pull request review approvals.

\n\n\n\n\n\n\n\n\n\n\n\n

isAdminEnforced (Boolean)

Can admins overwrite branch protection.

\n\n\n\n\n\n\n\n\n\n\n\n

pattern (String!)

The glob-like pattern used to determine matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

pushActorIds ([ID!])

A list of User, Team, or App IDs allowed to push to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The global relay id of the repository in which a new branch protection rule should be created in.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredApprovingReviewCount (Int)

Number of approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusCheckContexts ([String!])

List of required status check contexts that must pass for commits to be accepted to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusChecks ([RequiredStatusCheckInput!])

The list of required status checks.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresApprovingReviews (Boolean)

Are approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCodeOwnerReviews (Boolean)

Are reviews from code owners required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCommitSignatures (Boolean)

Are commits required to be signed.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresConversationResolution (Boolean)

Are conversations required to be resolved before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresLinearHistory (Boolean)

Are merge commits prohibited from being pushed to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStatusChecks (Boolean)

Are status checks required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStrictStatusChecks (Boolean)

Are branches required to be up to date before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsPushes (Boolean)

Is pushing to matching branches restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsReviewDismissals (Boolean)

Is dismissal of pull request reviews restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewDismissalActorIds ([ID!])

A list of User or Team IDs allowed to dismiss reviews on pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCheckRunInput

\n

Autogenerated input type of CreateCheckRun.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actions ([CheckRunAction!])

Possible further actions the integrator can perform, which a user may trigger.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

completedAt (DateTime)

The time that the check run finished.

\n\n\n\n\n\n\n\n\n\n\n\n

conclusion (CheckConclusionState)

The final conclusion of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

detailsUrl (URI)

The URL of the integrator's site that has the full details of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

externalId (String)

A reference for the run on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

headSha (GitObjectID!)

The SHA of the head commit.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

output (CheckRunOutput)

Descriptive details about the run.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

startedAt (DateTime)

The time that the check run began.

\n\n\n\n\n\n\n\n\n\n\n\n

status (RequestableCheckStatusState)

The current status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCheckSuiteInput

\n

Autogenerated input type of CreateCheckSuite.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

headSha (GitObjectID!)

The SHA of the head commit.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateCommitOnBranchInput

\n

Autogenerated input type of CreateCommitOnBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branch (CommittableBranch!)

The Ref to be updated. Must be a branch.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID!)

The git commit oid expected at the head of the branch prior to the commit.

\n\n\n\n\n\n\n\n\n\n\n\n

fileChanges (FileChanges)

A description of changes to files in this commit.

\n\n\n\n\n\n\n\n\n\n\n\n

message (CommitMessage!)

The commit message the be included with the commit.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDeploymentInput

\n

Autogenerated input type of CreateDeployment.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateDeploymentInput is available under the Deployments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoMerge (Boolean)

Attempt to automatically merge the default branch into the requested ref, defaults to true.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

Short description of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

environment (String)

Name for the target deployment environment.

\n\n\n\n\n\n\n\n\n\n\n\n

payload (String)

JSON payload with extra information about the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The node ID of the ref to be deployed.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredContexts ([String!])

The status contexts to verify against commit status checks. To bypass required\ncontexts, pass an empty array. Defaults to all unique contexts.

\n\n\n\n\n\n\n\n\n\n\n\n

task (String)

Specifies a task to execute.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDeploymentStatusInput

\n

Autogenerated input type of CreateDeploymentStatus.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateDeploymentStatusInput is available under the Deployments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoInactive (Boolean)

Adds a new inactive status to all non-transient, non-production environment\ndeployments with the same repository and environment name as the created\nstatus's deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

deploymentId (ID!)

The node ID of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the status. Maximum length of 140 characters.

\n\n\n\n\n\n\n\n\n\n\n\n

environment (String)

If provided, updates the environment of the deploy. Otherwise, does not modify the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentUrl (String)

Sets the URL for accessing your environment.

\n\n\n\n\n\n\n\n\n\n\n\n

logUrl (String)

The log URL to associate with this status. This URL should contain\noutput to keep the user updated while the task is running or serve as\nhistorical information for what happened in the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n

state (DeploymentStatusState!)

The state of the deployment.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateDiscussionInput

\n

Autogenerated input type of CreateDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The body of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

categoryId (ID!)

The id of the discussion category to associate with this discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The id of the repository on which to create the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateEnterpriseOrganizationInput

\n

Autogenerated input type of CreateEnterpriseOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

adminLogins ([String!]!)

The logins for the administrators of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

billingEmail (String!)

The email used for sending billing receipts.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise owning the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n

profileName (String!)

The profile name of the new organization.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateEnvironmentInput

\n

Autogenerated input type of CreateEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateIpAllowListEntryInput

\n

Autogenerated input type of CreateIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowListValue (String!)

An IP address or range of addresses in CIDR notation.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isActive (Boolean!)

Whether the IP allow list entry is active when an IP allow list is enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

An optional name for the IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner for which to create the new IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateIssueInput

\n

Autogenerated input type of CreateIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

The Node ID for the user assignee for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body for the issue description.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueTemplate (String)

The name of an issue template in the repository, assigns labels and assignees from the template to the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title for the issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateLabelInput

\n

Autogenerated input type of CreateLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

CreateLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

color (String!)

A 6 character hex code, without the leading #, identifying the color of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A brief description of the label, such as its purpose.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateMigrationSourceInput

\n

Autogenerated input type of CreateMigrationSource.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

accessToken (String)

The Octoshift migration source access token.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

githubPat (String)

The GitHub personal access token of the user importing to the target repository.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The Octoshift migration source name.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that will own the Octoshift migration source.

\n\n\n\n\n\n\n\n\n\n\n\n

type (MigrationSourceType!)

The Octoshift migration source type.

\n\n\n\n\n\n\n\n\n\n\n\n

url (String!)

The Octoshift migration source URL.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateProjectInput

\n

Autogenerated input type of CreateProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of project.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The owner ID to create the project under.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryIds ([ID!])

A list of repository IDs to create as linked repositories for the project.

\n\n\n\n\n\n\n\n\n\n\n\n

template (ProjectTemplate)

The name of the GitHub-provided template.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreatePullRequestInput

\n

Autogenerated input type of CreatePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

baseRefName (String!)

The name of the branch you want your changes pulled into. This should be an existing branch\non the current repository. You cannot update the base branch on a pull request to point\nto another repository.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The contents of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

draft (Boolean)

Indicates whether this pull request should be a draft.

\n\n\n\n\n\n\n\n\n\n\n\n

headRefName (String!)

The name of the branch where your changes are implemented. For cross-repository pull requests\nin the same network, namespace head_ref_name with a user like this: username:branch.

\n\n\n\n\n\n\n\n\n\n\n\n

maintainerCanModify (Boolean)

Indicates whether maintainers can modify the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateRefInput

\n

Autogenerated input type of CreateRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The fully qualified name of the new Ref (ie: refs/heads/my_new_branch).

\n\n\n\n\n\n\n\n\n\n\n\n

oid (GitObjectID!)

The GitObjectID that the new Ref shall target. Must point to a commit.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the Repository to create the Ref in.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateRepositoryInput

\n

Autogenerated input type of CreateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A short description of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

hasIssuesEnabled (Boolean)

Indicates if the repository should have the issues feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasWikiEnabled (Boolean)

Indicates if the repository should have the wiki feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

homepageUrl (URI)

The URL for a web page about this repository.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID)

The ID of the owner for the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

teamId (ID)

When an organization is specified as the owner, this ID identifies the team\nthat should be granted access to the new repository.

\n\n\n\n\n\n\n\n\n\n\n\n

template (Boolean)

Whether this repository should be marked as a template such that anyone who\ncan access it can create new repositories with the same files and directory structure.

\n\n\n\n\n\n\n\n\n\n\n\n

visibility (RepositoryVisibility!)

Indicates the repository's visibility level.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateTeamDiscussionCommentInput

\n

Autogenerated input type of CreateTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The content of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The ID of the discussion to which the comment belongs.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nCreateTeamDiscussionInput

\n

Autogenerated input type of CreateTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The content of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

private (Boolean)

If true, restricts the visibility of this discussion to team members and\norganization admins. If false or not specified, allows any organization member\nto view this discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

teamId (ID!)

The ID of the team to which the discussion belongs.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String!)

The title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteBranchProtectionRuleInput

\n

Autogenerated input type of DeleteBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

branchProtectionRuleId (ID!)

The global relay id of the branch protection rule to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDeploymentInput

\n

Autogenerated input type of DeleteDeployment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the deployment to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDiscussionCommentInput

\n

Autogenerated input type of DeleteDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node id of the discussion comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteDiscussionInput

\n

Autogenerated input type of DeleteDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The id of the discussion to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteEnvironmentInput

\n

Autogenerated input type of DeleteEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the environment to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIpAllowListEntryInput

\n

Autogenerated input type of DeleteIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ipAllowListEntryId (ID!)

The ID of the IP allow list entry to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIssueCommentInput

\n

Autogenerated input type of DeleteIssueComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteIssueInput

\n

Autogenerated input type of DeleteIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteLabelInput

\n

Autogenerated input type of DeleteLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

DeleteLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the label to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectCardInput

\n

Autogenerated input type of DeleteProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

cardId (ID!)

The id of the card to delete.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectColumnInput

\n

Autogenerated input type of DeleteProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteProjectInput

\n

Autogenerated input type of DeleteProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Project ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePullRequestReviewCommentInput

\n

Autogenerated input type of DeletePullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeletePullRequestReviewInput

\n

Autogenerated input type of DeletePullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteRefInput

\n

Autogenerated input type of DeleteRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The Node ID of the Ref to be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteTeamDiscussionCommentInput

\n

Autogenerated input type of DeleteTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeleteTeamDiscussionInput

\n

Autogenerated input type of DeleteTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The discussion ID to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDeploymentOrder

\n

Ordering options for deployment connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (DeploymentOrderField!)

The field to order deployments by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDisablePullRequestAutoMergeInput

\n

Autogenerated input type of DisablePullRequestAutoMerge.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to disable auto merge on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDiscussionOrder

\n

Ways in which lists of discussions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order discussions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (DiscussionOrderField!)

The field by which to order discussions.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDismissPullRequestReviewInput

\n

Autogenerated input type of DismissPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

message (String!)

The contents of the pull request review dismissal message.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDismissRepositoryVulnerabilityAlertInput

\n

Autogenerated input type of DismissRepositoryVulnerabilityAlert.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissReason (DismissReason!)

The reason the Dependabot alert is being dismissed.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryVulnerabilityAlertId (ID!)

The Dependabot alert ID to dismiss.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDraftPullRequestReviewComment

\n

Specifies a review comment to be left with a Pull Request Review.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the comment to leave.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int!)

Position in the file to leave a comment on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nDraftPullRequestReviewThread

\n

Specifies a review comment thread to be left with a Pull Request Review.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

Body of the comment to leave.

\n\n\n\n\n\n\n\n\n\n\n\n

line (Int!)

The line of the blob to which the thread refers. The end of the line range for multi-line comments.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

Path to the file being commented on.

\n\n\n\n\n\n\n\n\n\n\n\n

side (DiffSide)

The side of the diff on which the line resides. For multi-line comments, this is the side for the end of the line range.

\n\n\n\n\n\n\n\n\n\n\n\n

startLine (Int)

The first line of the range to which the comment refers.

\n\n\n\n\n\n\n\n\n\n\n\n

startSide (DiffSide)

The side of the diff on which the start line resides.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnablePullRequestAutoMergeInput

\n

Autogenerated input type of EnablePullRequestAutoMerge.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this merge.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitBody (String)

Commit body to use for the commit when the PR is mergable; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

commitHeadline (String)

Commit headline to use for the commit when the PR is mergable; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

mergeMethod (PullRequestMergeMethod)

The merge method to use. If omitted, defaults to 'MERGE'.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to enable auto-merge on.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseAdministratorInvitationOrder

\n

Ordering options for enterprise administrator invitation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseAdministratorInvitationOrderField!)

The field to order enterprise administrator invitations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseMemberOrder

\n

Ordering options for enterprise member connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseMemberOrderField!)

The field to order enterprise members by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountEmailOrder

\n

Ordering options for Enterprise Server user account email connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountEmailOrderField!)

The field to order emails by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountOrder

\n

Ordering options for Enterprise Server user account connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountOrderField!)

The field to order user accounts by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nEnterpriseServerUserAccountsUploadOrder

\n

Ordering options for Enterprise Server user accounts upload connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (EnterpriseServerUserAccountsUploadOrderField!)

The field to order user accounts uploads by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileAddition

\n

A command to add a file at the given path with the given contents as part of a\ncommit. Any existing file at that that path will be replaced.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

contents (Base64String!)

The base64 encoded contents of the file.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path in the repository where the file will be located.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileChanges

\n

A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file additions and zero or more\nfile deletions.

\n

Both fields are optional; omitting both will produce a commit with no\nfile changes.

\n

deletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.

\n

path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.

\n

Encoding

\n

File contents must be provided in full for each FileAddition.

\n

The contents of a FileAddition must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.

\n

The encoded contents may be binary.

\n

For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (\\n or \\r\\n), and that all files end\nwith a newline.

\n

Modeling file changes

\n

Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:

\n
    \n
  1. \n

    New file addition: create file hello world\\n at path docs/README.txt:

    \n

    {\n"additions" [\n{\n"path": "docs/README.txt",\n"contents": base64encode("hello world\\n")\n}\n]\n}

    \n
    2. \n
  2. \n

    Existing file modification: change existing docs/README.txt to have new\ncontent new content here\\n:

    \n
    {\n  "additions" [\n    {\n      "path": "docs/README.txt",\n      "contents": base64encode("new content here\\n")\n    }\n  ]\n}\n
    \n
    3. \n
  3. \n

    Existing file deletion: remove existing file docs/README.txt.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt"\n    }\n  ]\n}\n
    \n
    4. \n
  4. \n

    File rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt",\n    }\n  ],\n  "additions" [\n    {\n      "path": "newdocs/README.txt",\n      "contents": base64encode("hello world\\n")\n    }\n  ]\n}\n
    \n
    5. \n
  5. \n

    File rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:

    \n
    {\n  "deletions" [\n    {\n      "path": "docs/README.txt",\n    }\n  ],\n  "additions" [\n    {\n      "path": "newdocs/README.txt",\n      "contents": base64encode("new contents\\n")\n    }\n  ]\n}.\n
    \n
    6. \n
\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

additions ([FileAddition!])

File to add or change.

\n\n\n\n\n\n\n\n\n\n\n\n

deletions ([FileDeletion!])

Files to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFileDeletion

\n

A command to delete the file at the given path as part of a commit.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n
NameDescription

path (String!)

The path to delete.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFollowOrganizationInput

\n

Autogenerated input type of FollowOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

ID of the organization to follow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nFollowUserInput

\n

Autogenerated input type of FollowUser.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

ID of the user to follow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGistOrder

\n

Ordering options for gist connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (GistOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGrantEnterpriseOrganizationsMigratorRoleInput

\n

Autogenerated input type of GrantEnterpriseOrganizationsMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which all organizations managed by it will be granted the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to grant the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nGrantMigratorRoleInput

\n

Autogenerated input type of GrantMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actor (String!)

The user login or Team slug to grant the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

actorType (ActorType!)

Specifies the type of the actor, can be either USER or TEAM.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization that the user/team belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nImportProjectInput

\n

Autogenerated input type of ImportProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of Project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnImports ([ProjectColumnImport!]!)

A list of columns containing issues and pull requests.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of Project.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerName (String!)

The name of the Organization or User to create the Project under.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Whether the Project is public or not.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIpAllowListEntryOrder

\n

Ordering options for IP allow list entry connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IpAllowListEntryOrderField!)

The field to order IP allow list entries by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueCommentOrder

\n

Ways in which lists of issue comments can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order issue comments by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IssueCommentOrderField!)

The field in which to order issue comments by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueFilters

\n

Ways in which to filter lists of issues.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignee (String)

List issues assigned to given name. Pass in null for issues with no assigned\nuser, and * for issues assigned to any user.

\n\n\n\n\n\n\n\n\n\n\n\n

createdBy (String)

List issues created by given name.

\n\n\n\n\n\n\n\n\n\n\n\n

labels ([String!])

List issues where the list of label names exist on the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

mentioned (String)

List issues where the given name is mentioned in the issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestone (String)

List issues by given milestone argument. If an string representation of an\ninteger is passed, it should refer to a milestone by its database ID. Pass in\nnull for issues with no milestone, and * for issues that are assigned to any milestone.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneNumber (String)

List issues by given milestone argument. If an string representation of an\ninteger is passed, it should refer to a milestone by its number field. Pass in\nnull for issues with no milestone, and * for issues that are assigned to any milestone.

\n\n\n\n\n\n\n\n\n\n\n\n

since (DateTime)

List issues that have been updated at or after the given date.

\n\n\n\n\n\n\n\n\n\n\n\n

states ([IssueState!])

List issues filtered by the list of states given.

\n\n\n\n\n\n\n\n\n\n\n\n

viewerSubscribed (Boolean)

List issues subscribed to by viewer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nIssueOrder

\n

Ways in which lists of issues can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order issues by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (IssueOrderField!)

The field in which to order issues by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLabelOrder

\n

Ways in which lists of labels can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order labels by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (LabelOrderField!)

The field in which to order labels by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLanguageOrder

\n

Ordering options for language connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (LanguageOrderField!)

The field to order languages by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLinkRepositoryToProjectInput

\n

Autogenerated input type of LinkRepositoryToProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project to link to a Repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the Repository to link to a Project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nLockLockableInput

\n

Autogenerated input type of LockLockable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

lockReason (LockReason)

A reason for why the item will be locked.

\n\n\n\n\n\n\n\n\n\n\n\n

lockableId (ID!)

ID of the item to be locked.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkDiscussionCommentAsAnswerInput

\n

Autogenerated input type of MarkDiscussionCommentAsAnswer.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion comment to mark as an answer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkFileAsViewedInput

\n

Autogenerated input type of MarkFileAsViewed.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to mark as viewed.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMarkPullRequestReadyForReviewInput

\n

Autogenerated input type of MarkPullRequestReadyForReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be marked as ready for review.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMergeBranchInput

\n

Autogenerated input type of MergeBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

base (String!)

The name of the base branch that the provided head will be merged into.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitMessage (String)

Message to use for the merge commit. If omitted, a default will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

head (String!)

The head to merge into the base branch. This can be a branch name or a commit GitObjectID.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the Repository containing the base branch that will be modified.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMergePullRequestInput

\n

Autogenerated input type of MergePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

authorEmail (String)

The email address to associate with this merge.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commitBody (String)

Commit body to use for the merge commit; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

commitHeadline (String)

Commit headline to use for the merge commit; if omitted, a default message will be used.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID)

OID that the pull request head ref must match to allow merge; if omitted, no check is performed.

\n\n\n\n\n\n\n\n\n\n\n\n

mergeMethod (PullRequestMergeMethod)

The merge method to use. If omitted, defaults to 'MERGE'.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be merged.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMilestoneOrder

\n

Ordering options for milestone connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (MilestoneOrderField!)

The field to order milestones by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMinimizeCommentInput

\n

Autogenerated input type of MinimizeComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

classifier (ReportedContentClassifiers!)

The classification of comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMoveProjectCardInput

\n

Autogenerated input type of MoveProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterCardId (ID)

Place the new card after the card with this id. Pass null to place it at the top.

\n\n\n\n\n\n\n\n\n\n\n\n

cardId (ID!)

The id of the card to move.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to move it into.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nMoveProjectColumnInput

\n

Autogenerated input type of MoveProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterColumnId (ID)

Place the new column after the column with this id. Pass null to place it at the front.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

columnId (ID!)

The id of the column to move.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nOrgEnterpriseOwnerOrder

\n

Ordering options for an organization's enterprise owner connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (OrgEnterpriseOwnerOrderField!)

The field to order enterprise owners by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nOrganizationOrder

\n

Ordering options for organization connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (OrganizationOrderField!)

The field to order organizations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPinIssueInput

\n

Autogenerated input type of PinIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to be pinned.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectCardImport

\n

An issue or PR and its owning repository to be used in a project card.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

number (Int!)

The issue or pull request number.

\n\n\n\n\n\n\n\n\n\n\n\n

repository (String!)

Repository name with owner (owner/repository).

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectColumnImport

\n

A project column and a list of its issues and PRs.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

columnName (String!)

The name of the column.

\n\n\n\n\n\n\n\n\n\n\n\n

issues ([ProjectCardImport!])

A list of issues and pull requests in the column.

\n\n\n\n\n\n\n\n\n\n\n\n

position (Int!)

The position of the column, starting from 0.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nProjectOrder

\n

Ways in which lists of projects can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order projects by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ProjectOrderField!)

The field in which to order projects by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nPullRequestOrder

\n

Ways in which lists of issues can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order pull requests by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (PullRequestOrderField!)

The field in which to order pull requests by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReactionOrder

\n

Ways in which lists of reactions can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order reactions by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ReactionOrderField!)

The field in which to order reactions by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRefOrder

\n

Ways in which lists of git refs can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order refs by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RefOrderField!)

The field in which to order refs by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRefUpdate

\n

A ref update.

\n
\n\n
\n \n
\n

Preview notice

\n

RefUpdate is available under the Update refs preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

afterOid (GitObjectID!)

The value this ref should be updated to.

\n\n\n\n\n\n\n\n\n\n\n\n

beforeOid (GitObjectID)

The value this ref needs to point to before the update.

\n\n\n\n\n\n\n\n\n\n\n\n

force (Boolean)

Force a non fast-forward update.

\n\n\n\n\n\n\n\n\n\n\n\n

name (GitRefname!)

The fully qualified name of the ref to be update. For example refs/heads/branch-name.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRejectDeploymentsInput

\n

Autogenerated input type of RejectDeployments.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

comment (String)

Optional comment for rejecting deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentIds ([ID!]!)

The ids of environments to reject deployments.

\n\n\n\n\n\n\n\n\n\n\n\n

workflowRunId (ID!)

The node ID of the workflow run containing the pending deployments.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReleaseOrder

\n

Ways in which lists of releases can be ordered upon return.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order releases by the specified field.

\n\n\n\n\n\n\n\n\n\n\n\n

field (ReleaseOrderField!)

The field in which to order releases by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveAssigneesFromAssignableInput

\n

Autogenerated input type of RemoveAssigneesFromAssignable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assignableId (ID!)

The id of the assignable object to remove assignees from.

\n\n\n\n\n\n\n\n\n\n\n\n

assigneeIds ([ID!]!)

The id of users to remove as assignees.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveEnterpriseAdminInput

\n

Autogenerated input type of RemoveEnterpriseAdmin.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The Enterprise ID from which to remove the administrator.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to remove as an administrator.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveLabelsFromLabelableInput

\n

Autogenerated input type of RemoveLabelsFromLabelable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!]!)

The ids of labels to remove.

\n\n\n\n\n\n\n\n\n\n\n\n

labelableId (ID!)

The id of the Labelable to remove labels from.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveOutsideCollaboratorInput

\n

Autogenerated input type of RemoveOutsideCollaborator.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization to remove the outside collaborator from.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

The ID of the outside collaborator to remove.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveReactionInput

\n

Autogenerated input type of RemoveReaction.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

content (ReactionContent!)

The name of the emoji reaction to remove.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveStarInput

\n

Autogenerated input type of RemoveStar.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

starrableId (ID!)

The Starrable ID to unstar.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRemoveUpvoteInput

\n

Autogenerated input type of RemoveUpvote.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the discussion or comment to remove upvote.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReopenIssueInput

\n

Autogenerated input type of ReopenIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

ID of the issue to be opened.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nReopenPullRequestInput

\n

Autogenerated input type of ReopenPullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

ID of the pull request to be reopened.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryInvitationOrder

\n

Ordering options for repository invitation connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryInvitationOrderField!)

The field to order repository invitations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryMigrationOrder

\n

Ordering options for repository migrations.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (RepositoryMigrationOrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryMigrationOrderField!)

The field to order repository migrations by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRepositoryOrder

\n

Ordering options for repository connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (RepositoryOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRequestReviewsInput

\n

Autogenerated input type of RequestReviews.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

teamIds ([ID!])

The Node IDs of the team to request.

\n\n\n\n\n\n\n\n\n\n\n\n

union (Boolean)

Add users to the set rather than replace.

\n\n\n\n\n\n\n\n\n\n\n\n

userIds ([ID!])

The Node IDs of the user to request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRequiredStatusCheckInput

\n

Specifies the attributes for a new or updated required status check.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

appId (ID)

The ID of the App that must set the status in order for it to be accepted.\nOmit this value to use whichever app has recently been setting this status, or\nuse "any" to allow any app to set the status.

\n\n\n\n\n\n\n\n\n\n\n\n

context (String!)

Status check context that must pass for commits to be accepted to the matching branch.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRerequestCheckSuiteInput

\n

Autogenerated input type of RerequestCheckSuite.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

checkSuiteId (ID!)

The Node ID of the check suite.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nResolveReviewThreadInput

\n

Autogenerated input type of ResolveReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

threadId (ID!)

The ID of the thread to resolve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRevokeEnterpriseOrganizationsMigratorRoleInput

\n

Autogenerated input type of RevokeEnterpriseOrganizationsMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise to which all organizations managed by it will be granted the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n

login (String!)

The login of the user to revoke the migrator role.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nRevokeMigratorRoleInput

\n

Autogenerated input type of RevokeMigratorRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actor (String!)

The user login or Team slug to revoke the migrator role from.

\n\n\n\n\n\n\n\n\n\n\n\n

actorType (ActorType!)

Specifies the type of the actor, can be either USER or TEAM.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization that the user/team belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSavedReplyOrder

\n

Ordering options for saved reply connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (SavedReplyOrderField!)

The field to order saved replies by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nStarOrder

\n

Ways in which star connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (StarOrderField!)

The field in which to order nodes by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nStartRepositoryMigrationInput

\n

Autogenerated input type of StartRepositoryMigration.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

accessToken (String)

The Octoshift migration source access token.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

continueOnError (Boolean)

Whether to continue the migration on error.

\n\n\n\n\n\n\n\n\n\n\n\n

gitArchiveUrl (String)

The signed URL to access the user-uploaded git archive.

\n\n\n\n\n\n\n\n\n\n\n\n

githubPat (String)

The GitHub personal access token of the user importing to the target repository.

\n\n\n\n\n\n\n\n\n\n\n\n

metadataArchiveUrl (String)

The signed URL to access the user-uploaded metadata archive.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the organization that will own the imported repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryName (String!)

The name of the imported repository.

\n\n\n\n\n\n\n\n\n\n\n\n

skipReleases (Boolean)

Whether to skip migrating releases for the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

sourceId (ID!)

The ID of the Octoshift migration source.

\n\n\n\n\n\n\n\n\n\n\n\n

sourceRepositoryUrl (URI!)

The Octoshift migration source repository URL.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nSubmitPullRequestReviewInput

\n

Autogenerated input type of SubmitPullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The text field to set on the Pull Request Review.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

event (PullRequestReviewEvent!)

The event to send to the Pull Request Review.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID)

The Pull Request ID to submit any pending reviews.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID)

The Pull Request Review ID to submit.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamDiscussionCommentOrder

\n

Ways in which team discussion comment connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamDiscussionCommentOrderField!)

The field by which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamDiscussionOrder

\n

Ways in which team discussion connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamDiscussionOrderField!)

The field by which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamMemberOrder

\n

Ordering options for team member connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamMemberOrderField!)

The field to order team members by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamOrder

\n

Ways in which team connections can be ordered.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The direction in which to order nodes.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamOrderField!)

The field in which to order nodes by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTeamRepositoryOrder

\n

Ordering options for team repository connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (TeamRepositoryOrderField!)

The field to order repositories by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nTransferIssueInput

\n

Autogenerated input type of TransferIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The Node ID of the issue to be transferred.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository the issue should be transferred to.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnarchiveRepositoryInput

\n

Autogenerated input type of UnarchiveRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to unarchive.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnfollowOrganizationInput

\n

Autogenerated input type of UnfollowOrganization.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

ID of the organization to unfollow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnfollowUserInput

\n

Autogenerated input type of UnfollowUser.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

userId (ID!)

ID of the user to unfollow.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnlinkRepositoryFromProjectInput

\n

Autogenerated input type of UnlinkRepositoryFromProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The ID of the Project linked to the Repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the Repository linked to the Project.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnlockLockableInput

\n

Autogenerated input type of UnlockLockable.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

lockableId (ID!)

ID of the item to be unlocked.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkDiscussionCommentAsAnswerInput

\n

Autogenerated input type of UnmarkDiscussionCommentAsAnswer.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion comment to unmark as an answer.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkFileAsViewedInput

\n

Autogenerated input type of UnmarkFileAsViewed.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

path (String!)

The path of the file to mark as unviewed.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnmarkIssueAsDuplicateInput

\n

Autogenerated input type of UnmarkIssueAsDuplicate.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

canonicalId (ID!)

ID of the issue or pull request currently considered canonical/authoritative/original.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

duplicateId (ID!)

ID of the issue or pull request currently marked as a duplicate.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnminimizeCommentInput

\n

Autogenerated input type of UnminimizeComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

subjectId (ID!)

The Node ID of the subject to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnpinIssueInput

\n

Autogenerated input type of UnpinIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

issueId (ID!)

The ID of the issue to be unpinned.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUnresolveReviewThreadInput

\n

Autogenerated input type of UnresolveReviewThread.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

threadId (ID!)

The ID of the thread to unresolve.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateBranchProtectionRuleInput

\n

Autogenerated input type of UpdateBranchProtectionRule.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowsDeletions (Boolean)

Can this branch be deleted.

\n\n\n\n\n\n\n\n\n\n\n\n

allowsForcePushes (Boolean)

Are force pushes allowed on this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

blocksCreations (Boolean)

Is branch creation a protected operation.

\n\n\n\n\n\n\n\n\n\n\n\n

branchProtectionRuleId (ID!)

The global relay id of the branch protection rule to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassForcePushActorIds ([ID!])

A list of User or Team IDs allowed to bypass force push targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

bypassPullRequestActorIds ([ID!])

A list of User or Team IDs allowed to bypass pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

dismissesStaleReviews (Boolean)

Will new commits pushed to matching branches dismiss pull request review approvals.

\n\n\n\n\n\n\n\n\n\n\n\n

isAdminEnforced (Boolean)

Can admins overwrite branch protection.

\n\n\n\n\n\n\n\n\n\n\n\n

pattern (String)

The glob-like pattern used to determine matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

pushActorIds ([ID!])

A list of User, Team, or App IDs allowed to push to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredApprovingReviewCount (Int)

Number of approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusCheckContexts ([String!])

List of required status check contexts that must pass for commits to be accepted to matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiredStatusChecks ([RequiredStatusCheckInput!])

The list of required status checks.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresApprovingReviews (Boolean)

Are approving reviews required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCodeOwnerReviews (Boolean)

Are reviews from code owners required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresCommitSignatures (Boolean)

Are commits required to be signed.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresConversationResolution (Boolean)

Are conversations required to be resolved before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresLinearHistory (Boolean)

Are merge commits prohibited from being pushed to this branch.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStatusChecks (Boolean)

Are status checks required to update matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n

requiresStrictStatusChecks (Boolean)

Are branches required to be up to date before merging.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsPushes (Boolean)

Is pushing to matching branches restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

restrictsReviewDismissals (Boolean)

Is dismissal of pull request reviews restricted.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewDismissalActorIds ([ID!])

A list of User or Team IDs allowed to dismiss reviews on pull requests targeting matching branches.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateCheckRunInput

\n

Autogenerated input type of UpdateCheckRun.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

actions ([CheckRunAction!])

Possible further actions the integrator can perform, which a user may trigger.

\n\n\n\n\n\n\n\n\n\n\n\n

checkRunId (ID!)

The node of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

completedAt (DateTime)

The time that the check run finished.

\n\n\n\n\n\n\n\n\n\n\n\n

conclusion (CheckConclusionState)

The final conclusion of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

detailsUrl (URI)

The URL of the integrator's site that has the full details of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

externalId (String)

A reference for the run on the integrator's system.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of the check.

\n\n\n\n\n\n\n\n\n\n\n\n

output (CheckRunOutput)

Descriptive details about the run.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

startedAt (DateTime)

The time that the check run began.

\n\n\n\n\n\n\n\n\n\n\n\n

status (RequestableCheckStatusState)

The current status.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateCheckSuitePreferencesInput

\n

Autogenerated input type of UpdateCheckSuitePreferences.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

autoTriggerPreferences ([CheckSuiteAutoTriggerPreference!]!)

The check suite preferences to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateDiscussionCommentInput

\n

Autogenerated input type of UpdateDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The new contents of the comment body.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

commentId (ID!)

The Node ID of the discussion comment to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateDiscussionInput

\n

Autogenerated input type of UpdateDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The new contents of the discussion body.

\n\n\n\n\n\n\n\n\n\n\n\n

categoryId (ID)

The Node ID of a discussion category within the same repository to change this discussion to.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

discussionId (ID!)

The Node ID of the discussion to update.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The new discussion title.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseAllowPrivateRepositoryForkingSettingInput

\n

Autogenerated input type of UpdateEnterpriseAllowPrivateRepositoryForkingSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the allow private repository forking setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the allow private repository forking setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseDefaultRepositoryPermissionSettingInput

\n

Autogenerated input type of UpdateEnterpriseDefaultRepositoryPermissionSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the base repository permission setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseDefaultRepositoryPermissionSettingValue!)

The value for the base repository permission setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanChangeRepositoryVisibilitySettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanChangeRepositoryVisibilitySetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can change repository visibility setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can change repository visibility setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanCreateRepositoriesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanCreateRepositoriesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can create repositories setting.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreateInternalRepositories (Boolean)

Allow members to create internal repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreatePrivateRepositories (Boolean)

Allow members to create private repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreatePublicRepositories (Boolean)

Allow members to create public repositories. Defaults to current value.

\n\n\n\n\n\n\n\n\n\n\n\n

membersCanCreateRepositoriesPolicyEnabled (Boolean)

When false, allow member organizations to set their own repository creation member privileges.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseMembersCanCreateRepositoriesSettingValue)

Value for the members can create repositories setting on the enterprise. This\nor the granular public/private/internal allowed fields (but not both) must be provided.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanDeleteIssuesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanDeleteIssuesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can delete issues setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can delete issues setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanDeleteRepositoriesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanDeleteRepositoriesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can delete repositories setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can delete repositories setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanInviteCollaboratorsSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanInviteCollaboratorsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can invite collaborators setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can invite collaborators setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanMakePurchasesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanMakePurchasesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can make purchases setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseMembersCanMakePurchasesSettingValue!)

The value for the members can make purchases setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanUpdateProtectedBranchesSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanUpdateProtectedBranchesSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can update protected branches setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can update protected branches setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseMembersCanViewDependencyInsightsSettingInput

\n

Autogenerated input type of UpdateEnterpriseMembersCanViewDependencyInsightsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the members can view dependency insights setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the members can view dependency insights setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseOrganizationProjectsSettingInput

\n

Autogenerated input type of UpdateEnterpriseOrganizationProjectsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the organization projects setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the organization projects setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseOwnerOrganizationRoleInput

\n

Autogenerated input type of UpdateEnterpriseOwnerOrganizationRole.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the Enterprise which the owner belongs to.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization for membership change.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationRole (RoleInOrganization!)

The role to assume in the organization.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseProfileInput

\n

Autogenerated input type of UpdateEnterpriseProfile.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

The description of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The Enterprise ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n

location (String)

The location of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n

websiteUrl (String)

The URL of the enterprise's website.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseRepositoryProjectsSettingInput

\n

Autogenerated input type of UpdateEnterpriseRepositoryProjectsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the repository projects setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the repository projects setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseTeamDiscussionsSettingInput

\n

Autogenerated input type of UpdateEnterpriseTeamDiscussionsSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the team discussions setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledDisabledSettingValue!)

The value for the team discussions setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnterpriseTwoFactorAuthenticationRequiredSettingInput

\n

Autogenerated input type of UpdateEnterpriseTwoFactorAuthenticationRequiredSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enterpriseId (ID!)

The ID of the enterprise on which to set the two factor authentication required setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (EnterpriseEnabledSettingValue!)

The value for the two factor authentication required setting on the enterprise.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateEnvironmentInput

\n

Autogenerated input type of UpdateEnvironment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

environmentId (ID!)

The node ID of the environment.

\n\n\n\n\n\n\n\n\n\n\n\n

reviewers ([ID!])

The ids of users or teams that can approve deployments to this environment.

\n\n\n\n\n\n\n\n\n\n\n\n

waitTimer (Int)

The wait timer in minutes.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListEnabledSettingInput

\n

Autogenerated input type of UpdateIpAllowListEnabledSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner on which to set the IP allow list enabled setting.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (IpAllowListEnabledSettingValue!)

The value for the IP allow list enabled setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListEntryInput

\n

Autogenerated input type of UpdateIpAllowListEntry.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

allowListValue (String!)

An IP address or range of addresses in CIDR notation.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ipAllowListEntryId (ID!)

The ID of the IP allow list entry to update.

\n\n\n\n\n\n\n\n\n\n\n\n

isActive (Boolean!)

Whether the IP allow list entry is active when an IP allow list is enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

An optional name for the IP allow list entry.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIpAllowListForInstalledAppsEnabledSettingInput

\n

Autogenerated input type of UpdateIpAllowListForInstalledAppsEnabledSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

ownerId (ID!)

The ID of the owner.

\n\n\n\n\n\n\n\n\n\n\n\n

settingValue (IpAllowListForInstalledAppsEnabledSettingValue!)

The value for the IP allow list configuration for installed GitHub Apps setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIssueCommentInput

\n

Autogenerated input type of UpdateIssueComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The updated text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the IssueComment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateIssueInput

\n

Autogenerated input type of UpdateIssue.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

An array of Node IDs of users for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The body for the issue description.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the Issue to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this issue.

\n\n\n\n\n\n\n\n\n\n\n\n

state (IssueState)

The desired issue state.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title for the issue.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateLabelInput

\n

Autogenerated input type of UpdateLabel.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateLabelInput is available under the Labels preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

color (String)

A 6 character hex code, without the leading #, identifying the updated color of the label.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A brief description of the label, such as its purpose.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the label to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The updated name of the label.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateOrganizationAllowPrivateRepositoryForkingSettingInput

\n

Autogenerated input type of UpdateOrganizationAllowPrivateRepositoryForkingSetting.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

forkingEnabled (Boolean!)

Enable forking of private repositories in the organization?.

\n\n\n\n\n\n\n\n\n\n\n\n

organizationId (ID!)

The ID of the organization on which to set the allow private repository forking setting.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectCardInput

\n

Autogenerated input type of UpdateProjectCard.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

isArchived (Boolean)

Whether or not the ProjectCard should be archived.

\n\n\n\n\n\n\n\n\n\n\n\n

note (String)

The note of ProjectCard.

\n\n\n\n\n\n\n\n\n\n\n\n

projectCardId (ID!)

The ProjectCard ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectColumnInput

\n

Autogenerated input type of UpdateProjectColumn.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String!)

The name of project column.

\n\n\n\n\n\n\n\n\n\n\n\n

projectColumnId (ID!)

The ProjectColumn ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateProjectInput

\n

Autogenerated input type of UpdateProject.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The description of project.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The name of project.

\n\n\n\n\n\n\n\n\n\n\n\n

projectId (ID!)

The Project ID to update.

\n\n\n\n\n\n\n\n\n\n\n\n

public (Boolean)

Whether the project is public or not.

\n\n\n\n\n\n\n\n\n\n\n\n

state (ProjectState)

Whether the project is open or closed.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestBranchInput

\n

Autogenerated input type of UpdatePullRequestBranch.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

expectedHeadOid (GitObjectID)

The head ref oid for the upstream branch.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestInput

\n

Autogenerated input type of UpdatePullRequest.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

assigneeIds ([ID!])

An array of Node IDs of users for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

baseRefName (String)

The name of the branch you want your changes pulled into. This should be an existing branch\non the current repository.

\n\n\n\n\n\n\n\n\n\n\n\n

body (String)

The contents of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

labelIds ([ID!])

An array of Node IDs of labels for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

maintainerCanModify (Boolean)

Indicates whether maintainers can modify the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

milestoneId (ID)

The Node ID of the milestone for this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

projectIds ([ID!])

An array of Node IDs for projects associated with this pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestId (ID!)

The Node ID of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

state (PullRequestUpdateState)

The target state of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The title of the pull request.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestReviewCommentInput

\n

Autogenerated input type of UpdatePullRequestReviewComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewCommentId (ID!)

The Node ID of the comment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdatePullRequestReviewInput

\n

Autogenerated input type of UpdatePullRequestReview.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The contents of the pull request review body.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

pullRequestReviewId (ID!)

The Node ID of the pull request review to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRefInput

\n

Autogenerated input type of UpdateRef.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

force (Boolean)

Permit updates of branch Refs that are not fast-forwards?.

\n\n\n\n\n\n\n\n\n\n\n\n

oid (GitObjectID!)

The GitObjectID that the Ref shall be updated to target.

\n\n\n\n\n\n\n\n\n\n\n\n

refId (ID!)

The Node ID of the Ref to be updated.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRefsInput

\n

Autogenerated input type of UpdateRefs.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateRefsInput is available under the Update refs preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

refUpdates ([RefUpdate!]!)

A list of ref updates.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateRepositoryInput

\n

Autogenerated input type of UpdateRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

description (String)

A new description for the repository. Pass an empty string to erase the existing description.

\n\n\n\n\n\n\n\n\n\n\n\n

hasIssuesEnabled (Boolean)

Indicates if the repository should have the issues feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasProjectsEnabled (Boolean)

Indicates if the repository should have the project boards feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

hasWikiEnabled (Boolean)

Indicates if the repository should have the wiki feature enabled.

\n\n\n\n\n\n\n\n\n\n\n\n

homepageUrl (URI)

The URL for a web page about this repository. Pass an empty string to erase the existing URL.

\n\n\n\n\n\n\n\n\n\n\n\n

name (String)

The new name of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The ID of the repository to update.

\n\n\n\n\n\n\n\n\n\n\n\n

template (Boolean)

Whether this repository should be marked as a template such that anyone who\ncan access it can create new repositories with the same files and directory structure.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateSubscriptionInput

\n

Autogenerated input type of UpdateSubscription.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

state (SubscriptionState!)

The new state of the subscription.

\n\n\n\n\n\n\n\n\n\n\n\n

subscribableId (ID!)

The Node ID of the subscribable object to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamDiscussionCommentInput

\n

Autogenerated input type of UpdateTeamDiscussionComment.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String!)

The updated text of the comment.

\n\n\n\n\n\n\n\n\n\n\n\n

bodyVersion (String)

The current version of the body content.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The ID of the comment to modify.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamDiscussionInput

\n

Autogenerated input type of UpdateTeamDiscussion.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

body (String)

The updated text of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

bodyVersion (String)

The current version of the body content. If provided, this update operation\nwill be rejected if the given version does not match the latest version on the server.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the discussion to modify.

\n\n\n\n\n\n\n\n\n\n\n\n

pinned (Boolean)

If provided, sets the pinned state of the updated discussion.

\n\n\n\n\n\n\n\n\n\n\n\n

title (String)

The updated title of the discussion.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamReviewAssignmentInput

\n

Autogenerated input type of UpdateTeamReviewAssignment.

\n
\n\n
\n \n
\n

Preview notice

\n

UpdateTeamReviewAssignmentInput is available under the Team review assignments preview. During the preview period, the API may change without notice.

\n
\n\n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

algorithm (TeamReviewAssignmentAlgorithm)

The algorithm to use for review assignment.

\n\n\n\n\n\n\n\n\n\n\n\n

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

enabled (Boolean!)

Turn on or off review assignment.

\n\n\n\n\n\n\n\n\n\n\n\n

excludedTeamMemberIds ([ID!])

An array of team member IDs to exclude.

\n\n\n\n\n\n\n\n\n\n\n\n

id (ID!)

The Node ID of the team to update review assignments of.

\n\n\n\n\n\n\n\n\n\n\n\n

notifyTeam (Boolean)

Notify the entire team of the PR if it is delegated.

\n\n\n\n\n\n\n\n\n\n\n\n

teamMemberCount (Int)

The number of team members to assign.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTeamsRepositoryInput

\n

Autogenerated input type of UpdateTeamsRepository.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

permission (RepositoryPermission!)

Permission that should be granted to the teams.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

Repository ID being granted access to.

\n\n\n\n\n\n\n\n\n\n\n\n

teamIds ([ID!]!)

A list of teams being granted access. Limit: 10.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUpdateTopicsInput

\n

Autogenerated input type of UpdateTopics.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

clientMutationId (String)

A unique identifier for the client performing the mutation.

\n\n\n\n\n\n\n\n\n\n\n\n

repositoryId (ID!)

The Node ID of the repository.

\n\n\n\n\n\n\n\n\n\n\n\n

topicNames ([String!]!)

An array of topic names.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n\n
\n
\n

\n \n \nUserStatusOrder

\n

Ordering options for user status connections.

\n
\n\n
\n \n \n\n\n

Input fields

\n \n\n\n \n \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameDescription

direction (OrderDirection!)

The ordering direction.

\n\n\n\n\n\n\n\n\n\n\n\n

field (UserStatusOrderField!)

The field to order user statuses by.

\n\n\n\n\n\n\n\n\n\n\n\n
\n\n
\n
\n", "miniToc": [ { "contents": "\n AbortQueuedMigrationsInput", diff --git a/lib/graphql/static/schema-dotcom.json b/lib/graphql/static/schema-dotcom.json index 5087fe23e1..e5c9b0e37a 100644 --- a/lib/graphql/static/schema-dotcom.json +++ b/lib/graphql/static/schema-dotcom.json @@ -76417,7 +76417,7 @@ }, { "name": "pushActorIds", - "description": "

A list of User, Team or App IDs allowed to push to matching branches.

", + "description": "

A list of User, Team, or App IDs allowed to push to matching branches.

", "type": "[ID!]", "id": "id", "kind": "scalars", @@ -82172,7 +82172,7 @@ }, { "name": "pushActorIds", - "description": "

A list of User, Team or App IDs allowed to push to matching branches.

", + "description": "

A list of User, Team, or App IDs allowed to push to matching branches.

", "type": "[ID!]", "id": "id", "kind": "scalars", diff --git a/lib/graphql/static/schema-ghae.json b/lib/graphql/static/schema-ghae.json index aa6d23cb27..246acebb4e 100644 --- a/lib/graphql/static/schema-ghae.json +++ b/lib/graphql/static/schema-ghae.json @@ -66310,7 +66310,7 @@ }, { "name": "pushActorIds", - "description": "

A list of User, Team or App IDs allowed to push to matching branches.

", + "description": "

A list of User, Team, or App IDs allowed to push to matching branches.

", "type": "[ID!]", "id": "id", "kind": "scalars", @@ -71023,7 +71023,7 @@ }, { "name": "pushActorIds", - "description": "

A list of User, Team or App IDs allowed to push to matching branches.

", + "description": "

A list of User, Team, or App IDs allowed to push to matching branches.

", "type": "[ID!]", "id": "id", "kind": "scalars", diff --git a/lib/graphql/static/schema-ghec.json b/lib/graphql/static/schema-ghec.json index 5087fe23e1..e5c9b0e37a 100644 --- a/lib/graphql/static/schema-ghec.json +++ b/lib/graphql/static/schema-ghec.json @@ -76417,7 +76417,7 @@ }, { "name": "pushActorIds", - "description": "

A list of User, Team or App IDs allowed to push to matching branches.

", + "description": "

A list of User, Team, or App IDs allowed to push to matching branches.

", "type": "[ID!]", "id": "id", "kind": "scalars", @@ -82172,7 +82172,7 @@ }, { "name": "pushActorIds", - "description": "

A list of User, Team or App IDs allowed to push to matching branches.

", + "description": "

A list of User, Team, or App IDs allowed to push to matching branches.

", "type": "[ID!]", "id": "id", "kind": "scalars", diff --git a/lib/redirects/static/redirect-exceptions.txt b/lib/redirects/static/redirect-exceptions.txt index 2541000fca..4228a87474 100644 --- a/lib/redirects/static/redirect-exceptions.txt +++ b/lib/redirects/static/redirect-exceptions.txt @@ -539,4 +539,9 @@ - /articles/enabling-githubcom-repository-search-in-github-enterprise-server - /github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server - /github/searching-for-information-on-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-in-github-enterprise-server -- /enterprise-cloud@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment \ No newline at end of file +- /enterprise-cloud@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment + +/enterprise-cloud@latest/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization +- /enterprise-server@3.3/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization +- /enterprise-server@3.4/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization +- /enterprise-server@3.5/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization \ No newline at end of file diff --git a/lib/rest/static/apps/enabled-for-apps.json b/lib/rest/static/apps/enabled-for-apps.json index 5f0355ad32..eca5606544 100644 --- a/lib/rest/static/apps/enabled-for-apps.json +++ b/lib/rest/static/apps/enabled-for-apps.json @@ -21181,6 +21181,12 @@ "verb": "patch", "requestPath": "/orgs/{org}" }, + { + "slug": "get-the-audit-log-for-an-organization", + "subcategory": "orgs", + "verb": "get", + "requestPath": "/orgs/{org}/audit-log" + }, { "slug": "list-organization-webhooks", "subcategory": "webhooks", diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json index b801eacd11..12fe7e2293 100644 --- a/lib/rest/static/decorated/api.github.com.json +++ b/lib/rest/static/decorated/api.github.com.json @@ -29055,6 +29055,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -29069,6 +29076,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -33910,6 +33943,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -34013,8 +34047,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -34046,6 +34081,22 @@ "site_admin": false }, "run_attempt": 1, + "referenced_workflows": [ + { + "path": "octocat/Hello-World/.github/workflows/deploy.yml@main", + "sha": "86e8bc9ecf7d38b1ed2d2cfb8eb87ba9b35b01db", + "ref": "refs/heads/main" + }, + { + "path": "octo-org/octo-repo/.github/workflows/report.yml@v2", + "sha": "79e9790903e1c3373b1a3e3a941d57405478a232", + "ref": "refs/tags/v2" + }, + { + "path": "octo-org/octo-repo/.github/workflows/secure.yml@1595d4b6de6a9e9751fb270a41019ce507d4099e", + "sha": "1595d4b6de6a9e9751fb270a41019ce507d4099e" + } + ], "run_started_at": "2020-01-22T19:33:08Z", "triggering_actor": { "login": "octocat", @@ -34073,6 +34124,7 @@ "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", + "previous_attempt_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/attempts/1", "workflow_url": "https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038", "head_commit": { "id": "acb5820ced9479c074f688cc328bf03f341a511d", @@ -34283,6 +34335,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -34297,6 +34356,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -39138,6 +39223,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -39741,8 +39827,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -39774,6 +39861,22 @@ "site_admin": false }, "run_attempt": 1, + "referenced_workflows": [ + { + "path": "octocat/Hello-World/.github/workflows/deploy.yml@main", + "sha": "86e8bc9ecf7d38b1ed2d2cfb8eb87ba9b35b01db", + "ref": "refs/heads/main" + }, + { + "path": "octo-org/octo-repo/.github/workflows/report.yml@v2", + "sha": "79e9790903e1c3373b1a3e3a941d57405478a232", + "ref": "refs/tags/v2" + }, + { + "path": "octo-org/octo-repo/.github/workflows/secure.yml@1595d4b6de6a9e9751fb270a41019ce507d4099e", + "sha": "1595d4b6de6a9e9751fb270a41019ce507d4099e" + } + ], "run_started_at": "2020-01-22T19:33:08Z", "triggering_actor": { "login": "octocat", @@ -39801,6 +39904,7 @@ "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", + "previous_attempt_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/attempts/1", "workflow_url": "https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038", "head_commit": { "id": "acb5820ced9479c074f688cc328bf03f341a511d", @@ -40011,6 +40115,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -40025,6 +40136,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -44866,6 +45003,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -47404,6 +47542,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -47418,6 +47563,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -52259,6 +52430,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -99738,7 +99910,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -105661,7 +105833,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -467088,7 +467260,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" @@ -470054,7 +470226,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" @@ -473020,7 +473192,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" @@ -509618,6 +509790,7 @@ "example": [ { "id": 3, + "name": "mastahyeti's GPG Key", "primary_key_id": 2, "key_id": "3262EFF25BA0D270", "public_key": "xsBNBFayYZ...", @@ -509640,7 +509813,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": "2016-03-24T11:31:04-07:00" + "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false } ], "can_sign": true, @@ -509649,6 +509823,7 @@ "can_certify": true, "created_at": "2016-03-24T11:31:04-06:00", "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false, "raw_key": "string" } ], @@ -509665,6 +509840,15 @@ 3 ] }, + "name": { + "type": [ + "string", + "null" + ], + "examples": [ + "mastahyeti's GPG Key" + ] + }, "primary_key_id": { "type": [ "integer", @@ -509754,6 +509938,9 @@ "string", "null" ] + }, + "revoked": { + "type": "boolean" } } }, @@ -509770,7 +509957,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": null + "expires_at": null, + "revoked": false } ] }, @@ -509806,6 +509994,12 @@ ], "format": "date-time" }, + "revoked": { + "type": "boolean", + "examples": [ + true + ] + }, "raw_key": { "type": [ "string", @@ -509826,7 +510020,8 @@ "can_encrypt_storage", "can_certify", "emails", - "subkeys" + "subkeys", + "revoked" ] } } @@ -509867,6 +510062,16 @@ "subcategory": "gpg-keys", "parameters": [], "bodyParameters": [ + { + "description": "

A descriptive name for the new key.

", + "type": "string", + "name": "name", + "in": "body", + "rawType": "string", + "rawDescription": "A descriptive name for the new key.", + "isRequired": false, + "childParamsGroups": [] + }, { "description": "

A GPG key in ASCII-armored format.

", "type": "string", @@ -509893,6 +510098,7 @@ "description": "

Response

", "example": { "id": 3, + "name": "mastahyeti's GPG Key", "primary_key_id": 2, "key_id": "3262EFF25BA0D270", "public_key": "xsBNBFayYZ...", @@ -509915,7 +510121,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": "2016-03-24T11:31:04-07:00" + "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false } ], "can_sign": true, @@ -509924,6 +510131,7 @@ "can_certify": true, "created_at": "2016-03-24T11:31:04-06:00", "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false, "raw_key": "\"-----BEGIN PGP PUBLIC KEY BLOCK-----\\nVersion: GnuPG v2\\n\\nmQENBFayYZ0BCAC4hScoJXXpyR+MXGcrBxElqw3FzCVvkViuyeko+Jp76QJhg8kr\\nucRTxbnOoHfda/FmilEa/wxf9ch5/PSrrL26FxEoPHhJolp8fnIDLQeITn94NYdB\\nZtnnEKslpPrG97qSUWIchvyqCPtvOb8+8fWvGx9K/ZWcEEdh1X8+WFR2jMENMeoX\\nwxHWQoPnS7LpX/85/M7VUcJxvDVfv+eHsnQupmE5bGarKNih0oMe3LbdN3qA5PTz\\nSCm6Iudar1VsQ+xTz08ymL7t4pnEtLguQ7EyatFHCjxNblv5RzxoL0tDgN3HqoDz\\nc7TEA+q4RtDQl9amcvQ95emnXmZ974u7UkYdABEBAAG0HlNvbWUgVXNlciA8c29t\\nZXVzZXJAZ21haWwuY29tPokBOAQTAQIAIgUCVrJhnQIbAwYLCQgHAwIGFQgCCQoL\\nBBYCAwECHgECF4AACgkQMmLv8lug0nAViQgArWjI55+7p48URr2z9Jvak+yrBTx1\\nzkufltQAnHTJkq+Kl9dySSmTnOop8o3rE4++IOpYV5Y36PkKf9EZMk4n1RQiDPKE\\nAFtRVTkRaoWzOir9KQXJPfhKrl01j/QzY+utfiMvUoBJZ9ybq8Pa885SljW9lbaX\\nIYw+hl8ZdJ2KStvGrEyfQvRyq3aN5c9TV//4BdGnwx7Qabq/U+G18lizG6f/yq15\\ned7t0KELaCfeKPvytp4VE9/z/Ksah/h3+Qilx07/oG2Ae5kC1bEC9coD/ogPUhbv\\nb2bsBIoY9E9YwsLoif2lU+o1t76zLgUktuNscRRUKobW028H1zuFS/XQhrkBDQRW\\nsmGdAQgApnyyv3i144OLYy0O4UKQxd3e10Y3WpDwfnGIBefAI1m7RxnUxBag/DsU\\n7gi9qLEC4VHSfq4eiNfr1LJOyCL2edTgCWFgBhVjbXjZe6YAOrAnhxwCErnN0Y7N\\n6s8wVh9fObSOyf8ZE6G7JeKpcq9Q6gd/KxagfD48a1v+fyRHpyQc6J9pUEmtrDJ7\\nBjmsd2VWzLBvNWdHyxDNtZweIaqIO9VUYYpr1mtTliNBOZLUelmgrt7HBRcJpWMA\\nS8muVVbuP5MK0trLBq/JB8qUH3zRzB/PhMgzmkIfjEK1VYDWm4E8DYyTWEJcHqkb\\neqFsNjrIlwPaA122BWC6gUOPwwH+oQARAQABiQEfBBgBAgAJBQJWsmGdAhsMAAoJ\\nEDJi7/JboNJwAyAIALd4xcdmGbZD98gScJzqwzkOMcO8zFHqHNvJ42xIFvGny7c0\\n1Rx7iyrdypOby5AxE+viQcjG4rpLZW/xKYBNGrCfDyQO7511I0v8x20EICMlMfD/\\nNrWQCzesEPcUlKTP07d+sFyP8AyseOidbzY/92CpskTgdSBjY/ntLSaoknl/fjJE\\nQM8OkPqU7IraO1Jzzdnm20d5PZL9+PIwIWdSTedU/vBMTJyNcoqvSfKf1wNC66XP\\nhqfYgXJE564AdWZKA3C0IyCqiv+LHwxLnUHio1a4/r91C8KPzxs6tGxRDjXLd7ms\\nuYFGWymiUGOE/giHlcxdYcHzwLnPDliMQOLiTkK5AQ0EVuxMygEIAOD+bW1cDTmE\\nBxh5JECoqeHuwgl6DlLhnubWPkQ4ZeRzBRAsFcEJQlwlJjrzFDicL+lnm6Qq4tt0\\n560TwHdf15/AKTZIZu7H25axvGNzgeaUkJEJdYAq9zTKWwX7wKyzBszi485nQg97\\nMfAqwhMpDW0Qqf8+7Ug+WEmfBSGv9uL3aQC6WEeIsHfri0n0n8v4XgwhfShXguxO\\nCsOztEsuW7WWKW9P4TngKKv4lCHdPlV6FwxeMzODBJvc2fkHVHnqc0PqszJ5xcF8\\n6gZCpMM027SbpeYWCAD5zwJyYP9ntfO1p2HjnQ1dZaP9FeNcO7uIV1Lnd1eGCu6I\\nsrVp5k1f3isAEQEAAYkCPgQYAQIACQUCVuxMygIbAgEpCRAyYu/yW6DScMBdIAQZ\\nAQIABgUCVuxMygAKCRCKohN4dhq2b4tcCACHxmOHVXNpu47OvUGYQydLgMACUlXN\\nlj+HfE0VReqShxdDmpasAY9IRpuMB2RsGK8GbNP+4SlOlAiPf5SMhS7nZNkNDgQQ\\naZ3HFpgrFmFwmE10BKT4iQtoxELLM57z0qGOAfTsEjWFQa4sF+6IHAQR/ptkdkkI\\nBUEXiMnAwVwBysLIJiLO8qdjB6qp52QkT074JVrwywT/P+DkMfC2k4r/AfEbf6eF\\ndmPDuPk6KD87+hJZsSa5MaMUBQVvRO/mgEkhJRITVu58eWGaBOcQJ8gqurhCqM5P\\nDfUA4TJ7wiqM6sS764vV1rOioTTXkszzhClQqET7hPVnVQjenYgv0EZHNyQH/1f1\\n/CYqvV1vFjM9vJjMbxXsATCkZe6wvBVKD8vLsJAr8N+onKQz+4OPc3kmKq7aESu3\\nCi/iuie5KKVwnuNhr9AzT61vEkKxwHcVFEvHB77F6ZAAInhRvjzmQbD2dlPLLQCC\\nqDj71ODSSAPTEmUy6969bgD9PfWei7kNkBIx7s3eBv8yzytSc2EcuUgopqFazquw\\nFs1+tqGHjBvQfTo6bqbJjp/9Ci2pvde3ElV2rAgUlb3lqXyXjRDqrXosh5GcRPQj\\nK8Nhj1BNhnrCVskE4BP0LYbOHuzgm86uXwGCFsY+w2VOsSm16Jx5GHyG5S5WU3+D\\nIts/HFYRLiFgDLmTlxo=\\n=+OzK\\n-----END PGP PUBLIC KEY BLOCK-----\"" }, "schema": { @@ -509937,6 +510145,15 @@ 3 ] }, + "name": { + "type": [ + "string", + "null" + ], + "examples": [ + "mastahyeti's GPG Key" + ] + }, "primary_key_id": { "type": [ "integer", @@ -510026,6 +510243,9 @@ "string", "null" ] + }, + "revoked": { + "type": "boolean" } } }, @@ -510042,7 +510262,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": null + "expires_at": null, + "revoked": false } ] }, @@ -510078,6 +510299,12 @@ ], "format": "date-time" }, + "revoked": { + "type": "boolean", + "examples": [ + true + ] + }, "raw_key": { "type": [ "string", @@ -510098,7 +510325,8 @@ "can_encrypt_storage", "can_certify", "emails", - "subkeys" + "subkeys", + "revoked" ] } } @@ -510169,6 +510397,7 @@ "description": "

Response

", "example": { "id": 3, + "name": "mastahyeti's GPG Key", "primary_key_id": 2, "key_id": "3262EFF25BA0D270", "public_key": "xsBNBFayYZ...", @@ -510191,7 +510420,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": "2016-03-24T11:31:04-07:00" + "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false } ], "can_sign": true, @@ -510200,6 +510430,7 @@ "can_certify": true, "created_at": "2016-03-24T11:31:04-06:00", "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false, "raw_key": "\"-----BEGIN PGP PUBLIC KEY BLOCK-----\\nVersion: GnuPG v2\\n\\nmQENBFayYZ0BCAC4hScoJXXpyR+MXGcrBxElqw3FzCVvkViuyeko+Jp76QJhg8kr\\nucRTxbnOoHfda/FmilEa/wxf9ch5/PSrrL26FxEoPHhJolp8fnIDLQeITn94NYdB\\nZtnnEKslpPrG97qSUWIchvyqCPtvOb8+8fWvGx9K/ZWcEEdh1X8+WFR2jMENMeoX\\nwxHWQoPnS7LpX/85/M7VUcJxvDVfv+eHsnQupmE5bGarKNih0oMe3LbdN3qA5PTz\\nSCm6Iudar1VsQ+xTz08ymL7t4pnEtLguQ7EyatFHCjxNblv5RzxoL0tDgN3HqoDz\\nc7TEA+q4RtDQl9amcvQ95emnXmZ974u7UkYdABEBAAG0HlNvbWUgVXNlciA8c29t\\nZXVzZXJAZ21haWwuY29tPokBOAQTAQIAIgUCVrJhnQIbAwYLCQgHAwIGFQgCCQoL\\nBBYCAwECHgECF4AACgkQMmLv8lug0nAViQgArWjI55+7p48URr2z9Jvak+yrBTx1\\nzkufltQAnHTJkq+Kl9dySSmTnOop8o3rE4++IOpYV5Y36PkKf9EZMk4n1RQiDPKE\\nAFtRVTkRaoWzOir9KQXJPfhKrl01j/QzY+utfiMvUoBJZ9ybq8Pa885SljW9lbaX\\nIYw+hl8ZdJ2KStvGrEyfQvRyq3aN5c9TV//4BdGnwx7Qabq/U+G18lizG6f/yq15\\ned7t0KELaCfeKPvytp4VE9/z/Ksah/h3+Qilx07/oG2Ae5kC1bEC9coD/ogPUhbv\\nb2bsBIoY9E9YwsLoif2lU+o1t76zLgUktuNscRRUKobW028H1zuFS/XQhrkBDQRW\\nsmGdAQgApnyyv3i144OLYy0O4UKQxd3e10Y3WpDwfnGIBefAI1m7RxnUxBag/DsU\\n7gi9qLEC4VHSfq4eiNfr1LJOyCL2edTgCWFgBhVjbXjZe6YAOrAnhxwCErnN0Y7N\\n6s8wVh9fObSOyf8ZE6G7JeKpcq9Q6gd/KxagfD48a1v+fyRHpyQc6J9pUEmtrDJ7\\nBjmsd2VWzLBvNWdHyxDNtZweIaqIO9VUYYpr1mtTliNBOZLUelmgrt7HBRcJpWMA\\nS8muVVbuP5MK0trLBq/JB8qUH3zRzB/PhMgzmkIfjEK1VYDWm4E8DYyTWEJcHqkb\\neqFsNjrIlwPaA122BWC6gUOPwwH+oQARAQABiQEfBBgBAgAJBQJWsmGdAhsMAAoJ\\nEDJi7/JboNJwAyAIALd4xcdmGbZD98gScJzqwzkOMcO8zFHqHNvJ42xIFvGny7c0\\n1Rx7iyrdypOby5AxE+viQcjG4rpLZW/xKYBNGrCfDyQO7511I0v8x20EICMlMfD/\\nNrWQCzesEPcUlKTP07d+sFyP8AyseOidbzY/92CpskTgdSBjY/ntLSaoknl/fjJE\\nQM8OkPqU7IraO1Jzzdnm20d5PZL9+PIwIWdSTedU/vBMTJyNcoqvSfKf1wNC66XP\\nhqfYgXJE564AdWZKA3C0IyCqiv+LHwxLnUHio1a4/r91C8KPzxs6tGxRDjXLd7ms\\nuYFGWymiUGOE/giHlcxdYcHzwLnPDliMQOLiTkK5AQ0EVuxMygEIAOD+bW1cDTmE\\nBxh5JECoqeHuwgl6DlLhnubWPkQ4ZeRzBRAsFcEJQlwlJjrzFDicL+lnm6Qq4tt0\\n560TwHdf15/AKTZIZu7H25axvGNzgeaUkJEJdYAq9zTKWwX7wKyzBszi485nQg97\\nMfAqwhMpDW0Qqf8+7Ug+WEmfBSGv9uL3aQC6WEeIsHfri0n0n8v4XgwhfShXguxO\\nCsOztEsuW7WWKW9P4TngKKv4lCHdPlV6FwxeMzODBJvc2fkHVHnqc0PqszJ5xcF8\\n6gZCpMM027SbpeYWCAD5zwJyYP9ntfO1p2HjnQ1dZaP9FeNcO7uIV1Lnd1eGCu6I\\nsrVp5k1f3isAEQEAAYkCPgQYAQIACQUCVuxMygIbAgEpCRAyYu/yW6DScMBdIAQZ\\nAQIABgUCVuxMygAKCRCKohN4dhq2b4tcCACHxmOHVXNpu47OvUGYQydLgMACUlXN\\nlj+HfE0VReqShxdDmpasAY9IRpuMB2RsGK8GbNP+4SlOlAiPf5SMhS7nZNkNDgQQ\\naZ3HFpgrFmFwmE10BKT4iQtoxELLM57z0qGOAfTsEjWFQa4sF+6IHAQR/ptkdkkI\\nBUEXiMnAwVwBysLIJiLO8qdjB6qp52QkT074JVrwywT/P+DkMfC2k4r/AfEbf6eF\\ndmPDuPk6KD87+hJZsSa5MaMUBQVvRO/mgEkhJRITVu58eWGaBOcQJ8gqurhCqM5P\\nDfUA4TJ7wiqM6sS764vV1rOioTTXkszzhClQqET7hPVnVQjenYgv0EZHNyQH/1f1\\n/CYqvV1vFjM9vJjMbxXsATCkZe6wvBVKD8vLsJAr8N+onKQz+4OPc3kmKq7aESu3\\nCi/iuie5KKVwnuNhr9AzT61vEkKxwHcVFEvHB77F6ZAAInhRvjzmQbD2dlPLLQCC\\nqDj71ODSSAPTEmUy6969bgD9PfWei7kNkBIx7s3eBv8yzytSc2EcuUgopqFazquw\\nFs1+tqGHjBvQfTo6bqbJjp/9Ci2pvde3ElV2rAgUlb3lqXyXjRDqrXosh5GcRPQj\\nK8Nhj1BNhnrCVskE4BP0LYbOHuzgm86uXwGCFsY+w2VOsSm16Jx5GHyG5S5WU3+D\\nIts/HFYRLiFgDLmTlxo=\\n=+OzK\\n-----END PGP PUBLIC KEY BLOCK-----\"" }, "schema": { @@ -510213,6 +510444,15 @@ 3 ] }, + "name": { + "type": [ + "string", + "null" + ], + "examples": [ + "mastahyeti's GPG Key" + ] + }, "primary_key_id": { "type": [ "integer", @@ -510302,6 +510542,9 @@ "string", "null" ] + }, + "revoked": { + "type": "boolean" } } }, @@ -510318,7 +510561,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": null + "expires_at": null, + "revoked": false } ] }, @@ -510354,6 +510598,12 @@ ], "format": "date-time" }, + "revoked": { + "type": "boolean", + "examples": [ + true + ] + }, "raw_key": { "type": [ "string", @@ -510374,7 +510624,8 @@ "can_encrypt_storage", "can_certify", "emails", - "subkeys" + "subkeys", + "revoked" ] } } @@ -510525,6 +510776,7 @@ "example": [ { "id": 3, + "name": "mastahyeti's GPG Key", "primary_key_id": 2, "key_id": "3262EFF25BA0D270", "public_key": "xsBNBFayYZ...", @@ -510547,7 +510799,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": "2016-03-24T11:31:04-07:00" + "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false } ], "can_sign": true, @@ -510556,6 +510809,7 @@ "can_certify": true, "created_at": "2016-03-24T11:31:04-06:00", "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false, "raw_key": "string" } ], @@ -510572,6 +510826,15 @@ 3 ] }, + "name": { + "type": [ + "string", + "null" + ], + "examples": [ + "mastahyeti's GPG Key" + ] + }, "primary_key_id": { "type": [ "integer", @@ -510661,6 +510924,9 @@ "string", "null" ] + }, + "revoked": { + "type": "boolean" } } }, @@ -510677,7 +510943,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": null + "expires_at": null, + "revoked": false } ] }, @@ -510713,6 +510980,12 @@ ], "format": "date-time" }, + "revoked": { + "type": "boolean", + "examples": [ + true + ] + }, "raw_key": { "type": [ "string", @@ -510733,7 +511006,8 @@ "can_encrypt_storage", "can_certify", "emails", - "subkeys" + "subkeys", + "revoked" ] } } diff --git a/lib/rest/static/decorated/ghes-3.1.json b/lib/rest/static/decorated/ghes-3.1.json index 9a68774036..e99d1355c7 100644 --- a/lib/rest/static/decorated/ghes-3.1.json +++ b/lib/rest/static/decorated/ghes-3.1.json @@ -24377,16 +24377,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -28665,6 +28655,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -28768,8 +28759,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -29194,16 +29186,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -33482,6 +33464,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -34450,16 +34433,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -38738,6 +38711,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -83129,7 +83103,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -87583,7 +87557,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -153966,7 +153940,7 @@ } } ], - "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.

", "statusCodes": [ { "httpStatusCode": "200", @@ -159837,11 +159811,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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"About authentication for your enterprise.\"

", "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://docs.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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"[About authentication for your enterprise](https://docs.github.com/enterprise-server@3.1/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise).\"", "isRequired": false, "childParamsGroups": [] } @@ -161956,11 +161930,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://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.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.1/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.", "isRequired": false, "childParamsGroups": [] } @@ -161984,7 +161958,7 @@ } ], "previews": [], - "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.\"

", "statusCodes": [ { "httpStatusCode": "204", @@ -162013,11 +161987,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://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.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.1/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.", "isRequired": false, "childParamsGroups": [] } @@ -162041,7 +162015,7 @@ } ], "previews": [], - "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.

", "statusCodes": [ { "httpStatusCode": "204", @@ -362393,7 +362367,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" diff --git a/lib/rest/static/decorated/ghes-3.2.json b/lib/rest/static/decorated/ghes-3.2.json index 4d2e4e863b..2af626b234 100644 --- a/lib/rest/static/decorated/ghes-3.2.json +++ b/lib/rest/static/decorated/ghes-3.2.json @@ -25028,16 +25028,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -29338,6 +29328,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -29441,8 +29432,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -29867,16 +29859,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -34177,6 +34159,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -36885,16 +36868,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -41195,6 +41168,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -86273,7 +86247,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -90727,7 +90701,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -159686,7 +159660,7 @@ } } ], - "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.

", "statusCodes": [ { "httpStatusCode": "200", @@ -165564,11 +165538,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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"About authentication for your enterprise.\"

", "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://docs.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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"[About authentication for your enterprise](https://docs.github.com/enterprise-server@3.2/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise).\"", "isRequired": false, "childParamsGroups": [] } @@ -167699,11 +167673,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://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.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.2/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.", "isRequired": false, "childParamsGroups": [] } @@ -167727,7 +167701,7 @@ } ], "previews": [], - "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.\"

", "statusCodes": [ { "httpStatusCode": "204", @@ -167756,11 +167730,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://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.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.2/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.", "isRequired": false, "childParamsGroups": [] } @@ -167784,7 +167758,7 @@ } ], "previews": [], - "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.

", "statusCodes": [ { "httpStatusCode": "204", @@ -370879,7 +370853,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" diff --git a/lib/rest/static/decorated/ghes-3.3.json b/lib/rest/static/decorated/ghes-3.3.json index 1a97168db5..e25f8c0c49 100644 --- a/lib/rest/static/decorated/ghes-3.3.json +++ b/lib/rest/static/decorated/ghes-3.3.json @@ -25165,16 +25165,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -29475,6 +29465,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -29578,8 +29569,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -30004,16 +29996,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -34314,6 +34296,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -37022,16 +37005,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -41332,6 +41305,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -86511,7 +86485,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -90951,7 +90925,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -160311,7 +160285,7 @@ } ], "previews": [], - "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.

", "statusCodes": [ { "httpStatusCode": "200", @@ -166146,11 +166120,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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"About authentication for your enterprise.\"

", "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://docs.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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"[About authentication for your enterprise](https://docs.github.com/enterprise-server@3.3/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise).\"", "isRequired": false, "childParamsGroups": [] } @@ -168281,11 +168255,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://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.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.3/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.", "isRequired": false, "childParamsGroups": [] } @@ -168309,7 +168283,7 @@ } ], "previews": [], - "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.\"

", "statusCodes": [ { "httpStatusCode": "204", @@ -168338,11 +168312,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://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.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.3/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.", "isRequired": false, "childParamsGroups": [] } @@ -168366,7 +168340,7 @@ } ], "previews": [], - "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.

", "statusCodes": [ { "httpStatusCode": "204", @@ -366583,7 +366557,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" @@ -369535,7 +369509,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" diff --git a/lib/rest/static/decorated/ghes-3.4.json b/lib/rest/static/decorated/ghes-3.4.json index ada620bdf8..34861dafc2 100644 --- a/lib/rest/static/decorated/ghes-3.4.json +++ b/lib/rest/static/decorated/ghes-3.4.json @@ -27298,16 +27298,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -31608,6 +31598,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -31711,8 +31702,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -32137,16 +32129,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -36447,6 +36429,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -39155,16 +39138,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -43465,6 +43438,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -87445,7 +87419,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -93368,7 +93342,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -166524,7 +166498,7 @@ } ], "previews": [], - "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.

", "statusCodes": [ { "httpStatusCode": "200", @@ -172351,11 +172325,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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"About authentication for your enterprise.\"

", "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://docs.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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"[About authentication for your enterprise](https://docs.github.com/enterprise-server@3.4/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise).\"", "isRequired": false, "childParamsGroups": [] } @@ -174470,11 +174444,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://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.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.4/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.", "isRequired": false, "childParamsGroups": [] } @@ -174498,7 +174472,7 @@ } ], "previews": [], - "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.\"

", "statusCodes": [ { "httpStatusCode": "204", @@ -174527,11 +174501,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://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.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.4/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.", "isRequired": false, "childParamsGroups": [] } @@ -174555,7 +174529,7 @@ } ], "previews": [], - "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.

", "statusCodes": [ { "httpStatusCode": "204", @@ -384793,7 +384767,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" @@ -387745,7 +387719,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" @@ -390697,7 +390671,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" diff --git a/lib/rest/static/decorated/ghes-3.5.json b/lib/rest/static/decorated/ghes-3.5.json index 502924a81d..fe3936e2cb 100644 --- a/lib/rest/static/decorated/ghes-3.5.json +++ b/lib/rest/static/decorated/ghes-3.5.json @@ -33861,6 +33861,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -33964,12 +33965,12 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "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", @@ -34024,6 +34025,7 @@ "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", + "previous_attempt_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/attempts/1", "workflow_url": "https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038", "head_commit": { "id": "acb5820ced9479c074f688cc328bf03f341a511d", @@ -39089,6 +39091,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -39619,12 +39622,12 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "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", @@ -39679,6 +39682,7 @@ "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", + "previous_attempt_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/attempts/1", "workflow_url": "https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038", "head_commit": { "id": "acb5820ced9479c074f688cc328bf03f341a511d", @@ -44744,6 +44748,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -51879,6 +51884,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -95889,7 +95895,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -101812,7 +101818,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -178331,7 +178337,7 @@ } ], "previews": [], - "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.

", "statusCodes": [ { "httpStatusCode": "200", @@ -184158,11 +184164,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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"About authentication for your enterprise.\"

", "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://docs.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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"[About authentication for your enterprise](https://docs.github.com/enterprise-server@3.5/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise).\"", "isRequired": false, "childParamsGroups": [] } @@ -186277,11 +186283,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://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.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.5/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.", "isRequired": false, "childParamsGroups": [] } @@ -186305,7 +186311,7 @@ } ], "previews": [], - "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.\"

", "statusCodes": [ { "httpStatusCode": "204", @@ -186334,11 +186340,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://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.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.5/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.", "isRequired": false, "childParamsGroups": [] } @@ -186362,7 +186368,7 @@ } ], "previews": [], - "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.

", "statusCodes": [ { "httpStatusCode": "204", @@ -397065,7 +397071,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" @@ -400031,7 +400037,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" @@ -402997,7 +403003,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json index 2a66c05229..26e3ecf40c 100644 --- a/lib/rest/static/decorated/github.ae.json +++ b/lib/rest/static/decorated/github.ae.json @@ -21555,6 +21555,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -21569,6 +21576,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -26410,6 +26443,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -26513,8 +26547,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -26546,6 +26581,22 @@ "site_admin": false }, "run_attempt": 1, + "referenced_workflows": [ + { + "path": "octocat/Hello-World/.github/workflows/deploy.yml@main", + "sha": "86e8bc9ecf7d38b1ed2d2cfb8eb87ba9b35b01db", + "ref": "refs/heads/main" + }, + { + "path": "octo-org/octo-repo/.github/workflows/report.yml@v2", + "sha": "79e9790903e1c3373b1a3e3a941d57405478a232", + "ref": "refs/tags/v2" + }, + { + "path": "octo-org/octo-repo/.github/workflows/secure.yml@1595d4b6de6a9e9751fb270a41019ce507d4099e", + "sha": "1595d4b6de6a9e9751fb270a41019ce507d4099e" + } + ], "run_started_at": "2020-01-22T19:33:08Z", "triggering_actor": { "login": "octocat", @@ -26573,6 +26624,7 @@ "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", + "previous_attempt_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/attempts/1", "workflow_url": "https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038", "head_commit": { "id": "acb5820ced9479c074f688cc328bf03f341a511d", @@ -26783,6 +26835,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -26797,6 +26856,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -31638,6 +31723,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -31813,8 +31899,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -31846,6 +31933,22 @@ "site_admin": false }, "run_attempt": 1, + "referenced_workflows": [ + { + "path": "octocat/Hello-World/.github/workflows/deploy.yml@main", + "sha": "86e8bc9ecf7d38b1ed2d2cfb8eb87ba9b35b01db", + "ref": "refs/heads/main" + }, + { + "path": "octo-org/octo-repo/.github/workflows/report.yml@v2", + "sha": "79e9790903e1c3373b1a3e3a941d57405478a232", + "ref": "refs/tags/v2" + }, + { + "path": "octo-org/octo-repo/.github/workflows/secure.yml@1595d4b6de6a9e9751fb270a41019ce507d4099e", + "sha": "1595d4b6de6a9e9751fb270a41019ce507d4099e" + } + ], "run_started_at": "2020-01-22T19:33:08Z", "triggering_actor": { "login": "octocat", @@ -31873,6 +31976,7 @@ "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", + "previous_attempt_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/attempts/1", "workflow_url": "https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038", "head_commit": { "id": "acb5820ced9479c074f688cc328bf03f341a511d", @@ -32083,6 +32187,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -32097,6 +32208,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -36938,6 +37075,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -37993,6 +38131,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -38007,6 +38152,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -42848,6 +43019,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -83295,7 +83467,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -89218,7 +89390,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -157308,6 +157480,406 @@ ] } ], + "audit-log": [ + { + "serverUrl": "https://HOSTNAME/api/v3", + "verb": "get", + "requestPath": "/enterprises/{enterprise}/audit-log", + "title": "Get the audit log for an enterprise", + "category": "enterprise-admin", + "subcategory": "audit-log", + "parameters": [ + { + "name": "enterprise", + "description": "

The slug version of the enterprise name. You can also substitute this value with the enterprise id.

", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "phrase", + "description": "

A search phrase. For more information, see Searching the audit log.

", + "in": "query", + "required": false, + "schema": { + "type": "string" + } + }, + { + "name": "after", + "description": "

A cursor, as given in the Link header. If specified, the query only searches for events after this cursor.

", + "in": "query", + "required": false, + "schema": { + "type": "string" + } + }, + { + "name": "before", + "description": "

A cursor, as given in the Link header. If specified, the query only searches for events before this cursor.

", + "in": "query", + "required": false, + "schema": { + "type": "string" + } + }, + { + "name": "order", + "description": "

The order of audit log events. To list newest events first, specify desc. To list oldest events first, specify asc.

\n

The default is desc.

", + "in": "query", + "required": false, + "schema": { + "type": "string", + "enum": [ + "desc", + "asc" + ] + } + }, + { + "name": "page", + "description": "

Page number of the results to fetch.

", + "in": "query", + "schema": { + "type": "integer", + "default": 1 + } + }, + { + "name": "per_page", + "description": "

The number of results per page (max 100).

", + "in": "query", + "schema": { + "type": "integer", + "default": 30 + } + } + ], + "bodyParameters": [], + "enabledForGitHubApps": false, + "codeExamples": [ + { + "key": "default", + "request": { + "description": "Example", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "enterprise": "ENTERPRISE" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/json", + "description": "

Response

", + "example": [ + { + "actor_ip": "88.123.45.123", + "from": "pull_requests#merge", + "device_cookie": null, + "actor": "mona-admin", + "actor_id": 7, + "repo": "octo-org/octo-repo", + "repo_id": 17, + "business": "github", + "business_id": 1, + "org": "octo-org", + "org_id": 8, + "action": "pull_request.merge", + "@timestamp": 1635940599755, + "created_at": 1635940599755, + "operation_type": "modify", + "actor_location": { + "country_code": "GB", + "country_name": "United Kingdom", + "region": "ENG", + "region_name": "England", + "city": "Louth", + "postal_code": "LN11", + "location": { + "lat": 53.4457, + "lon": 0.141 + } + }, + "data": { + "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) ...", + "method": "POST", + "request_id": "e4dabc4d-ba16-4bca-1234-649be7ae1188", + "server_id": "5d17aab5-fd9f-abcd-a820-16bed246441b", + "request_category": "other", + "controller_action": "merge", + "url": "https://example.com/octo-org/octo-repo/pull/1/merge", + "client_id": 322299977.1635936, + "referrer": "https://example.com/octo-org/octo-repo/pull/1", + "actor_session": 1, + "pull_request_id": 1, + "category_type": "Resource Management" + } + }, + { + "actor_ip": "88.123.45.123", + "from": "pull_request_review_events#create", + "device_cookie": null, + "actor": "mona-admin", + "actor_id": 7, + "business_id": 1, + "org_id": 8, + "action": "pull_request_review.submit", + "@timestamp": 1635940593079, + "created_at": 1635940593079, + "operation_type": "modify", + "actor_location": { + "country_code": "GB", + "country_name": "United Kingdom", + "region": "ENG", + "region_name": "England", + "city": "Louth", + "postal_code": "LN11", + "location": { + "lat": 53.4457, + "lon": 0.141 + } + }, + "data": { + "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) ...", + "method": "PUT", + "request_id": "c0f63bb7-17b6-4796-940c-12345c5a581b", + "server_id": "2abc1234-f651-43e3-9696-e942ad5f8c89", + "request_category": "other", + "controller_action": "create", + "url": "https://example.com/octo-org/octo-repo/pull/1/reviews", + "client_id": 322299977.1635936, + "referrer": "https://example.com/octo-org/octo-repo/pull/1/files", + "actor_session": 1, + "spammy": false, + "pull_request_id": 1, + "body": null, + "allowed": true, + "id": 1, + "state": 40, + "issue_id": 1, + "review_id": 1, + "category_type": "Resource Management" + } + }, + { + "actor_ip": "88.123.45.123", + "from": "pull_requests#create", + "device_cookie": null, + "actor": "mona", + "actor_id": 9, + "user_id": 9, + "repo": "octo-org/octo-repo", + "repo_id": 17, + "business": "github", + "business_id": 1, + "org": "octo-org", + "org_id": 8, + "action": "pull_request.create", + "@timestamp": 1635940554161, + "created_at": 1635940554161, + "operation_type": "create", + "actor_location": { + "country_code": "GB", + "country_name": "United Kingdom", + "region": "ENG", + "region_name": "England", + "city": "Louth", + "postal_code": "LN11", + "location": { + "lat": 53.4457, + "lon": 0.141 + } + }, + "data": { + "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) ...", + "method": "POST", + "request_id": "2773abeb-477f-4ebf-a017-f8e8a206c305", + "server_id": "796e3115-4ce8-4606-8fd0-99ea57a2e12b", + "request_category": "other", + "controller_action": "create", + "url": "https://example.com/octo-org/octo-repo/pull/create?base=octo-org%3Amain&head=mona%3Apatch-1", + "client_id": 386351111.163594, + "referrer": "https://example.com/octo-org/octo-repo/compare/main...mona:patch-1", + "actor_session": 2, + "pull_request_id": 1, + "category_type": "Resource Management" + } + } + ], + "schema": { + "type": "array", + "items": { + "type": "object", + "properties": { + "@timestamp": { + "type": "integer", + "description": "The time the audit log event occurred, given as a [Unix timestamp](http://en.wikipedia.org/wiki/Unix_time)." + }, + "action": { + "type": "string", + "description": "The name of the action that was performed, for example `user.login` or `repo.create`." + }, + "active": { + "type": "boolean" + }, + "active_was": { + "type": "boolean" + }, + "actor": { + "type": "string", + "description": "The actor who performed the action." + }, + "actor_id": { + "type": "integer", + "description": "The id of the actor who performed the action." + }, + "actor_location": { + "type": "object", + "properties": { + "country_name": { + "type": "string" + } + } + }, + "data": { + "type": "object", + "additionalProperties": true + }, + "org_id": { + "type": "integer" + }, + "blocked_user": { + "type": "string", + "description": "The username of the account being blocked." + }, + "business": { + "type": "string" + }, + "config": { + "type": "array", + "items": { + "type": "object" + } + }, + "config_was": { + "type": "array", + "items": { + "type": "object" + } + }, + "content_type": { + "type": "string" + }, + "created_at": { + "type": "integer", + "description": "The time the audit log event was recorded, given as a [Unix timestamp](http://en.wikipedia.org/wiki/Unix_time)." + }, + "deploy_key_fingerprint": { + "type": "string" + }, + "_document_id": { + "type": "string", + "description": "A unique identifier for an audit event." + }, + "emoji": { + "type": "string" + }, + "events": { + "type": "array", + "items": { + "type": "object" + } + }, + "events_were": { + "type": "array", + "items": { + "type": "object" + } + }, + "explanation": { + "type": "string" + }, + "fingerprint": { + "type": "string" + }, + "hook_id": { + "type": "integer" + }, + "limited_availability": { + "type": "boolean" + }, + "message": { + "type": "string" + }, + "name": { + "type": "string" + }, + "old_user": { + "type": "string" + }, + "openssh_public_key": { + "type": "string" + }, + "org": { + "type": "string" + }, + "previous_visibility": { + "type": "string" + }, + "read_only": { + "type": "boolean" + }, + "repo": { + "type": "string", + "description": "The name of the repository." + }, + "repository": { + "type": "string", + "description": "The name of the repository." + }, + "repository_public": { + "type": "boolean" + }, + "target_login": { + "type": "string" + }, + "team": { + "type": "string" + }, + "transport_protocol": { + "type": "integer", + "description": "The type of protocol (for example, HTTP or SSH) used to transfer Git data." + }, + "transport_protocol_name": { + "type": "string", + "description": "A human readable name for the protocol (for example, HTTP or SSH) used to transfer Git data." + }, + "user": { + "type": "string", + "description": "The user that was affected by the action performed (if available)." + }, + "visibility": { + "type": "string", + "description": "The repository visibility, for example `public` or `private`." + } + } + } + } + } + } + ], + "previews": [], + "descriptionHTML": "

Gets the audit log for an enterprise. To use this endpoint, you must be an enterprise admin, and you must use an access token with the admin:enterprise scope.

", + "statusCodes": [ + { + "httpStatusCode": "200", + "description": "

OK

" + } + ] + } + ], "global-webhooks": [ { "serverUrl": "https://HOSTNAME/api/v3", @@ -163229,11 +163801,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://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.", + "rawDescription": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/github-ae@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.", "isRequired": false, "childParamsGroups": [] } @@ -163257,7 +163829,7 @@ } ], "previews": [], - "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.\"

", "statusCodes": [ { "httpStatusCode": "204", @@ -163286,11 +163858,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://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.", + "rawDescription": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/github-ae@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.", "isRequired": false, "childParamsGroups": [] } @@ -163314,7 +163886,7 @@ } ], "previews": [], - "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.

", "statusCodes": [ { "httpStatusCode": "204", @@ -250581,6 +251153,404 @@ ], "subcategory": "orgs" }, + { + "serverUrl": "https://HOSTNAME/api/v3", + "verb": "get", + "requestPath": "/orgs/{org}/audit-log", + "title": "Get the audit log for an organization", + "category": "orgs", + "parameters": [ + { + "name": "org", + "description": "

The organization name. The name is not case sensitive.

", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "phrase", + "description": "

A search phrase. For more information, see Searching the audit log.

", + "in": "query", + "required": false, + "schema": { + "type": "string" + } + }, + { + "name": "after", + "description": "

A cursor, as given in the Link header. If specified, the query only searches for events after this cursor.

", + "in": "query", + "required": false, + "schema": { + "type": "string" + } + }, + { + "name": "before", + "description": "

A cursor, as given in the Link header. If specified, the query only searches for events before this cursor.

", + "in": "query", + "required": false, + "schema": { + "type": "string" + } + }, + { + "name": "order", + "description": "

The order of audit log events. To list newest events first, specify desc. To list oldest events first, specify asc.

\n

The default is desc.

", + "in": "query", + "required": false, + "schema": { + "type": "string", + "enum": [ + "desc", + "asc" + ] + } + }, + { + "name": "per_page", + "description": "

The number of 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 + } + } + ], + "bodyParameters": [], + "enabledForGitHubApps": true, + "codeExamples": [ + { + "key": "default", + "request": { + "description": "Example", + "acceptHeader": "application/vnd.github.v3+json", + "parameters": { + "org": "ORG" + } + }, + "response": { + "statusCode": "200", + "contentType": "application/json", + "description": "

Response

", + "example": [ + { + "actor_ip": "88.123.45.123", + "from": "pull_requests#merge", + "device_cookie": null, + "actor": "mona-admin", + "actor_id": 7, + "repo": "octo-org/octo-repo", + "repo_id": 17, + "business": "github", + "business_id": 1, + "org": "octo-org", + "org_id": 8, + "action": "pull_request.merge", + "@timestamp": 1635940599755, + "created_at": 1635940599755, + "operation_type": "modify", + "actor_location": { + "country_code": "GB", + "country_name": "United Kingdom", + "region": "ENG", + "region_name": "England", + "city": "Louth", + "postal_code": "LN11", + "location": { + "lat": 53.4457, + "lon": 0.141 + } + }, + "data": { + "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) ...", + "method": "POST", + "request_id": "e4dabc4d-ba16-4bca-1234-649be7ae1188", + "server_id": "5d17aab5-fd9f-abcd-a820-16bed246441b", + "request_category": "other", + "controller_action": "merge", + "url": "https://example.com/octo-org/octo-repo/pull/1/merge", + "client_id": 322299977.1635936, + "referrer": "https://example.com/octo-org/octo-repo/pull/1", + "actor_session": 1, + "pull_request_id": 1, + "category_type": "Resource Management" + } + }, + { + "actor_ip": "88.123.45.123", + "from": "pull_request_review_events#create", + "device_cookie": null, + "actor": "mona-admin", + "actor_id": 7, + "business_id": 1, + "org_id": 8, + "action": "pull_request_review.submit", + "@timestamp": 1635940593079, + "created_at": 1635940593079, + "operation_type": "modify", + "actor_location": { + "country_code": "GB", + "country_name": "United Kingdom", + "region": "ENG", + "region_name": "England", + "city": "Louth", + "postal_code": "LN11", + "location": { + "lat": 53.4457, + "lon": 0.141 + } + }, + "data": { + "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) ...", + "method": "PUT", + "request_id": "c0f63bb7-17b6-4796-940c-12345c5a581b", + "server_id": "2abc1234-f651-43e3-9696-e942ad5f8c89", + "request_category": "other", + "controller_action": "create", + "url": "https://example.com/octo-org/octo-repo/pull/1/reviews", + "client_id": 322299977.1635936, + "referrer": "https://example.com/octo-org/octo-repo/pull/1/files", + "actor_session": 1, + "spammy": false, + "pull_request_id": 1, + "body": null, + "allowed": true, + "id": 1, + "state": 40, + "issue_id": 1, + "review_id": 1, + "category_type": "Resource Management" + } + }, + { + "actor_ip": "88.123.45.123", + "from": "pull_requests#create", + "device_cookie": null, + "actor": "mona", + "actor_id": 9, + "user_id": 9, + "repo": "octo-org/octo-repo", + "repo_id": 17, + "business": "github", + "business_id": 1, + "org": "octo-org", + "org_id": 8, + "action": "pull_request.create", + "@timestamp": 1635940554161, + "created_at": 1635940554161, + "operation_type": "create", + "actor_location": { + "country_code": "GB", + "country_name": "United Kingdom", + "region": "ENG", + "region_name": "England", + "city": "Louth", + "postal_code": "LN11", + "location": { + "lat": 53.4457, + "lon": 0.141 + } + }, + "data": { + "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) ...", + "method": "POST", + "request_id": "2773abeb-477f-4ebf-a017-f8e8a206c305", + "server_id": "796e3115-4ce8-4606-8fd0-99ea57a2e12b", + "request_category": "other", + "controller_action": "create", + "url": "https://example.com/octo-org/octo-repo/pull/create?base=octo-org%3Amain&head=mona%3Apatch-1", + "client_id": 386351111.163594, + "referrer": "https://example.com/octo-org/octo-repo/compare/main...mona:patch-1", + "actor_session": 2, + "pull_request_id": 1, + "category_type": "Resource Management" + } + } + ], + "schema": { + "type": "array", + "items": { + "type": "object", + "properties": { + "@timestamp": { + "type": "integer", + "description": "The time the audit log event occurred, given as a [Unix timestamp](http://en.wikipedia.org/wiki/Unix_time)." + }, + "action": { + "type": "string", + "description": "The name of the action that was performed, for example `user.login` or `repo.create`." + }, + "active": { + "type": "boolean" + }, + "active_was": { + "type": "boolean" + }, + "actor": { + "type": "string", + "description": "The actor who performed the action." + }, + "actor_id": { + "type": "integer", + "description": "The id of the actor who performed the action." + }, + "actor_location": { + "type": "object", + "properties": { + "country_name": { + "type": "string" + } + } + }, + "data": { + "type": "object", + "additionalProperties": true + }, + "org_id": { + "type": "integer" + }, + "blocked_user": { + "type": "string", + "description": "The username of the account being blocked." + }, + "business": { + "type": "string" + }, + "config": { + "type": "array", + "items": { + "type": "object" + } + }, + "config_was": { + "type": "array", + "items": { + "type": "object" + } + }, + "content_type": { + "type": "string" + }, + "created_at": { + "type": "integer", + "description": "The time the audit log event was recorded, given as a [Unix timestamp](http://en.wikipedia.org/wiki/Unix_time)." + }, + "deploy_key_fingerprint": { + "type": "string" + }, + "_document_id": { + "type": "string", + "description": "A unique identifier for an audit event." + }, + "emoji": { + "type": "string" + }, + "events": { + "type": "array", + "items": { + "type": "object" + } + }, + "events_were": { + "type": "array", + "items": { + "type": "object" + } + }, + "explanation": { + "type": "string" + }, + "fingerprint": { + "type": "string" + }, + "hook_id": { + "type": "integer" + }, + "limited_availability": { + "type": "boolean" + }, + "message": { + "type": "string" + }, + "name": { + "type": "string" + }, + "old_user": { + "type": "string" + }, + "openssh_public_key": { + "type": "string" + }, + "org": { + "type": "string" + }, + "previous_visibility": { + "type": "string" + }, + "read_only": { + "type": "boolean" + }, + "repo": { + "type": "string", + "description": "The name of the repository." + }, + "repository": { + "type": "string", + "description": "The name of the repository." + }, + "repository_public": { + "type": "boolean" + }, + "target_login": { + "type": "string" + }, + "team": { + "type": "string" + }, + "transport_protocol": { + "type": "integer", + "description": "The type of protocol (for example, HTTP or SSH) used to transfer Git data." + }, + "transport_protocol_name": { + "type": "string", + "description": "A human readable name for the protocol (for example, HTTP or SSH) used to transfer Git data." + }, + "user": { + "type": "string", + "description": "The user that was affected by the action performed (if available)." + }, + "visibility": { + "type": "string", + "description": "The repository visibility, for example `public` or `private`." + } + } + } + } + } + } + ], + "previews": [], + "descriptionHTML": "

Gets the audit log for an organization. For more information, see \"Reviewing the audit log for your organization.\"

\n

This endpoint is available for organizations on GitHub Enterprise Cloud. To use this endpoint, you must be an organization owner, and you must use an access token with the admin:org scope. GitHub Apps must have the organization_administration read permission to use this endpoint.

\n

By default, the response includes up to 30 events from the past three months. Use the phrase parameter to filter results and retrieve older events. For example, use the phrase parameter with the created qualifier to filter events based on when the events occurred. For more information, see \"Reviewing the audit log for your organization.\"

\n

Use pagination to retrieve fewer or more than 30 events. For more information, see \"Resources in the REST API.\"

", + "statusCodes": [ + { + "httpStatusCode": "200", + "description": "

OK

" + } + ], + "subcategory": "orgs" + }, { "serverUrl": "https://HOSTNAME/api/v3", "verb": "get", @@ -257815,6 +258785,7 @@ } } ], + "previews": [], "descriptionHTML": "

Configures a GitHub AE Pages site. For more information, see \"About GitHub Pages.\"

", "statusCodes": [ { @@ -257830,9 +258801,6 @@ "description": "

Validation failed

" } ], - "previews": [ - "

Enabling and disabling Pages in the Pages API is currently available for developers to preview. See the blog post preview for more details. To access the new endpoints during the preview period, you must provide a custom media type in the Accept header:

\n
application/vnd.github.switcheroo-preview+json
" - ], "subcategory": "pages" }, { @@ -258027,6 +258995,7 @@ } ], "descriptionHTML": "", + "previews": [], "statusCodes": [ { "httpStatusCode": "204", @@ -258041,9 +259010,6 @@ "description": "

Validation failed

" } ], - "previews": [ - "

To access the API with your GitHub App, you must provide a custom media type in the Accept Header for your requests. shell application/vnd.github.machine-man-preview+json

" - ], "subcategory": "pages" }, { @@ -361458,7 +362424,7 @@ { "name": "secret_type", "in": "query", - "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types (API slug).

", + "description": "

A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"Secret scanning patterns\"\nfor a complete list of secret types.

", "required": false, "schema": { "type": "string" diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json index 9f11a8d35a..f5c1b432e0 100644 --- a/lib/rest/static/dereferenced/api.github.com.deref.json +++ b/lib/rest/static/dereferenced/api.github.com.deref.json @@ -26763,7 +26763,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -122540,7 +122540,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -167235,6 +167235,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -167249,6 +167256,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -172090,6 +172123,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -172474,6 +172508,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -172488,6 +172529,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -177329,6 +177396,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -177355,8 +177423,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -177390,6 +177459,22 @@ "site_admin": false }, "run_attempt": 1, + "referenced_workflows": [ + { + "path": "octocat/Hello-World/.github/workflows/deploy.yml@main", + "sha": "86e8bc9ecf7d38b1ed2d2cfb8eb87ba9b35b01db", + "ref": "refs/heads/main" + }, + { + "path": "octo-org/octo-repo/.github/workflows/report.yml@v2", + "sha": "79e9790903e1c3373b1a3e3a941d57405478a232", + "ref": "refs/tags/v2" + }, + { + "path": "octo-org/octo-repo/.github/workflows/secure.yml@1595d4b6de6a9e9751fb270a41019ce507d4099e", + "sha": "1595d4b6de6a9e9751fb270a41019ce507d4099e" + } + ], "run_started_at": "2020-01-22T19:33:08Z", "triggering_actor": { "login": "octocat", @@ -177417,6 +177502,7 @@ "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", + "previous_attempt_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/attempts/1", "workflow_url": "https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038", "head_commit": { "id": "acb5820ced9479c074f688cc328bf03f341a511d", @@ -178441,6 +178527,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -178455,6 +178548,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -183296,6 +183415,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -183322,8 +183442,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -183357,6 +183478,22 @@ "site_admin": false }, "run_attempt": 1, + "referenced_workflows": [ + { + "path": "octocat/Hello-World/.github/workflows/deploy.yml@main", + "sha": "86e8bc9ecf7d38b1ed2d2cfb8eb87ba9b35b01db", + "ref": "refs/heads/main" + }, + { + "path": "octo-org/octo-repo/.github/workflows/report.yml@v2", + "sha": "79e9790903e1c3373b1a3e3a941d57405478a232", + "ref": "refs/tags/v2" + }, + { + "path": "octo-org/octo-repo/.github/workflows/secure.yml@1595d4b6de6a9e9751fb270a41019ce507d4099e", + "sha": "1595d4b6de6a9e9751fb270a41019ce507d4099e" + } + ], "run_started_at": "2020-01-22T19:33:08Z", "triggering_actor": { "login": "octocat", @@ -183384,6 +183521,7 @@ "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", + "previous_attempt_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/attempts/1", "workflow_url": "https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038", "head_commit": { "id": "acb5820ced9479c074f688cc328bf03f341a511d", @@ -187964,6 +188102,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -187978,6 +188123,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -192819,6 +192990,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -199138,7 +199310,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -205267,7 +205439,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -436066,7 +436238,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -511568,6 +511740,15 @@ 3 ] }, + "name": { + "type": [ + "string", + "null" + ], + "examples": [ + "mastahyeti's GPG Key" + ] + }, "primary_key_id": { "type": [ "integer", @@ -511659,6 +511840,9 @@ "string", "null" ] + }, + "revoked": { + "type": "boolean" } } }, @@ -511679,7 +511863,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": null + "expires_at": null, + "revoked": false } ] }, @@ -511715,6 +511900,12 @@ ], "format": "date-time" }, + "revoked": { + "type": "boolean", + "examples": [ + true + ] + }, "raw_key": { "type": [ "string", @@ -511735,7 +511926,8 @@ "can_encrypt_storage", "can_certify", "emails", - "subkeys" + "subkeys", + "revoked" ] } }, @@ -511744,6 +511936,7 @@ "value": [ { "id": 3, + "name": "mastahyeti's GPG Key", "primary_key_id": 2, "key_id": "3262EFF25BA0D270", "public_key": "xsBNBFayYZ...", @@ -511770,7 +511963,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": "2016-03-24T11:31:04-07:00" + "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false } ], "can_sign": true, @@ -511779,6 +511973,7 @@ "can_certify": true, "created_at": "2016-03-24T11:31:04-06:00", "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false, "raw_key": "string" } ] @@ -511904,6 +512099,10 @@ "application/json": { "schema": { "properties": { + "name": { + "description": "A descriptive name for the new key.", + "type": "string" + }, "armored_public_key": { "description": "A GPG key in ASCII-armored format.", "type": "string" @@ -511933,6 +512132,15 @@ 3 ] }, + "name": { + "type": [ + "string", + "null" + ], + "examples": [ + "mastahyeti's GPG Key" + ] + }, "primary_key_id": { "type": [ "integer", @@ -512024,6 +512232,9 @@ "string", "null" ] + }, + "revoked": { + "type": "boolean" } } }, @@ -512044,7 +512255,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": null + "expires_at": null, + "revoked": false } ] }, @@ -512080,6 +512292,12 @@ ], "format": "date-time" }, + "revoked": { + "type": "boolean", + "examples": [ + true + ] + }, "raw_key": { "type": [ "string", @@ -512100,13 +512318,15 @@ "can_encrypt_storage", "can_certify", "emails", - "subkeys" + "subkeys", + "revoked" ] }, "examples": { "default": { "value": { "id": 3, + "name": "mastahyeti's GPG Key", "primary_key_id": 2, "key_id": "3262EFF25BA0D270", "public_key": "xsBNBFayYZ...", @@ -512133,7 +512353,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": "2016-03-24T11:31:04-07:00" + "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false } ], "can_sign": true, @@ -512142,6 +512363,7 @@ "can_certify": true, "created_at": "2016-03-24T11:31:04-06:00", "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false, "raw_key": "\"-----BEGIN PGP PUBLIC KEY BLOCK-----\\nVersion: GnuPG v2\\n\\nmQENBFayYZ0BCAC4hScoJXXpyR+MXGcrBxElqw3FzCVvkViuyeko+Jp76QJhg8kr\\nucRTxbnOoHfda/FmilEa/wxf9ch5/PSrrL26FxEoPHhJolp8fnIDLQeITn94NYdB\\nZtnnEKslpPrG97qSUWIchvyqCPtvOb8+8fWvGx9K/ZWcEEdh1X8+WFR2jMENMeoX\\nwxHWQoPnS7LpX/85/M7VUcJxvDVfv+eHsnQupmE5bGarKNih0oMe3LbdN3qA5PTz\\nSCm6Iudar1VsQ+xTz08ymL7t4pnEtLguQ7EyatFHCjxNblv5RzxoL0tDgN3HqoDz\\nc7TEA+q4RtDQl9amcvQ95emnXmZ974u7UkYdABEBAAG0HlNvbWUgVXNlciA8c29t\\nZXVzZXJAZ21haWwuY29tPokBOAQTAQIAIgUCVrJhnQIbAwYLCQgHAwIGFQgCCQoL\\nBBYCAwECHgECF4AACgkQMmLv8lug0nAViQgArWjI55+7p48URr2z9Jvak+yrBTx1\\nzkufltQAnHTJkq+Kl9dySSmTnOop8o3rE4++IOpYV5Y36PkKf9EZMk4n1RQiDPKE\\nAFtRVTkRaoWzOir9KQXJPfhKrl01j/QzY+utfiMvUoBJZ9ybq8Pa885SljW9lbaX\\nIYw+hl8ZdJ2KStvGrEyfQvRyq3aN5c9TV//4BdGnwx7Qabq/U+G18lizG6f/yq15\\ned7t0KELaCfeKPvytp4VE9/z/Ksah/h3+Qilx07/oG2Ae5kC1bEC9coD/ogPUhbv\\nb2bsBIoY9E9YwsLoif2lU+o1t76zLgUktuNscRRUKobW028H1zuFS/XQhrkBDQRW\\nsmGdAQgApnyyv3i144OLYy0O4UKQxd3e10Y3WpDwfnGIBefAI1m7RxnUxBag/DsU\\n7gi9qLEC4VHSfq4eiNfr1LJOyCL2edTgCWFgBhVjbXjZe6YAOrAnhxwCErnN0Y7N\\n6s8wVh9fObSOyf8ZE6G7JeKpcq9Q6gd/KxagfD48a1v+fyRHpyQc6J9pUEmtrDJ7\\nBjmsd2VWzLBvNWdHyxDNtZweIaqIO9VUYYpr1mtTliNBOZLUelmgrt7HBRcJpWMA\\nS8muVVbuP5MK0trLBq/JB8qUH3zRzB/PhMgzmkIfjEK1VYDWm4E8DYyTWEJcHqkb\\neqFsNjrIlwPaA122BWC6gUOPwwH+oQARAQABiQEfBBgBAgAJBQJWsmGdAhsMAAoJ\\nEDJi7/JboNJwAyAIALd4xcdmGbZD98gScJzqwzkOMcO8zFHqHNvJ42xIFvGny7c0\\n1Rx7iyrdypOby5AxE+viQcjG4rpLZW/xKYBNGrCfDyQO7511I0v8x20EICMlMfD/\\nNrWQCzesEPcUlKTP07d+sFyP8AyseOidbzY/92CpskTgdSBjY/ntLSaoknl/fjJE\\nQM8OkPqU7IraO1Jzzdnm20d5PZL9+PIwIWdSTedU/vBMTJyNcoqvSfKf1wNC66XP\\nhqfYgXJE564AdWZKA3C0IyCqiv+LHwxLnUHio1a4/r91C8KPzxs6tGxRDjXLd7ms\\nuYFGWymiUGOE/giHlcxdYcHzwLnPDliMQOLiTkK5AQ0EVuxMygEIAOD+bW1cDTmE\\nBxh5JECoqeHuwgl6DlLhnubWPkQ4ZeRzBRAsFcEJQlwlJjrzFDicL+lnm6Qq4tt0\\n560TwHdf15/AKTZIZu7H25axvGNzgeaUkJEJdYAq9zTKWwX7wKyzBszi485nQg97\\nMfAqwhMpDW0Qqf8+7Ug+WEmfBSGv9uL3aQC6WEeIsHfri0n0n8v4XgwhfShXguxO\\nCsOztEsuW7WWKW9P4TngKKv4lCHdPlV6FwxeMzODBJvc2fkHVHnqc0PqszJ5xcF8\\n6gZCpMM027SbpeYWCAD5zwJyYP9ntfO1p2HjnQ1dZaP9FeNcO7uIV1Lnd1eGCu6I\\nsrVp5k1f3isAEQEAAYkCPgQYAQIACQUCVuxMygIbAgEpCRAyYu/yW6DScMBdIAQZ\\nAQIABgUCVuxMygAKCRCKohN4dhq2b4tcCACHxmOHVXNpu47OvUGYQydLgMACUlXN\\nlj+HfE0VReqShxdDmpasAY9IRpuMB2RsGK8GbNP+4SlOlAiPf5SMhS7nZNkNDgQQ\\naZ3HFpgrFmFwmE10BKT4iQtoxELLM57z0qGOAfTsEjWFQa4sF+6IHAQR/ptkdkkI\\nBUEXiMnAwVwBysLIJiLO8qdjB6qp52QkT074JVrwywT/P+DkMfC2k4r/AfEbf6eF\\ndmPDuPk6KD87+hJZsSa5MaMUBQVvRO/mgEkhJRITVu58eWGaBOcQJ8gqurhCqM5P\\nDfUA4TJ7wiqM6sS764vV1rOioTTXkszzhClQqET7hPVnVQjenYgv0EZHNyQH/1f1\\n/CYqvV1vFjM9vJjMbxXsATCkZe6wvBVKD8vLsJAr8N+onKQz+4OPc3kmKq7aESu3\\nCi/iuie5KKVwnuNhr9AzT61vEkKxwHcVFEvHB77F6ZAAInhRvjzmQbD2dlPLLQCC\\nqDj71ODSSAPTEmUy6969bgD9PfWei7kNkBIx7s3eBv8yzytSc2EcuUgopqFazquw\\nFs1+tqGHjBvQfTo6bqbJjp/9Ci2pvde3ElV2rAgUlb3lqXyXjRDqrXosh5GcRPQj\\nK8Nhj1BNhnrCVskE4BP0LYbOHuzgm86uXwGCFsY+w2VOsSm16Jx5GHyG5S5WU3+D\\nIts/HFYRLiFgDLmTlxo=\\n=+OzK\\n-----END PGP PUBLIC KEY BLOCK-----\"" } } @@ -512353,6 +512575,15 @@ 3 ] }, + "name": { + "type": [ + "string", + "null" + ], + "examples": [ + "mastahyeti's GPG Key" + ] + }, "primary_key_id": { "type": [ "integer", @@ -512444,6 +512675,9 @@ "string", "null" ] + }, + "revoked": { + "type": "boolean" } } }, @@ -512464,7 +512698,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": null + "expires_at": null, + "revoked": false } ] }, @@ -512500,6 +512735,12 @@ ], "format": "date-time" }, + "revoked": { + "type": "boolean", + "examples": [ + true + ] + }, "raw_key": { "type": [ "string", @@ -512520,13 +512761,15 @@ "can_encrypt_storage", "can_certify", "emails", - "subkeys" + "subkeys", + "revoked" ] }, "examples": { "default": { "value": { "id": 3, + "name": "mastahyeti's GPG Key", "primary_key_id": 2, "key_id": "3262EFF25BA0D270", "public_key": "xsBNBFayYZ...", @@ -512553,7 +512796,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": "2016-03-24T11:31:04-07:00" + "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false } ], "can_sign": true, @@ -512562,6 +512806,7 @@ "can_certify": true, "created_at": "2016-03-24T11:31:04-06:00", "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false, "raw_key": "\"-----BEGIN PGP PUBLIC KEY BLOCK-----\\nVersion: GnuPG v2\\n\\nmQENBFayYZ0BCAC4hScoJXXpyR+MXGcrBxElqw3FzCVvkViuyeko+Jp76QJhg8kr\\nucRTxbnOoHfda/FmilEa/wxf9ch5/PSrrL26FxEoPHhJolp8fnIDLQeITn94NYdB\\nZtnnEKslpPrG97qSUWIchvyqCPtvOb8+8fWvGx9K/ZWcEEdh1X8+WFR2jMENMeoX\\nwxHWQoPnS7LpX/85/M7VUcJxvDVfv+eHsnQupmE5bGarKNih0oMe3LbdN3qA5PTz\\nSCm6Iudar1VsQ+xTz08ymL7t4pnEtLguQ7EyatFHCjxNblv5RzxoL0tDgN3HqoDz\\nc7TEA+q4RtDQl9amcvQ95emnXmZ974u7UkYdABEBAAG0HlNvbWUgVXNlciA8c29t\\nZXVzZXJAZ21haWwuY29tPokBOAQTAQIAIgUCVrJhnQIbAwYLCQgHAwIGFQgCCQoL\\nBBYCAwECHgECF4AACgkQMmLv8lug0nAViQgArWjI55+7p48URr2z9Jvak+yrBTx1\\nzkufltQAnHTJkq+Kl9dySSmTnOop8o3rE4++IOpYV5Y36PkKf9EZMk4n1RQiDPKE\\nAFtRVTkRaoWzOir9KQXJPfhKrl01j/QzY+utfiMvUoBJZ9ybq8Pa885SljW9lbaX\\nIYw+hl8ZdJ2KStvGrEyfQvRyq3aN5c9TV//4BdGnwx7Qabq/U+G18lizG6f/yq15\\ned7t0KELaCfeKPvytp4VE9/z/Ksah/h3+Qilx07/oG2Ae5kC1bEC9coD/ogPUhbv\\nb2bsBIoY9E9YwsLoif2lU+o1t76zLgUktuNscRRUKobW028H1zuFS/XQhrkBDQRW\\nsmGdAQgApnyyv3i144OLYy0O4UKQxd3e10Y3WpDwfnGIBefAI1m7RxnUxBag/DsU\\n7gi9qLEC4VHSfq4eiNfr1LJOyCL2edTgCWFgBhVjbXjZe6YAOrAnhxwCErnN0Y7N\\n6s8wVh9fObSOyf8ZE6G7JeKpcq9Q6gd/KxagfD48a1v+fyRHpyQc6J9pUEmtrDJ7\\nBjmsd2VWzLBvNWdHyxDNtZweIaqIO9VUYYpr1mtTliNBOZLUelmgrt7HBRcJpWMA\\nS8muVVbuP5MK0trLBq/JB8qUH3zRzB/PhMgzmkIfjEK1VYDWm4E8DYyTWEJcHqkb\\neqFsNjrIlwPaA122BWC6gUOPwwH+oQARAQABiQEfBBgBAgAJBQJWsmGdAhsMAAoJ\\nEDJi7/JboNJwAyAIALd4xcdmGbZD98gScJzqwzkOMcO8zFHqHNvJ42xIFvGny7c0\\n1Rx7iyrdypOby5AxE+viQcjG4rpLZW/xKYBNGrCfDyQO7511I0v8x20EICMlMfD/\\nNrWQCzesEPcUlKTP07d+sFyP8AyseOidbzY/92CpskTgdSBjY/ntLSaoknl/fjJE\\nQM8OkPqU7IraO1Jzzdnm20d5PZL9+PIwIWdSTedU/vBMTJyNcoqvSfKf1wNC66XP\\nhqfYgXJE564AdWZKA3C0IyCqiv+LHwxLnUHio1a4/r91C8KPzxs6tGxRDjXLd7ms\\nuYFGWymiUGOE/giHlcxdYcHzwLnPDliMQOLiTkK5AQ0EVuxMygEIAOD+bW1cDTmE\\nBxh5JECoqeHuwgl6DlLhnubWPkQ4ZeRzBRAsFcEJQlwlJjrzFDicL+lnm6Qq4tt0\\n560TwHdf15/AKTZIZu7H25axvGNzgeaUkJEJdYAq9zTKWwX7wKyzBszi485nQg97\\nMfAqwhMpDW0Qqf8+7Ug+WEmfBSGv9uL3aQC6WEeIsHfri0n0n8v4XgwhfShXguxO\\nCsOztEsuW7WWKW9P4TngKKv4lCHdPlV6FwxeMzODBJvc2fkHVHnqc0PqszJ5xcF8\\n6gZCpMM027SbpeYWCAD5zwJyYP9ntfO1p2HjnQ1dZaP9FeNcO7uIV1Lnd1eGCu6I\\nsrVp5k1f3isAEQEAAYkCPgQYAQIACQUCVuxMygIbAgEpCRAyYu/yW6DScMBdIAQZ\\nAQIABgUCVuxMygAKCRCKohN4dhq2b4tcCACHxmOHVXNpu47OvUGYQydLgMACUlXN\\nlj+HfE0VReqShxdDmpasAY9IRpuMB2RsGK8GbNP+4SlOlAiPf5SMhS7nZNkNDgQQ\\naZ3HFpgrFmFwmE10BKT4iQtoxELLM57z0qGOAfTsEjWFQa4sF+6IHAQR/ptkdkkI\\nBUEXiMnAwVwBysLIJiLO8qdjB6qp52QkT074JVrwywT/P+DkMfC2k4r/AfEbf6eF\\ndmPDuPk6KD87+hJZsSa5MaMUBQVvRO/mgEkhJRITVu58eWGaBOcQJ8gqurhCqM5P\\nDfUA4TJ7wiqM6sS764vV1rOioTTXkszzhClQqET7hPVnVQjenYgv0EZHNyQH/1f1\\n/CYqvV1vFjM9vJjMbxXsATCkZe6wvBVKD8vLsJAr8N+onKQz+4OPc3kmKq7aESu3\\nCi/iuie5KKVwnuNhr9AzT61vEkKxwHcVFEvHB77F6ZAAInhRvjzmQbD2dlPLLQCC\\nqDj71ODSSAPTEmUy6969bgD9PfWei7kNkBIx7s3eBv8yzytSc2EcuUgopqFazquw\\nFs1+tqGHjBvQfTo6bqbJjp/9Ci2pvde3ElV2rAgUlb3lqXyXjRDqrXosh5GcRPQj\\nK8Nhj1BNhnrCVskE4BP0LYbOHuzgm86uXwGCFsY+w2VOsSm16Jx5GHyG5S5WU3+D\\nIts/HFYRLiFgDLmTlxo=\\n=+OzK\\n-----END PGP PUBLIC KEY BLOCK-----\"" } } @@ -565246,6 +565491,15 @@ 3 ] }, + "name": { + "type": [ + "string", + "null" + ], + "examples": [ + "mastahyeti's GPG Key" + ] + }, "primary_key_id": { "type": [ "integer", @@ -565337,6 +565591,9 @@ "string", "null" ] + }, + "revoked": { + "type": "boolean" } } }, @@ -565357,7 +565614,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": null + "expires_at": null, + "revoked": false } ] }, @@ -565393,6 +565651,12 @@ ], "format": "date-time" }, + "revoked": { + "type": "boolean", + "examples": [ + true + ] + }, "raw_key": { "type": [ "string", @@ -565413,7 +565677,8 @@ "can_encrypt_storage", "can_certify", "emails", - "subkeys" + "subkeys", + "revoked" ] } }, @@ -565422,6 +565687,7 @@ "value": [ { "id": 3, + "name": "mastahyeti's GPG Key", "primary_key_id": 2, "key_id": "3262EFF25BA0D270", "public_key": "xsBNBFayYZ...", @@ -565448,7 +565714,8 @@ "can_encrypt_storage": true, "can_certify": false, "created_at": "2016-03-24T11:31:04-06:00", - "expires_at": "2016-03-24T11:31:04-07:00" + "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false } ], "can_sign": true, @@ -565457,6 +565724,7 @@ "can_certify": true, "created_at": "2016-03-24T11:31:04-06:00", "expires_at": "2016-03-24T11:31:04-07:00", + "revoked": false, "raw_key": "string" } ] diff --git a/lib/rest/static/dereferenced/ghes-3.1.deref.json b/lib/rest/static/dereferenced/ghes-3.1.deref.json index 59dd213e88..8cf87eb4ea 100644 --- a/lib/rest/static/dereferenced/ghes-3.1.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.1.deref.json @@ -1336,7 +1336,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://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.", + "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-server@3.1/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/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" @@ -5169,7 +5169,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://docs.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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"[About authentication for your enterprise](https://docs.github.com/enterprise-server@3.1/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise).\"" } }, "required": [ @@ -136052,16 +136052,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -140340,6 +140330,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -140881,16 +140872,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -145169,6 +145150,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -145195,8 +145177,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -147911,16 +147894,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -152199,6 +152172,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -156566,7 +156540,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -161483,7 +161457,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -366931,7 +366905,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.1/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.1/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -463209,7 +463183,7 @@ "/users/{username}/suspended": { "put": { "summary": "Suspend a user", - "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).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise-server@3.1/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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" @@ -463245,7 +463219,7 @@ "properties": { "reason": { "type": "string", - "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." + "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.1/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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." } } } @@ -463261,7 +463235,7 @@ }, "delete": { "summary": "Unsuspend a user", - "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.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise-server@3.1/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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" @@ -463297,7 +463271,7 @@ "properties": { "reason": { "type": "string", - "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." + "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.1/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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 5966a18486..e081fb6c34 100644 --- a/lib/rest/static/dereferenced/ghes-3.2.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.2.deref.json @@ -1336,7 +1336,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://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.", + "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-server@3.2/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/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" @@ -5176,7 +5176,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://docs.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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"[About authentication for your enterprise](https://docs.github.com/enterprise-server@3.2/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise).\"" } }, "required": [ @@ -138601,16 +138601,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -142911,6 +142901,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -143452,16 +143443,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -147762,6 +147743,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -147788,8 +147770,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -152228,16 +152211,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -156538,6 +156511,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -160905,7 +160879,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -165822,7 +165796,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -376230,7 +376204,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.2/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.2/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -473297,7 +473271,7 @@ "/users/{username}/suspended": { "put": { "summary": "Suspend a user", - "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).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise-server@3.2/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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" @@ -473333,7 +473307,7 @@ "properties": { "reason": { "type": "string", - "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." + "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.2/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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." } } } @@ -473349,7 +473323,7 @@ }, "delete": { "summary": "Unsuspend a user", - "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.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise-server@3.2/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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" @@ -473385,7 +473359,7 @@ "properties": { "reason": { "type": "string", - "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." + "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.2/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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 e44cc39047..db1b71bd27 100644 --- a/lib/rest/static/dereferenced/ghes-3.3.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.3.deref.json @@ -1268,7 +1268,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://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.", + "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-server@3.3/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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" @@ -5030,7 +5030,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://docs.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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"[About authentication for your enterprise](https://docs.github.com/enterprise-server@3.3/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise).\"" } }, "required": [ @@ -99656,7 +99656,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.3/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.3/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -141497,16 +141497,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -145807,6 +145797,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -146348,16 +146339,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -150658,6 +150639,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -150684,8 +150666,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -155188,16 +155171,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -159498,6 +159471,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -164375,7 +164349,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -169250,7 +169224,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -379799,7 +379773,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.3/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.3/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -476887,7 +476861,7 @@ "/users/{username}/suspended": { "put": { "summary": "Suspend a user", - "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).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise-server@3.3/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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" @@ -476923,7 +476897,7 @@ "properties": { "reason": { "type": "string", - "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." + "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.3/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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." } } } @@ -476939,7 +476913,7 @@ }, "delete": { "summary": "Unsuspend a user", - "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.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise-server@3.3/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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" @@ -476975,7 +476949,7 @@ "properties": { "reason": { "type": "string", - "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." + "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.3/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.4.deref.json b/lib/rest/static/dereferenced/ghes-3.4.deref.json index d4ed2596c3..b20ca741db 100644 --- a/lib/rest/static/dereferenced/ghes-3.4.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.4.deref.json @@ -1268,7 +1268,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://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.4/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-server@3.4/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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.4/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" @@ -5022,7 +5022,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://docs.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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"[About authentication for your enterprise](https://docs.github.com/enterprise-server@3.4/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise).\"" } }, "required": [ @@ -33707,7 +33707,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.4/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.4/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -111452,7 +111452,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.4/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.4/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -154423,16 +154423,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -158733,6 +158723,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -159274,16 +159265,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -163584,6 +163565,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -163610,8 +163592,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -168114,16 +168097,6 @@ "https://api.github.com/repos/github/hello-world/actions/runs/5/rerun" ] }, - "previous_attempt_url": { - "description": "The URL to the previous attempted run of this workflow, if one exists.", - "type": [ - "string", - "null" - ], - "examples": [ - "https://api.github.com/repos/github/hello-world/actions/runs/5/attempts/3" - ] - }, "workflow_url": { "description": "The URL to the workflow.", "type": "string", @@ -172424,6 +172397,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -178492,7 +178466,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -184621,7 +184595,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -396001,7 +395975,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.4/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.4/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -499450,7 +499424,7 @@ "/users/{username}/suspended": { "put": { "summary": "Suspend a user", - "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.4/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-server@3.4/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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.4/rest/overview/resources-in-the-rest-api#http-verbs).\"", "operationId": "enterprise-admin/suspend-user", "tags": [ "enterprise-admin" @@ -499486,7 +499460,7 @@ "properties": { "reason": { "type": "string", - "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." + "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.4/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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." } } } @@ -499502,7 +499476,7 @@ }, "delete": { "summary": "Unsuspend a user", - "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.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise-server@3.4/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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" @@ -499538,7 +499512,7 @@ "properties": { "reason": { "type": "string", - "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." + "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.4/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.5.deref.json b/lib/rest/static/dereferenced/ghes-3.5.deref.json index 64b18fa06e..489d8fc257 100644 --- a/lib/rest/static/dereferenced/ghes-3.5.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.5.deref.json @@ -1268,7 +1268,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://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.5/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-server@3.5/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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.5/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" @@ -5022,7 +5022,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://docs.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\naddress. This parameter can be omitted when using CAS, LDAP, or SAML.\nFor more information, see \"[About authentication for your enterprise](https://docs.github.com/enterprise-server@3.5/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise).\"" } }, "required": [ @@ -34073,7 +34073,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.5/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.5/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -115703,7 +115703,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.5/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.5/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -163742,6 +163742,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -168981,6 +168982,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -169007,12 +169009,12 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "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", @@ -169069,6 +169071,7 @@ "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", + "previous_attempt_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/attempts/1", "workflow_url": "https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038", "head_commit": { "id": "acb5820ced9479c074f688cc328bf03f341a511d", @@ -174830,6 +174833,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -174856,12 +174860,12 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "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", @@ -174918,6 +174922,7 @@ "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", + "previous_attempt_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/attempts/1", "workflow_url": "https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038", "head_commit": { "id": "acb5820ced9479c074f688cc328bf03f341a511d", @@ -184109,6 +184114,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -190219,7 +190225,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -196348,7 +196354,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -407984,7 +407990,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.5/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/enterprise-server@3.5/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -511954,7 +511960,7 @@ "/users/{username}/suspended": { "put": { "summary": "Suspend a user", - "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.5/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-server@3.5/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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.5/rest/overview/resources-in-the-rest-api#http-verbs).\"", "operationId": "enterprise-admin/suspend-user", "tags": [ "enterprise-admin" @@ -511990,7 +511996,7 @@ "properties": { "reason": { "type": "string", - "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." + "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.5/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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." } } } @@ -512006,7 +512012,7 @@ }, "delete": { "summary": "Unsuspend a user", - "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.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/enterprise-server@3.5/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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" @@ -512042,7 +512048,7 @@ "properties": { "reason": { "type": "string", - "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." + "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/enterprise-server@3.5/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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 46c8e71494..305fdb0187 100644 --- a/lib/rest/static/dereferenced/github.ae.deref.json +++ b/lib/rest/static/dereferenced/github.ae.deref.json @@ -21302,6 +21302,402 @@ } } }, + "/enterprises/{enterprise}/audit-log": { + "get": { + "summary": "Get the audit log for an enterprise", + "operationId": "enterprise-admin/get-audit-log", + "description": "Gets the audit log for an enterprise. To use this endpoint, you must be an enterprise admin, and you must use an access token with the `admin:enterprise` scope.", + "tags": [ + "enterprise-admin" + ], + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/github-ae@latest/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise" + }, + "parameters": [ + { + "name": "enterprise", + "description": "The slug version of the enterprise name. You can also substitute this value with the enterprise id.", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "phrase", + "description": "A search phrase. For more information, see [Searching the audit log](https://docs.github.com/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log).", + "in": "query", + "required": false, + "schema": { + "type": "string" + } + }, + { + "name": "after", + "description": "A cursor, as given in the [Link header](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#link-header). If specified, the query only searches for events after this cursor.", + "in": "query", + "required": false, + "schema": { + "type": "string" + } + }, + { + "name": "before", + "description": "A cursor, as given in the [Link header](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#link-header). If specified, the query only searches for events before this cursor.", + "in": "query", + "required": false, + "schema": { + "type": "string" + } + }, + { + "name": "order", + "description": "The order of audit log events. To list newest events first, specify `desc`. To list oldest events first, specify `asc`.\n\nThe default is `desc`.", + "in": "query", + "required": false, + "schema": { + "type": "string", + "enum": [ + "desc", + "asc" + ] + } + }, + { + "name": "page", + "description": "Page number of the results to fetch.", + "in": "query", + "schema": { + "type": "integer", + "default": 1 + } + }, + { + "name": "per_page", + "description": "The number of results per page (max 100).", + "in": "query", + "schema": { + "type": "integer", + "default": 30 + } + } + ], + "responses": { + "200": { + "description": "Response", + "content": { + "application/json": { + "schema": { + "type": "array", + "items": { + "type": "object", + "properties": { + "@timestamp": { + "type": "integer", + "description": "The time the audit log event occurred, given as a [Unix timestamp](http://en.wikipedia.org/wiki/Unix_time)." + }, + "action": { + "type": "string", + "description": "The name of the action that was performed, for example `user.login` or `repo.create`." + }, + "active": { + "type": "boolean" + }, + "active_was": { + "type": "boolean" + }, + "actor": { + "type": "string", + "description": "The actor who performed the action." + }, + "actor_id": { + "type": "integer", + "description": "The id of the actor who performed the action." + }, + "actor_location": { + "type": "object", + "properties": { + "country_name": { + "type": "string" + } + } + }, + "data": { + "type": "object", + "additionalProperties": true + }, + "org_id": { + "type": "integer" + }, + "blocked_user": { + "type": "string", + "description": "The username of the account being blocked." + }, + "business": { + "type": "string" + }, + "config": { + "type": "array", + "items": { + "type": "object" + } + }, + "config_was": { + "type": "array", + "items": { + "type": "object" + } + }, + "content_type": { + "type": "string" + }, + "created_at": { + "type": "integer", + "description": "The time the audit log event was recorded, given as a [Unix timestamp](http://en.wikipedia.org/wiki/Unix_time)." + }, + "deploy_key_fingerprint": { + "type": "string" + }, + "_document_id": { + "type": "string", + "description": "A unique identifier for an audit event." + }, + "emoji": { + "type": "string" + }, + "events": { + "type": "array", + "items": { + "type": "object" + } + }, + "events_were": { + "type": "array", + "items": { + "type": "object" + } + }, + "explanation": { + "type": "string" + }, + "fingerprint": { + "type": "string" + }, + "hook_id": { + "type": "integer" + }, + "limited_availability": { + "type": "boolean" + }, + "message": { + "type": "string" + }, + "name": { + "type": "string" + }, + "old_user": { + "type": "string" + }, + "openssh_public_key": { + "type": "string" + }, + "org": { + "type": "string" + }, + "previous_visibility": { + "type": "string" + }, + "read_only": { + "type": "boolean" + }, + "repo": { + "type": "string", + "description": "The name of the repository." + }, + "repository": { + "type": "string", + "description": "The name of the repository." + }, + "repository_public": { + "type": "boolean" + }, + "target_login": { + "type": "string" + }, + "team": { + "type": "string" + }, + "transport_protocol": { + "type": "integer", + "description": "The type of protocol (for example, HTTP or SSH) used to transfer Git data." + }, + "transport_protocol_name": { + "type": "string", + "description": "A human readable name for the protocol (for example, HTTP or SSH) used to transfer Git data." + }, + "user": { + "type": "string", + "description": "The user that was affected by the action performed (if available)." + }, + "visibility": { + "type": "string", + "description": "The repository visibility, for example `public` or `private`." + } + } + } + }, + "examples": { + "default": { + "value": [ + { + "actor_ip": "88.123.45.123", + "from": "pull_requests#merge", + "device_cookie": null, + "actor": "mona-admin", + "actor_id": 7, + "repo": "octo-org/octo-repo", + "repo_id": 17, + "business": "github", + "business_id": 1, + "org": "octo-org", + "org_id": 8, + "action": "pull_request.merge", + "@timestamp": 1635940599755, + "created_at": 1635940599755, + "operation_type": "modify", + "actor_location": { + "country_code": "GB", + "country_name": "United Kingdom", + "region": "ENG", + "region_name": "England", + "city": "Louth", + "postal_code": "LN11", + "location": { + "lat": 53.4457, + "lon": 0.141 + } + }, + "data": { + "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) ...", + "method": "POST", + "request_id": "e4dabc4d-ba16-4bca-1234-649be7ae1188", + "server_id": "5d17aab5-fd9f-abcd-a820-16bed246441b", + "request_category": "other", + "controller_action": "merge", + "url": "https://example.com/octo-org/octo-repo/pull/1/merge", + "client_id": 322299977.1635936, + "referrer": "https://example.com/octo-org/octo-repo/pull/1", + "actor_session": 1, + "pull_request_id": 1, + "category_type": "Resource Management" + } + }, + { + "actor_ip": "88.123.45.123", + "from": "pull_request_review_events#create", + "device_cookie": null, + "actor": "mona-admin", + "actor_id": 7, + "business_id": 1, + "org_id": 8, + "action": "pull_request_review.submit", + "@timestamp": 1635940593079, + "created_at": 1635940593079, + "operation_type": "modify", + "actor_location": { + "country_code": "GB", + "country_name": "United Kingdom", + "region": "ENG", + "region_name": "England", + "city": "Louth", + "postal_code": "LN11", + "location": { + "lat": 53.4457, + "lon": 0.141 + } + }, + "data": { + "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) ...", + "method": "PUT", + "request_id": "c0f63bb7-17b6-4796-940c-12345c5a581b", + "server_id": "2abc1234-f651-43e3-9696-e942ad5f8c89", + "request_category": "other", + "controller_action": "create", + "url": "https://example.com/octo-org/octo-repo/pull/1/reviews", + "client_id": 322299977.1635936, + "referrer": "https://example.com/octo-org/octo-repo/pull/1/files", + "actor_session": 1, + "spammy": false, + "pull_request_id": 1, + "body": null, + "allowed": true, + "id": 1, + "state": 40, + "issue_id": 1, + "review_id": 1, + "category_type": "Resource Management" + } + }, + { + "actor_ip": "88.123.45.123", + "from": "pull_requests#create", + "device_cookie": null, + "actor": "mona", + "actor_id": 9, + "user_id": 9, + "repo": "octo-org/octo-repo", + "repo_id": 17, + "business": "github", + "business_id": 1, + "org": "octo-org", + "org_id": 8, + "action": "pull_request.create", + "@timestamp": 1635940554161, + "created_at": 1635940554161, + "operation_type": "create", + "actor_location": { + "country_code": "GB", + "country_name": "United Kingdom", + "region": "ENG", + "region_name": "England", + "city": "Louth", + "postal_code": "LN11", + "location": { + "lat": 53.4457, + "lon": 0.141 + } + }, + "data": { + "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) ...", + "method": "POST", + "request_id": "2773abeb-477f-4ebf-a017-f8e8a206c305", + "server_id": "796e3115-4ce8-4606-8fd0-99ea57a2e12b", + "request_category": "other", + "controller_action": "create", + "url": "https://example.com/octo-org/octo-repo/pull/create?base=octo-org%3Amain&head=mona%3Apatch-1", + "client_id": 386351111.163594, + "referrer": "https://example.com/octo-org/octo-repo/compare/main...mona:patch-1", + "actor_session": 2, + "pull_request_id": 1, + "category_type": "Resource Management" + } + } + ] + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": true, + "enabledForGitHubApps": false, + "category": "enterprise-admin", + "subcategory": "audit-log" + } + } + }, "/feeds": { "get": { "summary": "Get feeds", @@ -55511,6 +55907,402 @@ } } }, + "/orgs/{org}/audit-log": { + "get": { + "summary": "Get the audit log for an organization", + "description": "Gets the audit log for an organization. For more information, see \"[Reviewing the audit log for your organization](https://docs.github.com/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization).\"\n\nThis endpoint is available for organizations on GitHub Enterprise Cloud. To use this endpoint, you must be an organization owner, and you must use an access token with the `admin:org` scope. GitHub Apps must have the `organization_administration` read permission to use this endpoint.\n\nBy default, the response includes up to 30 events from the past three months. Use the `phrase` parameter to filter results and retrieve older events. For example, use the `phrase` parameter with the `created` qualifier to filter events based on when the events occurred. For more information, see \"[Reviewing the audit log for your organization](https://docs.github.com/github-ae@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#searching-the-audit-log).\"\n\nUse pagination to retrieve fewer or more than 30 events. For more information, see \"[Resources in the REST API](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#pagination).\"", + "operationId": "orgs/get-audit-log", + "tags": [ + "orgs" + ], + "externalDocs": { + "description": "API method documentation", + "url": "https://docs.github.com/github-ae@latest/rest/reference/orgs#get-audit-log" + }, + "parameters": [ + { + "name": "org", + "description": "The organization name. The name is not case sensitive.", + "in": "path", + "required": true, + "schema": { + "type": "string" + } + }, + { + "name": "phrase", + "description": "A search phrase. For more information, see [Searching the audit log](https://docs.github.com/github-ae@latest/github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization#searching-the-audit-log).", + "in": "query", + "required": false, + "schema": { + "type": "string" + } + }, + { + "name": "after", + "description": "A cursor, as given in the [Link header](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#link-header). If specified, the query only searches for events after this cursor.", + "in": "query", + "required": false, + "schema": { + "type": "string" + } + }, + { + "name": "before", + "description": "A cursor, as given in the [Link header](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#link-header). If specified, the query only searches for events before this cursor.", + "in": "query", + "required": false, + "schema": { + "type": "string" + } + }, + { + "name": "order", + "description": "The order of audit log events. To list newest events first, specify `desc`. To list oldest events first, specify `asc`.\n\nThe default is `desc`.", + "in": "query", + "required": false, + "schema": { + "type": "string", + "enum": [ + "desc", + "asc" + ] + } + }, + { + "name": "per_page", + "description": "The number of 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": "array", + "items": { + "type": "object", + "properties": { + "@timestamp": { + "type": "integer", + "description": "The time the audit log event occurred, given as a [Unix timestamp](http://en.wikipedia.org/wiki/Unix_time)." + }, + "action": { + "type": "string", + "description": "The name of the action that was performed, for example `user.login` or `repo.create`." + }, + "active": { + "type": "boolean" + }, + "active_was": { + "type": "boolean" + }, + "actor": { + "type": "string", + "description": "The actor who performed the action." + }, + "actor_id": { + "type": "integer", + "description": "The id of the actor who performed the action." + }, + "actor_location": { + "type": "object", + "properties": { + "country_name": { + "type": "string" + } + } + }, + "data": { + "type": "object", + "additionalProperties": true + }, + "org_id": { + "type": "integer" + }, + "blocked_user": { + "type": "string", + "description": "The username of the account being blocked." + }, + "business": { + "type": "string" + }, + "config": { + "type": "array", + "items": { + "type": "object" + } + }, + "config_was": { + "type": "array", + "items": { + "type": "object" + } + }, + "content_type": { + "type": "string" + }, + "created_at": { + "type": "integer", + "description": "The time the audit log event was recorded, given as a [Unix timestamp](http://en.wikipedia.org/wiki/Unix_time)." + }, + "deploy_key_fingerprint": { + "type": "string" + }, + "_document_id": { + "type": "string", + "description": "A unique identifier for an audit event." + }, + "emoji": { + "type": "string" + }, + "events": { + "type": "array", + "items": { + "type": "object" + } + }, + "events_were": { + "type": "array", + "items": { + "type": "object" + } + }, + "explanation": { + "type": "string" + }, + "fingerprint": { + "type": "string" + }, + "hook_id": { + "type": "integer" + }, + "limited_availability": { + "type": "boolean" + }, + "message": { + "type": "string" + }, + "name": { + "type": "string" + }, + "old_user": { + "type": "string" + }, + "openssh_public_key": { + "type": "string" + }, + "org": { + "type": "string" + }, + "previous_visibility": { + "type": "string" + }, + "read_only": { + "type": "boolean" + }, + "repo": { + "type": "string", + "description": "The name of the repository." + }, + "repository": { + "type": "string", + "description": "The name of the repository." + }, + "repository_public": { + "type": "boolean" + }, + "target_login": { + "type": "string" + }, + "team": { + "type": "string" + }, + "transport_protocol": { + "type": "integer", + "description": "The type of protocol (for example, HTTP or SSH) used to transfer Git data." + }, + "transport_protocol_name": { + "type": "string", + "description": "A human readable name for the protocol (for example, HTTP or SSH) used to transfer Git data." + }, + "user": { + "type": "string", + "description": "The user that was affected by the action performed (if available)." + }, + "visibility": { + "type": "string", + "description": "The repository visibility, for example `public` or `private`." + } + } + } + }, + "examples": { + "default": { + "value": [ + { + "actor_ip": "88.123.45.123", + "from": "pull_requests#merge", + "device_cookie": null, + "actor": "mona-admin", + "actor_id": 7, + "repo": "octo-org/octo-repo", + "repo_id": 17, + "business": "github", + "business_id": 1, + "org": "octo-org", + "org_id": 8, + "action": "pull_request.merge", + "@timestamp": 1635940599755, + "created_at": 1635940599755, + "operation_type": "modify", + "actor_location": { + "country_code": "GB", + "country_name": "United Kingdom", + "region": "ENG", + "region_name": "England", + "city": "Louth", + "postal_code": "LN11", + "location": { + "lat": 53.4457, + "lon": 0.141 + } + }, + "data": { + "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) ...", + "method": "POST", + "request_id": "e4dabc4d-ba16-4bca-1234-649be7ae1188", + "server_id": "5d17aab5-fd9f-abcd-a820-16bed246441b", + "request_category": "other", + "controller_action": "merge", + "url": "https://example.com/octo-org/octo-repo/pull/1/merge", + "client_id": 322299977.1635936, + "referrer": "https://example.com/octo-org/octo-repo/pull/1", + "actor_session": 1, + "pull_request_id": 1, + "category_type": "Resource Management" + } + }, + { + "actor_ip": "88.123.45.123", + "from": "pull_request_review_events#create", + "device_cookie": null, + "actor": "mona-admin", + "actor_id": 7, + "business_id": 1, + "org_id": 8, + "action": "pull_request_review.submit", + "@timestamp": 1635940593079, + "created_at": 1635940593079, + "operation_type": "modify", + "actor_location": { + "country_code": "GB", + "country_name": "United Kingdom", + "region": "ENG", + "region_name": "England", + "city": "Louth", + "postal_code": "LN11", + "location": { + "lat": 53.4457, + "lon": 0.141 + } + }, + "data": { + "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) ...", + "method": "PUT", + "request_id": "c0f63bb7-17b6-4796-940c-12345c5a581b", + "server_id": "2abc1234-f651-43e3-9696-e942ad5f8c89", + "request_category": "other", + "controller_action": "create", + "url": "https://example.com/octo-org/octo-repo/pull/1/reviews", + "client_id": 322299977.1635936, + "referrer": "https://example.com/octo-org/octo-repo/pull/1/files", + "actor_session": 1, + "spammy": false, + "pull_request_id": 1, + "body": null, + "allowed": true, + "id": 1, + "state": 40, + "issue_id": 1, + "review_id": 1, + "category_type": "Resource Management" + } + }, + { + "actor_ip": "88.123.45.123", + "from": "pull_requests#create", + "device_cookie": null, + "actor": "mona", + "actor_id": 9, + "user_id": 9, + "repo": "octo-org/octo-repo", + "repo_id": 17, + "business": "github", + "business_id": 1, + "org": "octo-org", + "org_id": 8, + "action": "pull_request.create", + "@timestamp": 1635940554161, + "created_at": 1635940554161, + "operation_type": "create", + "actor_location": { + "country_code": "GB", + "country_name": "United Kingdom", + "region": "ENG", + "region_name": "England", + "city": "Louth", + "postal_code": "LN11", + "location": { + "lat": 53.4457, + "lon": 0.141 + } + }, + "data": { + "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) ...", + "method": "POST", + "request_id": "2773abeb-477f-4ebf-a017-f8e8a206c305", + "server_id": "796e3115-4ce8-4606-8fd0-99ea57a2e12b", + "request_category": "other", + "controller_action": "create", + "url": "https://example.com/octo-org/octo-repo/pull/create?base=octo-org%3Amain&head=mona%3Apatch-1", + "client_id": 386351111.163594, + "referrer": "https://example.com/octo-org/octo-repo/compare/main...mona:patch-1", + "actor_session": 2, + "pull_request_id": 1, + "category_type": "Resource Management" + } + } + ] + } + } + } + } + } + }, + "x-github": { + "githubCloudOnly": true, + "enabledForGitHubApps": true, + "category": "orgs", + "subcategory": null + } + } + }, "/orgs/{org}/external-group/{group_id}": { "get": { "summary": "Get an external group", @@ -115529,6 +116321,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -115543,6 +116342,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -120384,6 +121209,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -120768,6 +121594,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -120782,6 +121615,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -125623,6 +126482,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -125649,8 +126509,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -125684,6 +126545,22 @@ "site_admin": false }, "run_attempt": 1, + "referenced_workflows": [ + { + "path": "octocat/Hello-World/.github/workflows/deploy.yml@main", + "sha": "86e8bc9ecf7d38b1ed2d2cfb8eb87ba9b35b01db", + "ref": "refs/heads/main" + }, + { + "path": "octo-org/octo-repo/.github/workflows/report.yml@v2", + "sha": "79e9790903e1c3373b1a3e3a941d57405478a232", + "ref": "refs/tags/v2" + }, + { + "path": "octo-org/octo-repo/.github/workflows/secure.yml@1595d4b6de6a9e9751fb270a41019ce507d4099e", + "sha": "1595d4b6de6a9e9751fb270a41019ce507d4099e" + } + ], "run_started_at": "2020-01-22T19:33:08Z", "triggering_actor": { "login": "octocat", @@ -125711,6 +126588,7 @@ "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", + "previous_attempt_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/attempts/1", "workflow_url": "https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038", "head_commit": { "id": "acb5820ced9479c074f688cc328bf03f341a511d", @@ -126266,6 +127144,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -126280,6 +127165,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -131121,6 +132032,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -131147,8 +132059,9 @@ "node_id": "MDEyOldvcmtmbG93IFJ1bjI2OTI4OQ==", "check_suite_id": 42, "check_suite_node_id": "MDEwOkNoZWNrU3VpdGU0Mg==", - "head_branch": "master", + "head_branch": "main", "head_sha": "acb5820ced9479c074f688cc328bf03f341a511d", + "path": ".github/workflows/build.yml@main", "run_number": 562, "event": "push", "status": "queued", @@ -131182,6 +132095,22 @@ "site_admin": false }, "run_attempt": 1, + "referenced_workflows": [ + { + "path": "octocat/Hello-World/.github/workflows/deploy.yml@main", + "sha": "86e8bc9ecf7d38b1ed2d2cfb8eb87ba9b35b01db", + "ref": "refs/heads/main" + }, + { + "path": "octo-org/octo-repo/.github/workflows/report.yml@v2", + "sha": "79e9790903e1c3373b1a3e3a941d57405478a232", + "ref": "refs/tags/v2" + }, + { + "path": "octo-org/octo-repo/.github/workflows/secure.yml@1595d4b6de6a9e9751fb270a41019ce507d4099e", + "sha": "1595d4b6de6a9e9751fb270a41019ce507d4099e" + } + ], "run_started_at": "2020-01-22T19:33:08Z", "triggering_actor": { "login": "octocat", @@ -131209,6 +132138,7 @@ "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", + "previous_attempt_url": "https://api.github.com/repos/octo-org/octo-repo/actions/runs/30433642/attempts/1", "workflow_url": "https://api.github.com/repos/octo-org/octo-repo/actions/workflows/159038", "head_commit": { "id": "acb5820ced9479c074f688cc328bf03f341a511d", @@ -134315,6 +135245,13 @@ "009b8a3a9ccbb128af87f9b1c0f4c62e8a304f6d" ] }, + "path": { + "description": "The full path of the workflow", + "type": "string", + "examples": [ + "octocat/octo-repo/.github/workflows/ci.yml@main" + ] + }, "run_number": { "type": "integer", "description": "The auto incrementing run number for the workflow run.", @@ -134329,6 +135266,32 @@ 1 ] }, + "referenced_workflows": { + "type": [ + "array", + "null" + ], + "items": { + "title": "Referenced workflow", + "description": "A workflow referenced/reused by the initial caller workflow", + "type": "object", + "properties": { + "path": { + "type": "string" + }, + "sha": { + "type": "string" + }, + "ref": { + "type": "string" + } + }, + "required": [ + "path", + "sha" + ] + } + }, "event": { "type": "string", "examples": [ @@ -139170,6 +140133,7 @@ "status", "conclusion", "head_sha", + "path", "workflow_id", "url", "html_url", @@ -145401,7 +146365,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -151530,7 +152494,7 @@ "url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions", "users_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/users", "teams_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", - "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/teams", + "apps_url": "https://api.github.com/repos/octocat/Hello-World/branches/master/protection/restrictions/apps", "users": [ { "login": "octocat", @@ -309663,13 +310627,7 @@ "githubCloudOnly": false, "enabledForGitHubApps": true, "category": "repos", - "subcategory": "pages", - "previews": [ - { - "name": "switcheroo", - "note": "Enabling and disabling Pages in the Pages API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/) preview for more details. To access the new endpoints during the preview period, you must provide a custom [media type](https://docs.github.com/github-ae@latest/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.switcheroo-preview+json\n```" - } - ] + "subcategory": "pages" } }, "put": { @@ -310094,13 +311052,7 @@ "githubCloudOnly": false, "enabledForGitHubApps": true, "category": "repos", - "subcategory": "pages", - "previews": [ - { - "name": "machine-man", - "note": "To access the API with your GitHub App, you must provide a custom [media type](https://docs.github.com/github-ae@latest/rest/overview/media-types) in the `Accept` Header for your requests. ```shell application/vnd.github.machine-man-preview+json ```" - } - ] + "subcategory": "pages" } } }, @@ -359684,7 +360636,7 @@ { "name": "secret_type", "in": "query", - "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/github-ae@latest/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types (API slug).", + "description": "A comma-separated list of secret types to return. By default all secret types are returned.\nSee \"[Secret scanning patterns](https://docs.github.com/github-ae@latest/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security)\"\nfor a complete list of secret types.", "required": false, "schema": { "type": "string" @@ -445734,7 +446686,7 @@ "/users/{username}/suspended": { "put": { "summary": "Suspend a user", - "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).\"", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/github-ae@latest/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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" @@ -445770,7 +446722,7 @@ "properties": { "reason": { "type": "string", - "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." + "description": "The reason the user is being suspended. This message will be logged in the [audit log](https://docs.github.com/github-ae@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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." } } } @@ -445786,7 +446738,7 @@ }, "delete": { "summary": "Unsuspend a user", - "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.", + "description": "If your GitHub instance uses [LDAP Sync with Active Directory LDAP servers](https://docs.github.com/github-ae@latest/admin/identity-and-access-management/using-ldap-for-enterprise-iam/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" @@ -445822,7 +446774,7 @@ "properties": { "reason": { "type": "string", - "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." + "description": "The reason the user is being unsuspended. This message will be logged in the [audit log](https://docs.github.com/github-ae@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise). 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.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br index ee6192fbc6..729110c296 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:4985bcd539135928f1a46f8da342ad2d1e1b9d8a80d7281e7443c0159b2a0085 -size 683471 +oid sha256:7b0fbab5cd3a8ab6cc53a2de7f333289c4efa1089b7782629172d9610becee63 +size 686792 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 9ab5125e7c..e10a18a6d5 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:35a7ee0c5eb66d9b15f8185f36bdf45f086424f02d2f23c595f8daddcee7a036 -size 1330709 +oid sha256:f888dea4d035ba8f0c234982edae4343e9cd33d211a14b15711814b6fbb70386 +size 1335316 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 747c4f4bc9..7e41d09449 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:224fc4ac5ef05c9f9c4aaa91011b57eaf06e40eea11f6ee85d36c67c1e22893f -size 912642 +oid sha256:472df7108b23b13783d6a346c774bd8ddc5aadb5e3a8eb8098b242d2f4fc697f +size 916672 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 aa47601b92..389c8cf07b 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:da81c31fdca5c55de89f8082d602f7efde7648b460193a4b1025d1f06b6c2f3e -size 3519873 +oid sha256:eedc2a155f6de8527daaa67528c47fd4e058af9131509bfb6fc741aa25d412d4 +size 3536178 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 f60ecb1948..3255c3bb65 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:61bc248a5e3fc422863c7546bb18a5bf9a32d8a7c6cc51fa9747659d0597c448 -size 630192 +oid sha256:56b42617e51ba0a928c2dde3455c977eb579514062a57af6994d5e6d1ee12e05 +size 632815 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 d96411c453..54cd4e06e3 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:c74c0313edcf08438ec587ccae67f1f8da67a9e2d8b70f156efa986368388c99 -size 2661968 +oid sha256:838e4915a733dfa992394795794be8e602799132b0f8dfea1f4a28983a8b1c9c +size 2676256 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 3ddaceae21..2991f5ddb3 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:d2ce77ed6d2386509a2c6d35e7dbd7fedb01ba2885a1b7ceba636010a1ca33ad -size 694648 +oid sha256:c6d059acfe555621460fb31b5d622e2e2c11e8bf905d946edbdf8af0353d0f21 +size 697189 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 9e68150124..e62cdaf797 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:d14496d977d949a4733627148c2e95478e0ff7782a0ce41836a3ede363c305e4 -size 3702840 +oid sha256:9f32f7b694ef08375527e13c7c16dae336192ac82a9723cf79bb0b4fd636931e +size 3720006 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 5313cd8464..de09ae3039 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:a76429a535285fedb118b0f07b7424f944cb4633a89819d2ac208eb74c0446d7 -size 622558 +oid sha256:57fddf99c5c5f510ffe8cf8e82629053528669b01f304308198146374013edf3 +size 624009 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 303df02052..ad518e6e39 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:7556f1eb4cc8786cbba3b98755471f0da9929a4544f595e05930c038c136baa0 -size 2563066 +oid sha256:2d3ba81cb7ab216eeea5b9fd5d795774e838292d35a1a6afabdce1480a4dd9ab +size 2564408 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 535951f337..25bcbf1d35 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:7f82918321a2b3aaf0b6ae94ae9610b027aeeda9ad44807770d0966d2f4ec2e3 -size 702228 +oid sha256:adde953631d672eaf7f348912fec6d37f698f5baff1fdb03653a9afd845b7075 +size 704278 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 d8673fe1eb..4bebeadce0 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:8ce63434ef0b5ffad4a435bc8ecd2f844787c14114fe1eb86caa48eaa70ebc1a -size 1357823 +oid sha256:12c9a99c77991d3a02d0c679b254100226145c1b2c1ea42844001fa45934bd80 +size 1362836 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 05a8d8520c..879f751df2 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:b61469c436869f6958926a3cbea33ebf4e08684faff5149283e1cadfba16f500 -size 944266 +oid sha256:a82f59fbf50322be80694bfc432d5ca4e92685aaa73801ed355d1c820e0e8886 +size 947343 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 00e7aa4c03..f9f3fc3766 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:dce9130d5780ad54ddefd9a32551db67c9a8134dbef5f3db5b34b3f3b82b2d02 -size 3642519 +oid sha256:d64b528fe55303bc3df0d09367bc424749e972f1d61973b90263a3128287a607 +size 3657565 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 abac8abb7b..9141ad668b 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:16d1e55afe1dfeb7ba60b8d4839d16d3ca4e0c60374d9526f3b9de7bc2a41cf7 -size 646799 +oid sha256:69e2e547760d831c609ebda99342a784c0fa35ee533f6019d3b00289d2f0a811 +size 648869 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 57c0710120..2be8a16777 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:81692fb609a8fb79e98746edfadc0a4ec50d81b9a9262ed2f0f982b46f4ad857 -size 2734259 +oid sha256:82edd72d453672455717ade571f7b2629fdc88aba187adf6b21aa5263e0845df +size 2745531 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 69fc3fb506..7e48558cc7 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:8078fd8358bf906a8068c47faaffe9d55f2301b94cab0ad9299074b881b4d7d0 -size 712062 +oid sha256:b7ddf47e538441aa034023a63725c1a1fb10f51838b9e8fba11eeeaf15732e9c +size 714695 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 92a8b1c9b6..92bdc1ff8c 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:49c1f69530dfd744f1998c60c79554d8772f49484cb805cad551c90843d5f118 -size 3797721 +oid sha256:0255d9b26dbde6d8731c981d827d01b0bc8333f39084f213dde19da9260e28ba +size 3815001 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 8152638929..4c6647dfc8 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:50f35d36196c29b725444a38fdf6472816a0eb846ef99d96e1eebbba5e0f8198 -size 638151 +oid sha256:490031c8aae067ce69a7f186a53ccbfaf474235ca16fdc341296b9a0edbb50f9 +size 640638 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 befaef1420..9329a31fd9 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:17062c0a55d30904002601c509be444b295ff01f31ba239fb55a6c9468366de7 -size 2624971 +oid sha256:5df2a1e1292efc23de07842810f4a2e5472ef168949092bf0b2d2ca7b0fba1b7 +size 2629184 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 5c7e9e0374..79bd9ebbd0 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:3f506b9f6af1ca20050710ff715b047f56be42683c5a6f1bedce076a6023bb2a -size 725705 +oid sha256:2bd67f9c5b8538a44ab76f7e8845f81a7a6b66b6beb884c03672e1598413ffcc +size 727387 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 720add9f6f..d8b9a01805 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:dd4021c615897c81a6619a88bebbbd213d6a0d71c9c44d5348637bc2160d8da4 -size 1403772 +oid sha256:23a4e064332155deff78e8d51372c7aeb1cf9a3f0b9a01d94c4e293900ddcdae +size 1406708 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 cffc393851..e81e9f77f3 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:c6e4f08ff1ff6f5f6f786bdef2632514d62a21a64b66e02bd2fa7684e2c26bdf -size 980822 +oid sha256:1cee321f1f37e3e8e5eac1bd618d5f3f45bbbe472d8985e65aa3f1363e47f77c +size 981698 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 92536eb3d9..2594e8e3c3 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:0ebdaa6cd78f43b2b34472f551b79ad49f231af8bcde0b2c9c7abf13c8112cd9 -size 3759878 +oid sha256:f7c04fc7bb1aa4b7273be300a5cc052d856de428889bab6e9464ac01d7ef2359 +size 3774983 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 62f67f5f29..60afc837aa 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:bb5a8cfdd167d8b2f98e279fafe6612fb1d01a530903afcfad0ff6979466c65d -size 666947 +oid sha256:4477a83f0c9827559284277735d642d24794accc82fb7f7db8a4340655ba492e +size 668007 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 81fb62ee13..43bdb12a39 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:288cccbbbe02a94e3ddb6d6dd0e55883ce6156a312a75d990b3fe4a1679b4cc4 -size 2821054 +oid sha256:a51ece9978d2f02549078b7c992dc72f83bd2ce5aebda5ea036a684c8350ed64 +size 2829933 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 5a4c5bcfe1..48d825817a 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:0cd96d6496b29fc907c72887843e287ab5940f424d5c439133f37f4a86347f9f -size 735524 +oid sha256:0c1804547bc633626ff9da9e9c102b1090dde3cf92fdcf3ff175e3ba4157c3d2 +size 736900 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 02b9cd83ea..6b9977591f 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:dee24dcb390959a8f38a743c48f57dee844fdb16b205cfbc642d56b568b2849c -size 3921625 +oid sha256:ea6b2bffd32b4b41fd243d784c10ff089ed302e93cf601b626c9518cc814cde4 +size 3939805 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 4cafb138e9..504214d638 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:96b271bf153d9aa0156a9d1d782eac6ada64c52ec1c479650090577c13b9f564 -size 657631 +oid sha256:f37385b14af7e062e77cf980180a736548f5c9cf5d7bd46d7d98faed7749a7ea +size 658943 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 01a5a9aee2..444e5f49c8 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:5183f1b16152a1c123b7c7ca3647006b80483001d5b6243a56a8c5709775396e -size 2707630 +oid sha256:1d7a1d1b66680a2ff34a7488273ede454c3295e450e082362a339a6e001f492c +size 2709277 diff --git a/lib/search/indexes/github-docs-3.4-cn-records.json.br b/lib/search/indexes/github-docs-3.4-cn-records.json.br index 94d92bff41..523462a60c 100644 --- a/lib/search/indexes/github-docs-3.4-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.4-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f5661373ca659714a4d1f74840f2f71e506fec1a0a6425b1b9212ae2b62bdf60 -size 725602 +oid sha256:e9a003f8af6a7939812e5b558a022a1196a44d5ba8a8558e560c886ce64c9eb7 +size 727549 diff --git a/lib/search/indexes/github-docs-3.4-cn.json.br b/lib/search/indexes/github-docs-3.4-cn.json.br index d2be87a11b..d5600b8026 100644 --- a/lib/search/indexes/github-docs-3.4-cn.json.br +++ b/lib/search/indexes/github-docs-3.4-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:49b3951e4c73e5385521762fcdfa80c80f3f5800018203a6777098f3ed851d20 -size 1405675 +oid sha256:e99a95b0fedc02678699ba979532ba1791524f36f08df9d49693027b465ea4ce +size 1409197 diff --git a/lib/search/indexes/github-docs-3.4-en-records.json.br b/lib/search/indexes/github-docs-3.4-en-records.json.br index 43d557ede4..b1efccbddd 100644 --- a/lib/search/indexes/github-docs-3.4-en-records.json.br +++ b/lib/search/indexes/github-docs-3.4-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2487569043be49bae3520158e59ec10c5d317265ef9032f7f232e0f1cca6a1bf -size 986796 +oid sha256:9b0be5f78d2575167d263a2fbcb498e20c469a77ab66e7cce8d6ac65c63f6140 +size 988174 diff --git a/lib/search/indexes/github-docs-3.4-en.json.br b/lib/search/indexes/github-docs-3.4-en.json.br index 6dc616816d..eaf9941792 100644 --- a/lib/search/indexes/github-docs-3.4-en.json.br +++ b/lib/search/indexes/github-docs-3.4-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c9a85a63818045ced06d5612964db9ae2ff0a1452d290951093d708cf1823a81 -size 3779300 +oid sha256:87cc3623cc6ab206d5aed4f182105831e8eba78c36600face2cf78b158ff2be2 +size 3792353 diff --git a/lib/search/indexes/github-docs-3.4-es-records.json.br b/lib/search/indexes/github-docs-3.4-es-records.json.br index abda4228e2..0944276212 100644 --- a/lib/search/indexes/github-docs-3.4-es-records.json.br +++ b/lib/search/indexes/github-docs-3.4-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:40ded9b7832d76f8ee2c0be6db86ea4d88c611b45899b3b11a90e8eebb03a2ab -size 668684 +oid sha256:6d5e730dad831985ddd3797253ed687c8fc489449b468e1c170b4914d8fcb9fa +size 669941 diff --git a/lib/search/indexes/github-docs-3.4-es.json.br b/lib/search/indexes/github-docs-3.4-es.json.br index b6f3406768..1c27f238ec 100644 --- a/lib/search/indexes/github-docs-3.4-es.json.br +++ b/lib/search/indexes/github-docs-3.4-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c8ed0bb506071ca7e16b6f3afed467eba3e073cad21f26d9e14c099f50fec237 -size 2827243 +oid sha256:24ae45626ed5339974780420c4ea4a2a1045cec175421c46f0ecd20fe2af474f +size 2834101 diff --git a/lib/search/indexes/github-docs-3.4-ja-records.json.br b/lib/search/indexes/github-docs-3.4-ja-records.json.br index eaeb58f2eb..fe92f8de8a 100644 --- a/lib/search/indexes/github-docs-3.4-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.4-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5e9290e8c036792d972c24df4ca3139ea71d63d7fbf2bbfa0fae0a6c95e95b63 -size 736857 +oid sha256:bd8d8c7474392bc3c8cdd9be09e07473033e14f647c131107e5f7b4839b7e012 +size 737976 diff --git a/lib/search/indexes/github-docs-3.4-ja.json.br b/lib/search/indexes/github-docs-3.4-ja.json.br index 7c56b79f3b..63f2523e7e 100644 --- a/lib/search/indexes/github-docs-3.4-ja.json.br +++ b/lib/search/indexes/github-docs-3.4-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7b494cf596e2fa35e6ef760e8e123da626c7096970440e64ecf076656e833d93 -size 3930708 +oid sha256:0f609a812f293885f8f5185db30e66536a7a281a51527902c77c58f9bc3bbbbf +size 3944727 diff --git a/lib/search/indexes/github-docs-3.4-pt-records.json.br b/lib/search/indexes/github-docs-3.4-pt-records.json.br index 3c92bf8a66..b864b9b9d0 100644 --- a/lib/search/indexes/github-docs-3.4-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.4-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:25bdff9c2c9a1beedcf23c4b48c45429257c8dcd9e77875c54770d6531e92603 -size 659734 +oid sha256:e0a1132d0090c69514ae86b42a75f8b40655f528da4ac3b9a2070938d348e4b7 +size 660499 diff --git a/lib/search/indexes/github-docs-3.4-pt.json.br b/lib/search/indexes/github-docs-3.4-pt.json.br index 5178188e7d..96f50dd042 100644 --- a/lib/search/indexes/github-docs-3.4-pt.json.br +++ b/lib/search/indexes/github-docs-3.4-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f1df374cafca8c031d783677cc64667d9492cfde516a6b87ecd28028c93bfc8f -size 2714849 +oid sha256:2aa5fc206736dcb5f29da6251b55febd93cff3fc7a21b9ecd58da10c513eec70 +size 2714670 diff --git a/lib/search/indexes/github-docs-3.5-cn-records.json.br b/lib/search/indexes/github-docs-3.5-cn-records.json.br index dd50d862a9..453c373ceb 100644 --- a/lib/search/indexes/github-docs-3.5-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.5-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5f2619aee63dce3eaf4c677e23460f7e77531de1f047a8086351cb57a94a8f0d -size 751195 +oid sha256:9cf92a53e14fb0362cdf16041b6c891b29d3bf84c77cd325570d2414e7c2522b +size 754151 diff --git a/lib/search/indexes/github-docs-3.5-cn.json.br b/lib/search/indexes/github-docs-3.5-cn.json.br index 419bd06237..05f83bdf80 100644 --- a/lib/search/indexes/github-docs-3.5-cn.json.br +++ b/lib/search/indexes/github-docs-3.5-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b0f31f100694995ad8ba6e43e1a9637f537ff1478721999ee791b66048d5d8d8 -size 1460649 +oid sha256:9e1a20e5eb5cc95fbb3578cdd944153b7dfe3475051cdfef2ee5f32f9bf5e255 +size 1467400 diff --git a/lib/search/indexes/github-docs-3.5-en-records.json.br b/lib/search/indexes/github-docs-3.5-en-records.json.br index 0cc3b7b48e..67043a419a 100644 --- a/lib/search/indexes/github-docs-3.5-en-records.json.br +++ b/lib/search/indexes/github-docs-3.5-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:843138209fb429c2810a07b6f25cd31c628100c2ada4571fdbd8e8638d1de4bd -size 1019287 +oid sha256:8891408b19c407bee082be87ef74c1e5a946be99315ff6a5ce625fe770a85088 +size 1023535 diff --git a/lib/search/indexes/github-docs-3.5-en.json.br b/lib/search/indexes/github-docs-3.5-en.json.br index 39c31b6c2d..db5b29b442 100644 --- a/lib/search/indexes/github-docs-3.5-en.json.br +++ b/lib/search/indexes/github-docs-3.5-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1af42ade1d1b6be2995f871bd69a2618a977a0348f401ff994a2fa5888a705e1 -size 3911928 +oid sha256:88b29fff74e647de8b21b1c0cab2e1df40aba7fac79d91e6d721e3e122c3b236 +size 3929241 diff --git a/lib/search/indexes/github-docs-3.5-es-records.json.br b/lib/search/indexes/github-docs-3.5-es-records.json.br index 45efa2a6d1..05cfef1a9f 100644 --- a/lib/search/indexes/github-docs-3.5-es-records.json.br +++ b/lib/search/indexes/github-docs-3.5-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:07d5a2f18f25e72a66b47c2710bbcbe6622443b7a6ecb4ab69a6977cfcf175d9 -size 689730 +oid sha256:de6bf0c9b64d962b71b9ce714d1ea91ea9945ab176aeb58fe09fba0751143a85 +size 691367 diff --git a/lib/search/indexes/github-docs-3.5-es.json.br b/lib/search/indexes/github-docs-3.5-es.json.br index f51b73b108..ad3474e7fb 100644 --- a/lib/search/indexes/github-docs-3.5-es.json.br +++ b/lib/search/indexes/github-docs-3.5-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:52a53f5703462ed933519d386bb6d55ff06c6d89009d6c6fc27270a3985bfa05 -size 2936597 +oid sha256:6ec582529762b22e3e23fef174c91329eead9fd71cfd97fe8f5f52d84fe41d1c +size 2946540 diff --git a/lib/search/indexes/github-docs-3.5-ja-records.json.br b/lib/search/indexes/github-docs-3.5-ja-records.json.br index cb6715692a..12b8166c5e 100644 --- a/lib/search/indexes/github-docs-3.5-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.5-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9155a58061874348b8197637f8ee398f0d3b24fd22006c9726a182e31669daa8 -size 759920 +oid sha256:994d35d8147cb5337f16144c1fc4d0a6d54e4ce9c0b764a0434b03bcd7ded109 +size 760653 diff --git a/lib/search/indexes/github-docs-3.5-ja.json.br b/lib/search/indexes/github-docs-3.5-ja.json.br index c8b6544abe..9bb4b37829 100644 --- a/lib/search/indexes/github-docs-3.5-ja.json.br +++ b/lib/search/indexes/github-docs-3.5-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1138949f70dd78b838067c01d1e2ce6ad82e7f23e62b8302166fdfc8e53a4625 -size 4072198 +oid sha256:4b09191fb34b6814ebfc8eb65ae822ed2ce88c9c94589b648e10e18e8c946efd +size 4087455 diff --git a/lib/search/indexes/github-docs-3.5-pt-records.json.br b/lib/search/indexes/github-docs-3.5-pt-records.json.br index 7feb45a78a..73282dfffa 100644 --- a/lib/search/indexes/github-docs-3.5-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.5-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:17fd737b67a347f0f97a096a9489c89ff5d0cccd6a9bd0037103a3c99392681b -size 680219 +oid sha256:6bd37ebd55f4b617d9116ca3e81b08ae4630575c6245744cee8b018f846b5385 +size 681109 diff --git a/lib/search/indexes/github-docs-3.5-pt.json.br b/lib/search/indexes/github-docs-3.5-pt.json.br index 60f5466ef7..5dded8848c 100644 --- a/lib/search/indexes/github-docs-3.5-pt.json.br +++ b/lib/search/indexes/github-docs-3.5-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a4aa98be0f2a202f6742b00bbc10894157231ca551ba904d5b013f6ad97f2f6d -size 2817873 +oid sha256:73d9dd4649963903a21d7a1108ed1a5cca18e93f6ba5b4d1745eba0b6f2c6e14 +size 2812039 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 199bf8977f..d3a5bf39cc 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:4908344fc8d1cf54b37f7913d30badb21e0d54115a8fcdcbd0427d4019de542e -size 925352 +oid sha256:f97a7a48214ff9949450e862f664e8ba276dc56f1eae17f741ee4f7c730ec2f7 +size 927862 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index 387f9d60c1..13f9af7a30 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:e90a0b0ad27750f4ed2390bb909d54a44bb0dedec5e1f5c8200c0b0cc9a73109 -size 1445650 +oid sha256:8f428b7558d27a74cf8cac9ecd592ef99030ffedf98c6a732123012952ab2637 +size 1457914 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 73ce749520..c4c19d43e0 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:e665e69f72bb2278b013f32ed4b89357c10d1ab238679200fcc92fc4b10476c0 -size 1245978 +oid sha256:0b1eccd4b68440d8e65a6b41913a69e6c85826e5aa11de896e7c6dd6bf7e0f74 +size 1252336 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index dba85e8404..32a4625516 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:0ad918c7c96f9f2b4d1b482afd8ebdc3b28f90e75f459f00b3b530719a94185c -size 4501843 +oid sha256:31dbe7d7e5622b1ff9487a446aa240ab2959b3013441402db54c0a2a30fe72d3 +size 4525901 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 e036651c16..234fbeff73 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:752a3481605f31d1f09cf4a433c4d62cd9229ce2085bc7eb16eed5a80de71638 -size 831540 +oid sha256:c75ebc689ee51bfc3ac8ed077bc1ee7b1c894f4dbaa3943aac8a37d713dcb33c +size 833144 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index 95e1ee2ec2..2d8d1aba3f 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:93d59c515ce6a89eec3f1a4077f769df30c6aabdf34171c7ce991300689ff705 -size 3336412 +oid sha256:e81da33e98a3d659a75024608809d36123dd5e132bc2564a75dd6c81428e06bf +size 3350496 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 777af31595..f398c1f8d8 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:b6b5f084423bb7be102935d42631b0be58c094e1391cf0b70d665ffa9c832b80 -size 930677 +oid sha256:213df33693ebf855ba81f6762a8af1715a1c895d8797598e01cd5df266bff696 +size 931902 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index 53e47c7336..d23fce57f3 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:fd5e8e2f615f5a37c8f68d4bbebe7c347e5927b5b1f019b6b48b8eca1cc19543 -size 4741141 +oid sha256:fade5d57b4c7e955f2b7ad5fdd01df22d581872f1e04969fc58350aa69e0ff68 +size 4761700 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 9ee93c6151..ef54ed9ff5 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:2f9dae4eaef59ee1b81aec252def204946276ca48587df8033adc11ba1c8f6b1 -size 820558 +oid sha256:0d87b4ea68091434f21630ef3b325ab68f934c82144510f8b74400e1d2c3473c +size 823613 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index 1c9cb9a7ac..350e900569 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:8b978c435624489191c5b9f6f4ec8cff437506b812490a517c1b6b2b6f6c80a4 -size 3219270 +oid sha256:3f10962ccbbe47a66e7f5eff8428beba72a94141415b95701c1c4d160e46d9bc +size 3225126 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 5baa525230..d6115808d6 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:72e80fd174d697b82d16db7045412274bbb23faac0be85689158521c8f6262b5 -size 546983 +oid sha256:0881bba8aae7edfe53c9b161738c1b13a48062faf085d60202c13d16e4c38d93 +size 567867 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index 3184916205..df8339ebb6 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:fc6baa9a661a3a0d382f2baf6febc46238eba3424d740b1f10c78d9432486d91 -size 1002002 +oid sha256:fec61fb3eec8ef8bc00b5ffab4ee2ea4c0093bd97a65e085e413af5376a4fbfb +size 1042870 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 1921d24b9f..a96a949d22 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:56a2f16409a275b12eba08aa8220c3820a8634c780e6f7c53c51920c43e1d58a -size 758098 +oid sha256:463a78c1dc381e05116569ad7be31a7b2f49e5cf9edba9dd970906441272e9d0 +size 779687 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index 73a851d190..4405528a90 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:2432009bd4b9edcef529d12eb2a99371aee4f006cf3ed911a91daee299a76240 -size 2871420 +oid sha256:b18415482249690ba9c731cecaee75cd8408d515bb9f23bd5c5f1a074831a87c +size 2954885 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 6b07245a42..f8ebfbac11 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:1b2a735e07b422a2ce3c085552a36ed407e2b755e71e749ed60b6ae0216fd3b1 -size 507750 +oid sha256:b7940d640f7cd3d1d8e75e41e6ca05f18f225d6bec397d7df38a1b8def2bb760 +size 526642 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index 9e6765207a..1b33b07ce8 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:4ae8fa8c2abd3113d78063b46833179ac74a652d271d4f86b6fd7076cd934824 -size 2057009 +oid sha256:bf8416c25d202e26c502a3047875a3d979459eb34b89f90cdd5aadaa5a680658 +size 2141933 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 69a57fac2b..f8d15e7092 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:6ca5b7660b02ab73fdb7ae8eceac395ea4ba07ee20a16f3d783592763ac4348a -size 558298 +oid sha256:ee8c8bcdd0fe51f431e90a527341f8ecf400a2d93e131ebffef26910e3cbd99f +size 577800 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index c01be5bd07..e5e7aff4e2 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:0d394e4d7428cd238d66a0c1f0db24acc6eea069aeba0263e9ace588d081473c -size 2845527 +oid sha256:c5df9bc73a7466619b094e5aec6bb13084ca718c4ecf12bf5cdced59686535f6 +size 2954735 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 ee3747779e..accfbd95a3 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:2dda68a2329b615b618d626fd656a06d41098dcf4daceca0cde10be20d62a200 -size 501153 +oid sha256:71beabe8b388047b5404512bcce1871434d782c241d4946f7eac007eaaaee284 +size 520531 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index 0d9fa00112..375b292519 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:4fb284b1864e59cef0990d84ef90236460f34aff77146d891da3bcc41ae2ee33 -size 1962894 +oid sha256:0e7f5e22ce2dfdfad496d44d4db380958199a4d06f3649f4ab5972a19459d1e7 +size 2035527 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 3c9350923c..f8fe6d5422 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:e89ee2b755ef8fa290d9db40464cd24bb512a519a6a81e068a98e63253d084a8 -size 872617 +oid sha256:8ab20d55053ffa5e148c1773afe9050cd1163efe6d55c55de2a933a66140970b +size 877070 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index f05ca1fe6a..23bde35ef8 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:6db25c0a1d8196a569f1fa9b9f33b95401cfbd341ae507e5f5552249f974aa08 -size 1541258 +oid sha256:c45ba2c6202143fe0838bb53bc0cc08d0d3ade5d90e374e68b1f1ed1525a9139 +size 1551260 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 4ae86210ee..deeb075678 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:c32e6ea2d1f6aeb922ea811c7b7fead93813396f48e2953dd2016f07449e37cd -size 1156252 +oid sha256:43f5a711707000007b8e0cf1a37e056069f214a66f8b69d5cab0d3aaaea26219 +size 1162583 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index e32622b16b..3043373267 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:fe8ce460329568a2c3dfb11f3fc332be760951fb64e5f4772b31fd71d9c4519e -size 4414333 +oid sha256:7da46a70ab12089e072c355db0ca0bc7a0c4f31bf192d64e683a7d8875f08524 +size 4438994 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 2a6fc8a111..a01ae48097 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:2b044ff52e6e3dc82f261e473aa480e5568825dfce75cea715f2e813d2f5f256 -size 805212 +oid sha256:469b1dfdbd6b8b80d2812913f3f91e219533936d20b2f9da355e72e62a010583 +size 807752 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index 2513d08374..21c8f124cf 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:1bbb1b8ff46d1f502a56dd2d383a6b35d78b540a3e1c28294bc9213dfe2c6508 -size 3393453 +oid sha256:6e9f625bc5552eb076f2dcba45e0957383e76bb2b4e93bdc6c190a679e871bba +size 3409293 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 943a29a318..9aaa0fc34f 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:a913bf99fdaf16fe7139309ac601a18183b389cc6cd7501486feca50cce3f7b2 -size 881025 +oid sha256:c5768668291c646d254da256443b8f451dd1ee584877e7c718ceee0705fd8317 +size 884045 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index 56262c0b19..11758e6e40 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:e9668515547e2d18cd6121c4ee1675a9e695d1a752db82e2dfe7c5a3f8a9dcb3 -size 4716374 +oid sha256:86667373fa0a8b2fc3d8851aecbb32f5ed5745346d6cd293be8e73e3ff7ec56b +size 4743870 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 193144fa48..bfc6bb35d6 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:e5eb93de4d6d750c4ccd46bf46a31bf79c04573cea757b2ac99ef0a617411850 -size 793847 +oid sha256:35c41b5db79210545d1617a4bf75a5e21869e4a14a53b8dfa499f5f83a8ef965 +size 796266 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index e8e35fa06c..876f4e7b8d 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:bae1fd77d6c56179b23eba30ece8bbe18666a0ca6184f17e17fb8a0d37c18d58 -size 3265569 +oid sha256:9753adb60a0612728dce71bef8250930160bedbba0aea2fb143315c868238a2e +size 3272142 diff --git a/middleware/fastly-cache-test.js b/middleware/fastly-cache-test.js new file mode 100644 index 0000000000..0ba8b28c91 --- /dev/null +++ b/middleware/fastly-cache-test.js @@ -0,0 +1,64 @@ +// +// This middleware function is intended to be used for testing caching behavior with Fastly. +// It will intercept ALL URLs that are routed to it and respond with a simple HTML body +// containing a timestamp. +// The logic will detect certain values in the path and set the HTTP status and/or the +// Surrogate-Control header value. +// +// NOTE: This middleware is intended to be removed once testing is complete! +// +export default function fastlyCacheTest(req, res, next) { + // If X-CacheTest-Error is set, simulate the site being down (regardless of URL) + if (req.get('X-CacheTest-Error')) { + res.status(parseInt(req.get('X-CacheTest-Error'))).end() + return + } + + const staleIfErrorParam = req.get('X-CacheTest-StaleIfError') ?? '300' + const staleWhileRevalidateParam = req.get('X-CacheTest-StaleWhileRevalidate') ?? '60' + + const path = req.params[0] + + let status = 200 + const surrogateControlValues = [] + + if (path.includes('must-revalidate')) surrogateControlValues.push('must-revalidate') + if (path.includes('no-cache')) surrogateControlValues.push('no-cache') + if (path.includes('no-store')) surrogateControlValues.push('no-store') + if (path.includes('private')) surrogateControlValues.push('private') + if (path.includes('proxy-revalidate')) surrogateControlValues.push('proxy-revalidate') + if (path.includes('public')) surrogateControlValues.push('public') + + if (path.includes('stale-if-error')) + surrogateControlValues.push(`stale-if-error=${staleIfErrorParam}`) + if (path.includes('stale-while-revalidate')) + surrogateControlValues.push(`stale-while-revalidate=${staleWhileRevalidateParam}`) + + if (path.includes('no-cookies')) { + res.removeHeader('Set-Cookie') + } + + if (path.includes('error500')) { + status = 500 + } else if (path.includes('error502')) { + status = 502 + } else if (path.includes('error503')) { + status = 503 + } else if (path.includes('error504')) { + status = 504 + } + + if (surrogateControlValues.length > 0) { + res.set({ + 'surrogate-control': surrogateControlValues.join(', '), + }) + } + + res.status(status) + res.send(` + +

Timestamp: ${new Date()}

+ +`) + res.end() +} diff --git a/middleware/index.js b/middleware/index.js index 62cd1517e4..2767f8d4bb 100644 --- a/middleware/index.js +++ b/middleware/index.js @@ -66,6 +66,8 @@ import setStaticAssetCaching from './static-asset-caching.js' import protect from './overload-protection.js' import fastHead from './fast-head.js' +import fastlyCacheTest from './fastly-cache-test.js' + const { DEPLOYMENT_ENV, NODE_ENV } = process.env const isDevelopment = NODE_ENV === 'development' const isAzureDeployment = DEPLOYMENT_ENV === 'azure' @@ -122,7 +124,7 @@ export default function (app) { // Only used in production because our tests can overload the server if ( process.env.NODE_ENV === 'production' && - !JSON.parse(process.env.DISABLE_OVERLOAD_PROTECTION | 'false') + !JSON.parse(process.env.DISABLE_OVERLOAD_PROTECTION || 'false') ) { app.use(protect) } @@ -330,6 +332,11 @@ export default function (app) { app.use(asyncMiddleware(instrument(featuredLinks, './featured-links'))) app.use(asyncMiddleware(instrument(learningTrack, './learning-track'))) + // The fastlyCacheTest middleware is intended to be used with Fastly to test caching behavior. + // This middleware will intercept ALL requests routed to it, so be careful if you need to + // make any changes to the following line: + app.use('/fastly-cache-test/*', fastlyCacheTest) + // *** Headers for pages only *** app.use(setFastlyCacheHeaders) diff --git a/middleware/overload-protection.js b/middleware/overload-protection.js index 6fbc80f983..a596fdee3c 100644 --- a/middleware/overload-protection.js +++ b/middleware/overload-protection.js @@ -1,7 +1,7 @@ import overloadProtection from 'overload-protection' // Default is 42. We're being more conservative. -const DEFAULT_MAX_DELAY_DEFAULT = 150 +const DEFAULT_MAX_DELAY_DEFAULT = 300 const OVERLOAD_PROTECTION_MAX_DELAY = parseInt( process.env.OVERLOAD_PROTECTION_MAX_DELAY || DEFAULT_MAX_DELAY_DEFAULT, diff --git a/package-lock.json b/package-lock.json index 6e4f6dd329..b32bf4ad71 100644 --- a/package-lock.json +++ b/package-lock.json @@ -101,7 +101,7 @@ "@babel/preset-env": "^7.16.11", "@graphql-inspector/core": "^3.1.1", "@graphql-tools/load": "^7.4.1", - "@jest/globals": "^27.4.6", + "@jest/globals": "^28.1.0", "@octokit/graphql": "4.8.0", "@octokit/rest": "^18.12.0", "@types/github-slugger": "^1.3.0", @@ -110,7 +110,7 @@ "@types/lodash": "^4.14.178", "@types/react": "^17.0.38", "@types/react-dom": "^18.0.0", - "@types/react-syntax-highlighter": "^13.5.2", + "@types/react-syntax-highlighter": "^15.5.1", "@types/uuid": "^8.3.4", "@typescript-eslint/eslint-plugin": "5.23.0", "@typescript-eslint/parser": "5.23.0", @@ -126,7 +126,7 @@ "domwaiter": "^1.3.0", "eslint": "8.11.0", "eslint-config-prettier": "^8.3.0", - "eslint-config-standard": "^16.0.3", + "eslint-config-standard": "^17.0.0", "eslint-plugin-import": "^2.25.4", "eslint-plugin-jsx-a11y": "^6.5.1", "eslint-plugin-node": "^11.1.0", @@ -143,7 +143,7 @@ "jest-fail-on-console": "^2.2.3", "jest-github-actions-reporter": "^1.0.3", "jest-slow-test-reporter": "^1.0.0", - "kill-port": "1.6.1", + "kill-port": "2.0.0", "linkinator": "^3.0.3", "lint-staged": "^12.3.3", "make-promises-safe": "^5.1.0", @@ -151,7 +151,7 @@ "mkdirp": "^1.0.4", "mockdate": "^3.0.5", "nock": "^13.2.2", - "nodemon": "^2.0.15", + "nodemon": "2.0.16", "npm-merge-driver-install": "^3.0.0", "postcss": "^8.4.6", "prettier": "^2.5.1", @@ -2481,49 +2481,579 @@ } }, "node_modules/@jest/environment": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/@jest/environment/-/environment-27.4.6.tgz", - "integrity": "sha512-E6t+RXPfATEEGVidr84WngLNWZ8ffCPky8RqqRK6u1Bn0LK92INe0MDttyPl/JOzaq92BmDzOeuqk09TvM22Sg==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/@jest/environment/-/environment-27.5.1.tgz", + "integrity": "sha512-/WQjhPJe3/ghaol/4Bq480JKXV/Rfw8nQdN7f41fM8VDHLcxKXou6QyXAh3EFr9/bVG3x74z1NWDkP87EiY8gA==", "devOptional": true, "dependencies": { - "@jest/fake-timers": "^27.4.6", - "@jest/types": "^27.4.2", + "@jest/fake-timers": "^27.5.1", + "@jest/types": "^27.5.1", "@types/node": "*", - "jest-mock": "^27.4.6" + "jest-mock": "^27.5.1" }, "engines": { "node": "^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0" } }, + "node_modules/@jest/expect": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/expect/-/expect-28.1.0.tgz", + "integrity": "sha512-be9ETznPLaHOmeJqzYNIXv1ADEzENuQonIoobzThOYPuK/6GhrWNIJDVTgBLCrz3Am73PyEU2urQClZp0hLTtA==", + "dev": true, + "dependencies": { + "expect": "^28.1.0", + "jest-snapshot": "^28.1.0" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect-utils": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/expect-utils/-/expect-utils-28.1.0.tgz", + "integrity": "sha512-5BrG48dpC0sB80wpeIX5FU6kolDJI4K0n5BM9a5V38MGx0pyRvUBSS0u2aNTdDzmOrCjhOg8pGs6a20ivYkdmw==", + "dev": true, + "dependencies": { + "jest-get-type": "^28.0.2" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect-utils/node_modules/jest-get-type": { + "version": "28.0.2", + "resolved": "https://registry.npmjs.org/jest-get-type/-/jest-get-type-28.0.2.tgz", + "integrity": "sha512-ioj2w9/DxSYHfOm5lJKCdcAmPJzQXmbM/Url3rhlghrPvT3tt+7a/+oXc9azkKmLvoiXjtV83bEWqi+vs5nlPA==", + "dev": true, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/@jest/transform": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/transform/-/transform-28.1.0.tgz", + "integrity": "sha512-omy2xe5WxlAfqmsTjTPxw+iXRTRnf+NtX0ToG+4S0tABeb4KsKmPUHq5UBuwunHg3tJRwgEQhEp0M/8oiatLEA==", + "dev": true, + "dependencies": { + "@babel/core": "^7.11.6", + "@jest/types": "^28.1.0", + "@jridgewell/trace-mapping": "^0.3.7", + "babel-plugin-istanbul": "^6.1.1", + "chalk": "^4.0.0", + "convert-source-map": "^1.4.0", + "fast-json-stable-stringify": "^2.0.0", + "graceful-fs": "^4.2.9", + "jest-haste-map": "^28.1.0", + "jest-regex-util": "^28.0.2", + "jest-util": "^28.1.0", + "micromatch": "^4.0.4", + "pirates": "^4.0.4", + "slash": "^3.0.0", + "write-file-atomic": "^4.0.1" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/@jest/types": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/types/-/types-28.1.0.tgz", + "integrity": "sha512-xmEggMPr317MIOjjDoZ4ejCSr9Lpbt/u34+dvc99t7DS8YirW5rwZEhzKPC2BMUFkUhI48qs6qLUSGw5FuL0GA==", + "dev": true, + "dependencies": { + "@jest/schemas": "^28.0.2", + "@types/istanbul-lib-coverage": "^2.0.0", + "@types/istanbul-reports": "^3.0.0", + "@types/node": "*", + "@types/yargs": "^17.0.8", + "chalk": "^4.0.0" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/@types/yargs": { + "version": "17.0.10", + "resolved": "https://registry.npmjs.org/@types/yargs/-/yargs-17.0.10.tgz", + "integrity": "sha512-gmEaFwpj/7f/ROdtIlci1R1VYU1J4j95m8T+Tj3iBgiBFKg1foE/PSl93bBd5T9LDXNPo8UlNN6W0qwD8O5OaA==", + "dev": true, + "dependencies": { + "@types/yargs-parser": "*" + } + }, + "node_modules/@jest/expect/node_modules/chalk": { + "version": "4.1.2", + "resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz", + "integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==", + "dev": true, + "dependencies": { + "ansi-styles": "^4.1.0", + "supports-color": "^7.1.0" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/chalk/chalk?sponsor=1" + } + }, + "node_modules/@jest/expect/node_modules/diff-sequences": { + "version": "28.0.2", + "resolved": "https://registry.npmjs.org/diff-sequences/-/diff-sequences-28.0.2.tgz", + "integrity": "sha512-YtEoNynLDFCRznv/XDalsKGSZDoj0U5kLnXvY0JSq3nBboRrZXjD81+eSiwi+nzcZDwedMmcowcxNwwgFW23mQ==", + "dev": true, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/expect": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/expect/-/expect-28.1.0.tgz", + "integrity": "sha512-qFXKl8Pmxk8TBGfaFKRtcQjfXEnKAs+dmlxdwvukJZorwrAabT7M3h8oLOG01I2utEhkmUTi17CHaPBovZsKdw==", + "dev": true, + "dependencies": { + "@jest/expect-utils": "^28.1.0", + "jest-get-type": "^28.0.2", + "jest-matcher-utils": "^28.1.0", + "jest-message-util": "^28.1.0", + "jest-util": "^28.1.0" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/jest-diff": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-diff/-/jest-diff-28.1.0.tgz", + "integrity": "sha512-8eFd3U3OkIKRtlasXfiAQfbovgFgRDb0Ngcs2E+FMeBZ4rUezqIaGjuyggJBp+llosQXNEWofk/Sz4Hr5gMUhA==", + "dev": true, + "dependencies": { + "chalk": "^4.0.0", + "diff-sequences": "^28.0.2", + "jest-get-type": "^28.0.2", + "pretty-format": "^28.1.0" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/jest-get-type": { + "version": "28.0.2", + "resolved": "https://registry.npmjs.org/jest-get-type/-/jest-get-type-28.0.2.tgz", + "integrity": "sha512-ioj2w9/DxSYHfOm5lJKCdcAmPJzQXmbM/Url3rhlghrPvT3tt+7a/+oXc9azkKmLvoiXjtV83bEWqi+vs5nlPA==", + "dev": true, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/jest-haste-map": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-haste-map/-/jest-haste-map-28.1.0.tgz", + "integrity": "sha512-xyZ9sXV8PtKi6NCrJlmq53PyNVHzxmcfXNVvIRHpHmh1j/HChC4pwKgyjj7Z9us19JMw8PpQTJsFWOsIfT93Dw==", + "dev": true, + "dependencies": { + "@jest/types": "^28.1.0", + "@types/graceful-fs": "^4.1.3", + "@types/node": "*", + "anymatch": "^3.0.3", + "fb-watchman": "^2.0.0", + "graceful-fs": "^4.2.9", + "jest-regex-util": "^28.0.2", + "jest-util": "^28.1.0", + "jest-worker": "^28.1.0", + "micromatch": "^4.0.4", + "walker": "^1.0.7" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + }, + "optionalDependencies": { + "fsevents": "^2.3.2" + } + }, + "node_modules/@jest/expect/node_modules/jest-matcher-utils": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-matcher-utils/-/jest-matcher-utils-28.1.0.tgz", + "integrity": "sha512-onnax0n2uTLRQFKAjC7TuaxibrPSvZgKTcSCnNUz/tOjJ9UhxNm7ZmPpoQavmTDUjXvUQ8KesWk2/VdrxIFzTQ==", + "dev": true, + "dependencies": { + "chalk": "^4.0.0", + "jest-diff": "^28.1.0", + "jest-get-type": "^28.0.2", + "pretty-format": "^28.1.0" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/jest-message-util": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-message-util/-/jest-message-util-28.1.0.tgz", + "integrity": "sha512-RpA8mpaJ/B2HphDMiDlrAZdDytkmwFqgjDZovM21F35lHGeUeCvYmm6W+sbQ0ydaLpg5bFAUuWG1cjqOl8vqrw==", + "dev": true, + "dependencies": { + "@babel/code-frame": "^7.12.13", + "@jest/types": "^28.1.0", + "@types/stack-utils": "^2.0.0", + "chalk": "^4.0.0", + "graceful-fs": "^4.2.9", + "micromatch": "^4.0.4", + "pretty-format": "^28.1.0", + "slash": "^3.0.0", + "stack-utils": "^2.0.3" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/jest-regex-util": { + "version": "28.0.2", + "resolved": "https://registry.npmjs.org/jest-regex-util/-/jest-regex-util-28.0.2.tgz", + "integrity": "sha512-4s0IgyNIy0y9FK+cjoVYoxamT7Zeo7MhzqRGx7YDYmaQn1wucY9rotiGkBzzcMXTtjrCAP/f7f+E0F7+fxPNdw==", + "dev": true, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/jest-snapshot": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-snapshot/-/jest-snapshot-28.1.0.tgz", + "integrity": "sha512-ex49M2ZrZsUyQLpLGxQtDbahvgBjlLPgklkqGM0hq/F7W/f8DyqZxVHjdy19QKBm4O93eDp+H5S23EiTbbUmHw==", + "dev": true, + "dependencies": { + "@babel/core": "^7.11.6", + "@babel/generator": "^7.7.2", + "@babel/plugin-syntax-typescript": "^7.7.2", + "@babel/traverse": "^7.7.2", + "@babel/types": "^7.3.3", + "@jest/expect-utils": "^28.1.0", + "@jest/transform": "^28.1.0", + "@jest/types": "^28.1.0", + "@types/babel__traverse": "^7.0.6", + "@types/prettier": "^2.1.5", + "babel-preset-current-node-syntax": "^1.0.0", + "chalk": "^4.0.0", + "expect": "^28.1.0", + "graceful-fs": "^4.2.9", + "jest-diff": "^28.1.0", + "jest-get-type": "^28.0.2", + "jest-haste-map": "^28.1.0", + "jest-matcher-utils": "^28.1.0", + "jest-message-util": "^28.1.0", + "jest-util": "^28.1.0", + "natural-compare": "^1.4.0", + "pretty-format": "^28.1.0", + "semver": "^7.3.5" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/jest-util": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-util/-/jest-util-28.1.0.tgz", + "integrity": "sha512-qYdCKD77k4Hwkose2YBEqQk7PzUf/NSE+rutzceduFveQREeH6b+89Dc9+wjX9dAwHcgdx4yedGA3FQlU/qCTA==", + "dev": true, + "dependencies": { + "@jest/types": "^28.1.0", + "@types/node": "*", + "chalk": "^4.0.0", + "ci-info": "^3.2.0", + "graceful-fs": "^4.2.9", + "picomatch": "^2.2.3" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/jest-worker": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-worker/-/jest-worker-28.1.0.tgz", + "integrity": "sha512-ZHwM6mNwaWBR52Snff8ZvsCTqQsvhCxP/bT1I6T6DAnb6ygkshsyLQIMxFwHpYxht0HOoqt23JlC01viI7T03A==", + "dev": true, + "dependencies": { + "@types/node": "*", + "merge-stream": "^2.0.0", + "supports-color": "^8.0.0" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/jest-worker/node_modules/supports-color": { + "version": "8.1.1", + "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-8.1.1.tgz", + "integrity": "sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==", + "dev": true, + "dependencies": { + "has-flag": "^4.0.0" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/chalk/supports-color?sponsor=1" + } + }, + "node_modules/@jest/expect/node_modules/pretty-format": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/pretty-format/-/pretty-format-28.1.0.tgz", + "integrity": "sha512-79Z4wWOYCdvQkEoEuSlBhHJqWeZ8D8YRPiPctJFCtvuaClGpiwiQYSCUOE6IEKUbbFukKOTFIUAXE8N4EQTo1Q==", + "dev": true, + "dependencies": { + "@jest/schemas": "^28.0.2", + "ansi-regex": "^5.0.1", + "ansi-styles": "^5.0.0", + "react-is": "^18.0.0" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/expect/node_modules/pretty-format/node_modules/ansi-styles": { + "version": "5.2.0", + "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-5.2.0.tgz", + "integrity": "sha512-Cxwpt2SfTzTtXcfOlzGEee8O+c+MmUgGrNiBcXnuWxuFJHe6a5Hz7qwhwe5OgaSYI0IJvkLqWX1ASG+cJOkEiA==", + "dev": true, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/chalk/ansi-styles?sponsor=1" + } + }, + "node_modules/@jest/expect/node_modules/react-is": { + "version": "18.1.0", + "resolved": "https://registry.npmjs.org/react-is/-/react-is-18.1.0.tgz", + "integrity": "sha512-Fl7FuabXsJnV5Q1qIOQwx/sagGF18kogb4gpfcG4gjLBWO0WDiiz1ko/ExayuxE7InyQkBLkxRFG5oxY6Uu3Kg==", + "dev": true + }, + "node_modules/@jest/expect/node_modules/slash": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/slash/-/slash-3.0.0.tgz", + "integrity": "sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==", + "dev": true, + "engines": { + "node": ">=8" + } + }, + "node_modules/@jest/expect/node_modules/write-file-atomic": { + "version": "4.0.1", + "resolved": "https://registry.npmjs.org/write-file-atomic/-/write-file-atomic-4.0.1.tgz", + "integrity": "sha512-nSKUxgAbyioruk6hU87QzVbY279oYT6uiwgDoujth2ju4mJ+TZau7SQBhtbTmUyuNYTuXnSyRn66FV0+eCgcrQ==", + "dev": true, + "dependencies": { + "imurmurhash": "^0.1.4", + "signal-exit": "^3.0.7" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || >=16" + } + }, "node_modules/@jest/fake-timers": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/@jest/fake-timers/-/fake-timers-27.4.6.tgz", - "integrity": "sha512-mfaethuYF8scV8ntPpiVGIHQgS0XIALbpY2jt2l7wb/bvq4Q5pDLk4EP4D7SAvYT1QrPOPVZAtbdGAOOyIgs7A==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/@jest/fake-timers/-/fake-timers-27.5.1.tgz", + "integrity": "sha512-/aPowoolwa07k7/oM3aASneNeBGCmGQsc3ugN4u6s4C/+s5M64MFo/+djTdiwcbQlRfFElGuDXWzaWj6QgKObQ==", "devOptional": true, "dependencies": { - "@jest/types": "^27.4.2", + "@jest/types": "^27.5.1", "@sinonjs/fake-timers": "^8.0.1", "@types/node": "*", - "jest-message-util": "^27.4.6", - "jest-mock": "^27.4.6", - "jest-util": "^27.4.2" + "jest-message-util": "^27.5.1", + "jest-mock": "^27.5.1", + "jest-util": "^27.5.1" }, "engines": { "node": "^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0" } }, "node_modules/@jest/globals": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/@jest/globals/-/globals-27.4.6.tgz", - "integrity": "sha512-kAiwMGZ7UxrgPzu8Yv9uvWmXXxsy0GciNejlHvfPIfWkSxChzv6bgTS3YqBkGuHcis+ouMFI2696n2t+XYIeFw==", + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/globals/-/globals-28.1.0.tgz", + "integrity": "sha512-3m7sTg52OTQR6dPhsEQSxAvU+LOBbMivZBwOvKEZ+Rb+GyxVnXi9HKgOTYkx/S99T8yvh17U4tNNJPIEQmtwYw==", "dev": true, "dependencies": { - "@jest/environment": "^27.4.6", - "@jest/types": "^27.4.2", - "expect": "^27.4.6" + "@jest/environment": "^28.1.0", + "@jest/expect": "^28.1.0", + "@jest/types": "^28.1.0" }, "engines": { - "node": "^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0" + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/globals/node_modules/@jest/environment": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/environment/-/environment-28.1.0.tgz", + "integrity": "sha512-S44WGSxkRngzHslhV6RoAExekfF7Qhwa6R5+IYFa81mpcj0YgdBnRSmvHe3SNwOt64yXaE5GG8Y2xM28ii5ssA==", + "dev": true, + "dependencies": { + "@jest/fake-timers": "^28.1.0", + "@jest/types": "^28.1.0", + "@types/node": "*", + "jest-mock": "^28.1.0" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/globals/node_modules/@jest/fake-timers": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/fake-timers/-/fake-timers-28.1.0.tgz", + "integrity": "sha512-Xqsf/6VLeAAq78+GNPzI7FZQRf5cCHj1qgQxCjws9n8rKw8r1UYoeaALwBvyuzOkpU3c1I6emeMySPa96rxtIg==", + "dev": true, + "dependencies": { + "@jest/types": "^28.1.0", + "@sinonjs/fake-timers": "^9.1.1", + "@types/node": "*", + "jest-message-util": "^28.1.0", + "jest-mock": "^28.1.0", + "jest-util": "^28.1.0" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/globals/node_modules/@jest/types": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/types/-/types-28.1.0.tgz", + "integrity": "sha512-xmEggMPr317MIOjjDoZ4ejCSr9Lpbt/u34+dvc99t7DS8YirW5rwZEhzKPC2BMUFkUhI48qs6qLUSGw5FuL0GA==", + "dev": true, + "dependencies": { + "@jest/schemas": "^28.0.2", + "@types/istanbul-lib-coverage": "^2.0.0", + "@types/istanbul-reports": "^3.0.0", + "@types/node": "*", + "@types/yargs": "^17.0.8", + "chalk": "^4.0.0" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/globals/node_modules/@sinonjs/fake-timers": { + "version": "9.1.2", + "resolved": "https://registry.npmjs.org/@sinonjs/fake-timers/-/fake-timers-9.1.2.tgz", + "integrity": "sha512-BPS4ynJW/o92PUR4wgriz2Ud5gpST5vz6GQfMixEDK0Z8ZCUv2M7SkBLykH56T++Xs+8ln9zTGbOvNGIe02/jw==", + "dev": true, + "dependencies": { + "@sinonjs/commons": "^1.7.0" + } + }, + "node_modules/@jest/globals/node_modules/@types/yargs": { + "version": "17.0.10", + "resolved": "https://registry.npmjs.org/@types/yargs/-/yargs-17.0.10.tgz", + "integrity": "sha512-gmEaFwpj/7f/ROdtIlci1R1VYU1J4j95m8T+Tj3iBgiBFKg1foE/PSl93bBd5T9LDXNPo8UlNN6W0qwD8O5OaA==", + "dev": true, + "dependencies": { + "@types/yargs-parser": "*" + } + }, + "node_modules/@jest/globals/node_modules/chalk": { + "version": "4.1.2", + "resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz", + "integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==", + "dev": true, + "dependencies": { + "ansi-styles": "^4.1.0", + "supports-color": "^7.1.0" + }, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/chalk/chalk?sponsor=1" + } + }, + "node_modules/@jest/globals/node_modules/jest-message-util": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-message-util/-/jest-message-util-28.1.0.tgz", + "integrity": "sha512-RpA8mpaJ/B2HphDMiDlrAZdDytkmwFqgjDZovM21F35lHGeUeCvYmm6W+sbQ0ydaLpg5bFAUuWG1cjqOl8vqrw==", + "dev": true, + "dependencies": { + "@babel/code-frame": "^7.12.13", + "@jest/types": "^28.1.0", + "@types/stack-utils": "^2.0.0", + "chalk": "^4.0.0", + "graceful-fs": "^4.2.9", + "micromatch": "^4.0.4", + "pretty-format": "^28.1.0", + "slash": "^3.0.0", + "stack-utils": "^2.0.3" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/globals/node_modules/jest-mock": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-mock/-/jest-mock-28.1.0.tgz", + "integrity": "sha512-H7BrhggNn77WhdL7O1apG0Q/iwl0Bdd5E1ydhCJzL3oBLh/UYxAwR3EJLsBZ9XA3ZU4PA3UNw4tQjduBTCTmLw==", + "dev": true, + "dependencies": { + "@jest/types": "^28.1.0", + "@types/node": "*" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/globals/node_modules/jest-util": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-util/-/jest-util-28.1.0.tgz", + "integrity": "sha512-qYdCKD77k4Hwkose2YBEqQk7PzUf/NSE+rutzceduFveQREeH6b+89Dc9+wjX9dAwHcgdx4yedGA3FQlU/qCTA==", + "dev": true, + "dependencies": { + "@jest/types": "^28.1.0", + "@types/node": "*", + "chalk": "^4.0.0", + "ci-info": "^3.2.0", + "graceful-fs": "^4.2.9", + "picomatch": "^2.2.3" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/globals/node_modules/pretty-format": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/pretty-format/-/pretty-format-28.1.0.tgz", + "integrity": "sha512-79Z4wWOYCdvQkEoEuSlBhHJqWeZ8D8YRPiPctJFCtvuaClGpiwiQYSCUOE6IEKUbbFukKOTFIUAXE8N4EQTo1Q==", + "dev": true, + "dependencies": { + "@jest/schemas": "^28.0.2", + "ansi-regex": "^5.0.1", + "ansi-styles": "^5.0.0", + "react-is": "^18.0.0" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, + "node_modules/@jest/globals/node_modules/pretty-format/node_modules/ansi-styles": { + "version": "5.2.0", + "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-5.2.0.tgz", + "integrity": "sha512-Cxwpt2SfTzTtXcfOlzGEee8O+c+MmUgGrNiBcXnuWxuFJHe6a5Hz7qwhwe5OgaSYI0IJvkLqWX1ASG+cJOkEiA==", + "dev": true, + "engines": { + "node": ">=10" + }, + "funding": { + "url": "https://github.com/chalk/ansi-styles?sponsor=1" + } + }, + "node_modules/@jest/globals/node_modules/react-is": { + "version": "18.1.0", + "resolved": "https://registry.npmjs.org/react-is/-/react-is-18.1.0.tgz", + "integrity": "sha512-Fl7FuabXsJnV5Q1qIOQwx/sagGF18kogb4gpfcG4gjLBWO0WDiiz1ko/ExayuxE7InyQkBLkxRFG5oxY6Uu3Kg==", + "dev": true + }, + "node_modules/@jest/globals/node_modules/slash": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/slash/-/slash-3.0.0.tgz", + "integrity": "sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==", + "dev": true, + "engines": { + "node": ">=8" } }, "node_modules/@jest/reporters": { @@ -2646,6 +3176,18 @@ "node": ">=0.10.0" } }, + "node_modules/@jest/schemas": { + "version": "28.0.2", + "resolved": "https://registry.npmjs.org/@jest/schemas/-/schemas-28.0.2.tgz", + "integrity": "sha512-YVDJZjd4izeTDkij00vHHAymNXQ6WWsdChFRK86qck6Jpr3DCL5W3Is3vslviRlP+bLuMYRLbdp98amMvqudhA==", + "dev": true, + "dependencies": { + "@sinclair/typebox": "^0.23.3" + }, + "engines": { + "node": "^12.13.0 || ^14.15.0 || ^16.10.0 || >=17.0.0" + } + }, "node_modules/@jest/source-map": { "version": "27.4.0", "resolved": "https://registry.npmjs.org/@jest/source-map/-/source-map-27.4.0.tgz", @@ -2760,9 +3302,9 @@ } }, "node_modules/@jest/types": { - "version": "27.4.2", - "resolved": "https://registry.npmjs.org/@jest/types/-/types-27.4.2.tgz", - "integrity": "sha512-j35yw0PMTPpZsUoOBiuHzr1zTYoad1cVIE0ajEjcrJONxxrko/IRGKkXx3os0Nsi4Hu3+5VmDbVfq5WhG/pWAg==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/@jest/types/-/types-27.5.1.tgz", + "integrity": "sha512-Cx46iJ9QpwQTjIdq5VJu2QTMMs3QlEjI0x1QbBP5W1+nMzyc2XmimiRR/CbX9TO0cPTeUlxWMOu8mslYsJ8DEw==", "devOptional": true, "dependencies": { "@types/istanbul-lib-coverage": "^2.0.0", @@ -3255,6 +3797,31 @@ "regenerator-runtime": "^0.13.3" } }, + "node_modules/@jridgewell/resolve-uri": { + "version": "3.0.7", + "resolved": "https://registry.npmjs.org/@jridgewell/resolve-uri/-/resolve-uri-3.0.7.tgz", + "integrity": "sha512-8cXDaBBHOr2pQ7j77Y6Vp5VDT2sIqWyWQ56TjEq4ih/a4iST3dItRe8Q9fp0rrIl9DoKhWQtUQz/YpOxLkXbNA==", + "dev": true, + "engines": { + "node": ">=6.0.0" + } + }, + "node_modules/@jridgewell/sourcemap-codec": { + "version": "1.4.13", + "resolved": "https://registry.npmjs.org/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.4.13.tgz", + "integrity": "sha512-GryiOJmNcWbovBxTfZSF71V/mXbgcV3MewDe3kIMCLyIh5e7SKAeUZs+rMnJ8jkMolZ/4/VsdBmMrw3l+VdZ3w==", + "dev": true + }, + "node_modules/@jridgewell/trace-mapping": { + "version": "0.3.11", + "resolved": "https://registry.npmjs.org/@jridgewell/trace-mapping/-/trace-mapping-0.3.11.tgz", + "integrity": "sha512-RllI476aSMsxzeI9TtlSMoNTgHDxEmnl6GkkHwhr0vdL8W+0WuesyI8Vd3rBOfrwtPXbPxdT9ADJdiOKgzxPQA==", + "dev": true, + "dependencies": { + "@jridgewell/resolve-uri": "^3.0.3", + "@jridgewell/sourcemap-codec": "^1.4.10" + } + }, "node_modules/@napi-rs/triples": { "version": "1.1.0", "resolved": "https://registry.npmjs.org/@napi-rs/triples/-/triples-1.1.0.tgz", @@ -3726,6 +4293,12 @@ "integrity": "sha512-RNiOoTPkptFtSVzQevY/yWtZwf/RxyVnPy/OcA9HBM3MlGDnBEYL5B41H0MTn0Uec8Hi+2qUtTfG2WWZBmMejQ==", "devOptional": true }, + "node_modules/@sinclair/typebox": { + "version": "0.23.5", + "resolved": "https://registry.npmjs.org/@sinclair/typebox/-/typebox-0.23.5.tgz", + "integrity": "sha512-AFBVi/iT4g20DHoujvMH1aEDn8fGJh4xsRGCP6d8RpLPMqsNPvW01Jcn0QysXTsg++/xj25NmJsGyH9xug/wKg==", + "dev": true + }, "node_modules/@sindresorhus/is": { "version": "4.6.0", "resolved": "https://registry.npmjs.org/@sindresorhus/is/-/is-4.6.0.tgz", @@ -4128,9 +4701,9 @@ } }, "node_modules/@types/react-syntax-highlighter": { - "version": "13.5.2", - "resolved": "https://registry.npmjs.org/@types/react-syntax-highlighter/-/react-syntax-highlighter-13.5.2.tgz", - "integrity": "sha512-sRZoKZBGKaE7CzMvTTgz+0x/aVR58ZYUTfB7HN76vC+yQnvo1FWtzNARBt0fGqcLGEVakEzMu/CtPzssmanu8Q==", + "version": "15.5.1", + "resolved": "https://registry.npmjs.org/@types/react-syntax-highlighter/-/react-syntax-highlighter-15.5.1.tgz", + "integrity": "sha512-+yD6D8y21JqLf89cRFEyRfptVMqo2ROHyAlysRvFwT28gT5gDo3KOiXHwGilHcq9y/OKTjlWK0f/hZUicrBFPQ==", "dev": true, "dependencies": { "@types/react": "*" @@ -4789,6 +5362,15 @@ "node": ">=8" } }, + "node_modules/async": { + "version": "2.6.4", + "resolved": "https://registry.npmjs.org/async/-/async-2.6.4.tgz", + "integrity": "sha512-mzo5dfJYwAn29PeiJ0zvwTo04zj8HDJj0Mn8TD7sno7q12prdbnasKJHhkm2c1LgrhlJ0teaea8860oxi51mGA==", + "optional": true, + "dependencies": { + "lodash": "^4.17.14" + } + }, "node_modules/async-limiter": { "version": "1.0.1", "resolved": "https://registry.npmjs.org/async-limiter/-/async-limiter-1.0.1.tgz", @@ -6241,6 +6823,16 @@ "resolved": "https://registry.npmjs.org/builtin-status-codes/-/builtin-status-codes-3.0.0.tgz", "integrity": "sha1-hZgoeOIbmOHGZCXgPQF0eI9Wnug=" }, + "node_modules/builtins": { + "version": "4.1.0", + "resolved": "https://registry.npmjs.org/builtins/-/builtins-4.1.0.tgz", + "integrity": "sha512-1bPRZQtmKaO6h7qV1YHXNtr6nCK28k0Zo95KM4dXfILcZZwoHJBN1m3lfLv9LPkcOZlrSr+J1bzMaZFO98Yq0w==", + "dev": true, + "peer": true, + "dependencies": { + "semver": "^7.0.0" + } + }, "node_modules/cacheable-lookup": { "version": "5.0.4", "resolved": "https://registry.npmjs.org/cacheable-lookup/-/cacheable-lookup-5.0.4.tgz", @@ -7558,9 +8150,9 @@ } }, "node_modules/diff-sequences": { - "version": "27.4.0", - "resolved": "https://registry.npmjs.org/diff-sequences/-/diff-sequences-27.4.0.tgz", - "integrity": "sha512-YqiQzkrsmHMH5uuh8OdQFU9/ZpADnwzml8z0O5HvRNda+5UZsaX/xN+AAxfR2hWq1Y7HZnAzO9J5lJXOuDz2Ww==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/diff-sequences/-/diff-sequences-27.5.1.tgz", + "integrity": "sha512-k1gCAXAsNgLwEL+Y8Wvl+M6oEFj5bgazfZULpS5CneoPPXRaCCW7dm+q21Ky2VEE5X+VeRDBVg1Pcvvsr4TtNQ==", "dev": true, "engines": { "node": "^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0" @@ -8240,9 +8832,9 @@ } }, "node_modules/eslint-config-standard": { - "version": "16.0.3", - "resolved": "https://registry.npmjs.org/eslint-config-standard/-/eslint-config-standard-16.0.3.tgz", - "integrity": "sha512-x4fmJL5hGqNJKGHSjnLdgA6U6h1YW/G2dW9fA+cyVur4SK6lyue8+UgNKWlZtUDTXvgKDD/Oa3GQjmB5kjtVvg==", + "version": "17.0.0", + "resolved": "https://registry.npmjs.org/eslint-config-standard/-/eslint-config-standard-17.0.0.tgz", + "integrity": "sha512-/2ks1GKyqSOkH7JFvXJicu0iMpoojkwB+f5Du/1SC0PtBL+s8v30k9njRZ21pm2drKYm2342jFnGWzttxPmZVg==", "dev": true, "funding": [ { @@ -8259,10 +8851,10 @@ } ], "peerDependencies": { - "eslint": "^7.12.1", - "eslint-plugin-import": "^2.22.1", - "eslint-plugin-node": "^11.1.0", - "eslint-plugin-promise": "^4.2.1 || ^5.0.0" + "eslint": "^8.0.1", + "eslint-plugin-import": "^2.25.2", + "eslint-plugin-n": "^15.0.0", + "eslint-plugin-promise": "^6.0.0" } }, "node_modules/eslint-import-resolver-node": { @@ -8306,6 +8898,26 @@ "ms": "^2.1.1" } }, + "node_modules/eslint-plugin-es": { + "version": "4.1.0", + "resolved": "https://registry.npmjs.org/eslint-plugin-es/-/eslint-plugin-es-4.1.0.tgz", + "integrity": "sha512-GILhQTnjYE2WorX5Jyi5i4dz5ALWxBIdQECVQavL6s7cI76IZTDWleTHkxz/QT3kvcs2QlGHvKLYsSlPOlPXnQ==", + "dev": true, + "peer": true, + "dependencies": { + "eslint-utils": "^2.0.0", + "regexpp": "^3.0.0" + }, + "engines": { + "node": ">=8.10.0" + }, + "funding": { + "url": "https://github.com/sponsors/mysticatea" + }, + "peerDependencies": { + "eslint": ">=4.19.1" + } + }, "node_modules/eslint-plugin-import": { "version": "2.25.4", "resolved": "https://registry.npmjs.org/eslint-plugin-import/-/eslint-plugin-import-2.25.4.tgz", @@ -8430,6 +9042,85 @@ "node": "*" } }, + "node_modules/eslint-plugin-n": { + "version": "15.2.0", + "resolved": "https://registry.npmjs.org/eslint-plugin-n/-/eslint-plugin-n-15.2.0.tgz", + "integrity": "sha512-lWLg++jGwC88GDGGBX3CMkk0GIWq0y41aH51lavWApOKcMQcYoL3Ayd0lEdtD3SnQtR+3qBvWQS3qGbR2BxRWg==", + "dev": true, + "peer": true, + "dependencies": { + "builtins": "^4.0.0", + "eslint-plugin-es": "^4.1.0", + "eslint-utils": "^3.0.0", + "ignore": "^5.1.1", + "is-core-module": "^2.3.0", + "minimatch": "^3.0.4", + "resolve": "^1.10.1", + "semver": "^6.3.0" + }, + "engines": { + "node": ">=12.22.0" + }, + "funding": { + "url": "https://github.com/sponsors/mysticatea" + }, + "peerDependencies": { + "eslint": ">=7.0.0" + } + }, + "node_modules/eslint-plugin-n/node_modules/brace-expansion": { + "version": "1.1.11", + "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz", + "integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==", + "dev": true, + "peer": true, + "dependencies": { + "balanced-match": "^1.0.0", + "concat-map": "0.0.1" + } + }, + "node_modules/eslint-plugin-n/node_modules/eslint-utils": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/eslint-utils/-/eslint-utils-3.0.0.tgz", + "integrity": "sha512-uuQC43IGctw68pJA1RgbQS8/NP7rch6Cwd4j3ZBtgo4/8Flj4eGE7ZYSZRN3iq5pVUv6GPdW5Z1RFleo84uLDA==", + "dev": true, + "peer": true, + "dependencies": { + "eslint-visitor-keys": "^2.0.0" + }, + "engines": { + "node": "^10.0.0 || ^12.0.0 || >= 14.0.0" + }, + "funding": { + "url": "https://github.com/sponsors/mysticatea" + }, + "peerDependencies": { + "eslint": ">=5" + } + }, + "node_modules/eslint-plugin-n/node_modules/minimatch": { + "version": "3.1.2", + "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz", + "integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==", + "dev": true, + "peer": true, + "dependencies": { + "brace-expansion": "^1.1.7" + }, + "engines": { + "node": "*" + } + }, + "node_modules/eslint-plugin-n/node_modules/semver": { + "version": "6.3.0", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", + "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "dev": true, + "peer": true, + "bin": { + "semver": "bin/semver.js" + } + }, "node_modules/eslint-plugin-node": { "version": "11.1.0", "resolved": "https://registry.npmjs.org/eslint-plugin-node/-/eslint-plugin-node-11.1.0.tgz", @@ -8968,15 +9659,15 @@ } }, "node_modules/expect": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/expect/-/expect-27.4.6.tgz", - "integrity": "sha512-1M/0kAALIaj5LaG66sFJTbRsWTADnylly82cu4bspI0nl+pgP4E6Bh/aqdHlTUjul06K7xQnnrAoqfxVU0+/ag==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/expect/-/expect-27.5.1.tgz", + "integrity": "sha512-E1q5hSUG2AmYQwQJ041nvgpkODHQvB+RKlB4IYdru6uJsyFTRyZAP463M+1lINorwbqAmUggi6+WwkD8lCS/Dw==", "dev": true, "dependencies": { - "@jest/types": "^27.4.2", - "jest-get-type": "^27.4.0", - "jest-matcher-utils": "^27.4.6", - "jest-message-util": "^27.4.6" + "@jest/types": "^27.5.1", + "jest-get-type": "^27.5.1", + "jest-matcher-utils": "^27.5.1", + "jest-message-util": "^27.5.1" }, "engines": { "node": "^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0" @@ -9558,6 +10249,19 @@ "integrity": "sha1-FQStJSMVjKpA20onh8sBQRmU6k8=", "devOptional": true }, + "node_modules/fsevents": { + "version": "2.3.2", + "resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.2.tgz", + "integrity": "sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT7jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt812P9ab+DDKA==", + "hasInstallScript": true, + "optional": true, + "os": [ + "darwin" + ], + "engines": { + "node": "^8.16.0 || ^10.6.0 || >=11.0.0" + } + }, "node_modules/function-bind": { "version": "1.1.1", "resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.1.tgz", @@ -10009,9 +10713,9 @@ } }, "node_modules/graceful-fs": { - "version": "4.2.8", - "resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.8.tgz", - "integrity": "sha512-qkIilPUYcNhJpd33n0GBXTB1MMPp14TxEsEs0pTrsSVucApsYzW5V+Q8Qxhik6KU3evy+qkAAowTByymK0avdg==" + "version": "4.2.10", + "resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.10.tgz", + "integrity": "sha512-9ByhssR2fPVsNZj478qUUbKfmL0+t5BDVyjShtyZZLiK7ZDAArFFfopyOTj0M05wE2tJPisA4iTnnXl2YoPvOA==" }, "node_modules/graphql": { "version": "16.3.0", @@ -11819,15 +12523,15 @@ } }, "node_modules/jest-diff": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/jest-diff/-/jest-diff-27.4.6.tgz", - "integrity": "sha512-zjaB0sh0Lb13VyPsd92V7HkqF6yKRH9vm33rwBt7rPYrpQvS1nCvlIy2pICbKta+ZjWngYLNn4cCK4nyZkjS/w==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/jest-diff/-/jest-diff-27.5.1.tgz", + "integrity": "sha512-m0NvkX55LDt9T4mctTEgnZk3fmEg3NRYutvMPWM/0iPnkFj2wIeF45O1718cMSOFO1vINkqmxqD8vE37uTEbqw==", "dev": true, "dependencies": { "chalk": "^4.0.0", - "diff-sequences": "^27.4.0", - "jest-get-type": "^27.4.0", - "pretty-format": "^27.4.6" + "diff-sequences": "^27.5.1", + "jest-get-type": "^27.5.1", + "pretty-format": "^27.5.1" }, "engines": { "node": "^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0" @@ -11983,9 +12687,9 @@ } }, "node_modules/jest-get-type": { - "version": "27.4.0", - "resolved": "https://registry.npmjs.org/jest-get-type/-/jest-get-type-27.4.0.tgz", - "integrity": "sha512-tk9o+ld5TWq41DkK14L4wox4s2D9MtTpKaAVzXfr5CUKm5ZK2ExcaFE0qls2W71zE/6R2TxxrK9w2r6svAFDBQ==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/jest-get-type/-/jest-get-type-27.5.1.tgz", + "integrity": "sha512-2KY95ksYSaK7DMBWQn6dQz3kqAf3BB64y2udeG+hv4KfSOb9qwcYQstTJc1KCbsix+wLZWZYN8t7nwX3GOBLRw==", "dev": true, "engines": { "node": "^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0" @@ -12084,15 +12788,15 @@ } }, "node_modules/jest-matcher-utils": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/jest-matcher-utils/-/jest-matcher-utils-27.4.6.tgz", - "integrity": "sha512-XD4PKT3Wn1LQnRAq7ZsTI0VRuEc9OrCPFiO1XL7bftTGmfNF0DcEwMHRgqiu7NGf8ZoZDREpGrCniDkjt79WbA==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/jest-matcher-utils/-/jest-matcher-utils-27.5.1.tgz", + "integrity": "sha512-z2uTx/T6LBaCoNWNFWwChLBKYxTMcGBRjAt+2SbP929/Fflb9aa5LGma654Rz8z9HLxsrUaYzxE9T/EFIL/PAw==", "dev": true, "dependencies": { "chalk": "^4.0.0", - "jest-diff": "^27.4.6", - "jest-get-type": "^27.4.0", - "pretty-format": "^27.4.6" + "jest-diff": "^27.5.1", + "jest-get-type": "^27.5.1", + "pretty-format": "^27.5.1" }, "engines": { "node": "^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0" @@ -12115,18 +12819,18 @@ } }, "node_modules/jest-message-util": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/jest-message-util/-/jest-message-util-27.4.6.tgz", - "integrity": "sha512-0p5szriFU0U74czRSFjH6RyS7UYIAkn/ntwMuOwTGWrQIOh5NzXXrq72LOqIkJKKvFbPq+byZKuBz78fjBERBA==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/jest-message-util/-/jest-message-util-27.5.1.tgz", + "integrity": "sha512-rMyFe1+jnyAAf+NHwTclDz0eAaLkVDdKVHHBFWsBWHnnh5YeJMNWWsv7AbFYXfK3oTqvL7VTWkhNLu1jX24D+g==", "devOptional": true, "dependencies": { "@babel/code-frame": "^7.12.13", - "@jest/types": "^27.4.2", + "@jest/types": "^27.5.1", "@types/stack-utils": "^2.0.0", "chalk": "^4.0.0", - "graceful-fs": "^4.2.4", + "graceful-fs": "^4.2.9", "micromatch": "^4.0.4", - "pretty-format": "^27.4.6", + "pretty-format": "^27.5.1", "slash": "^3.0.0", "stack-utils": "^2.0.3" }, @@ -12160,12 +12864,12 @@ } }, "node_modules/jest-mock": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/jest-mock/-/jest-mock-27.4.6.tgz", - "integrity": "sha512-kvojdYRkst8iVSZ1EJ+vc1RRD9llueBjKzXzeCytH3dMM7zvPV/ULcfI2nr0v0VUgm3Bjt3hBCQvOeaBz+ZTHw==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/jest-mock/-/jest-mock-27.5.1.tgz", + "integrity": "sha512-K4jKbY1d4ENhbrG2zuPWaQBvDly+iZ2yAW+T1fATN78hc0sInwn7wZB8XtlNnvHug5RMwV897Xm4LqmPM4e2Og==", "devOptional": true, "dependencies": { - "@jest/types": "^27.4.2", + "@jest/types": "^27.5.1", "@types/node": "*" }, "engines": { @@ -12353,6 +13057,20 @@ "node": "^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0" } }, + "node_modules/jest-runtime/node_modules/@jest/globals": { + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/@jest/globals/-/globals-27.5.1.tgz", + "integrity": "sha512-ZEJNB41OBQQgGzgyInAv0UUfDDj3upmHydjieSxFvTRuZElrx7tXg/uVQ5hYVEwiXs3+aMsAeEc9X7xiSKCm4Q==", + "dev": true, + "dependencies": { + "@jest/environment": "^27.5.1", + "@jest/types": "^27.5.1", + "expect": "^27.5.1" + }, + "engines": { + "node": "^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0" + } + }, "node_modules/jest-runtime/node_modules/brace-expansion": { "version": "1.1.11", "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz", @@ -12489,16 +13207,16 @@ } }, "node_modules/jest-util": { - "version": "27.4.2", - "resolved": "https://registry.npmjs.org/jest-util/-/jest-util-27.4.2.tgz", - "integrity": "sha512-YuxxpXU6nlMan9qyLuxHaMMOzXAl5aGZWCSzben5DhLHemYQxCc4YK+4L3ZrCutT8GPQ+ui9k5D8rUJoDioMnA==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/jest-util/-/jest-util-27.5.1.tgz", + "integrity": "sha512-Kv2o/8jNvX1MQ0KGtw480E/w4fBCDOnH6+6DmeKi6LZUIlKA5kwY0YNdlzaWTiVgxqAqik11QyxDOKk543aKXw==", "devOptional": true, "dependencies": { - "@jest/types": "^27.4.2", + "@jest/types": "^27.5.1", "@types/node": "*", "chalk": "^4.0.0", "ci-info": "^3.2.0", - "graceful-fs": "^4.2.4", + "graceful-fs": "^4.2.9", "picomatch": "^2.2.3" }, "engines": { @@ -12848,9 +13566,9 @@ } }, "node_modules/kill-port": { - "version": "1.6.1", - "resolved": "https://registry.npmjs.org/kill-port/-/kill-port-1.6.1.tgz", - "integrity": "sha512-un0Y55cOM7JKGaLnGja28T38tDDop0AQ8N0KlAdyh+B1nmMoX8AnNmqPNZbS3mUMgiST51DCVqmbFT1gNJpVNw==", + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/kill-port/-/kill-port-2.0.0.tgz", + "integrity": "sha512-TWGAJ/SGy52aKhYpPSCw4S/WR0rTYkC2+6oRp5xBlLo4UvJe3Gt0MwROO8hI+Hu4YkTDhe27EPKKeFUtqNNfdA==", "dev": true, "dependencies": { "get-them-args": "1.3.2", @@ -15356,9 +16074,9 @@ } }, "node_modules/nodemon": { - "version": "2.0.15", - "resolved": "https://registry.npmjs.org/nodemon/-/nodemon-2.0.15.tgz", - "integrity": "sha512-gdHMNx47Gw7b3kWxJV64NI+Q5nfl0y5DgDbiVtShiwa7Z0IZ07Ll4RLFo6AjrhzMtoEZn5PDE3/c2AbVsiCkpA==", + "version": "2.0.16", + "resolved": "https://registry.npmjs.org/nodemon/-/nodemon-2.0.16.tgz", + "integrity": "sha512-zsrcaOfTWRuUzBn3P44RDliLlp263Z/76FPoHFr3cFFkOz0lTPAcIw8dCzfdVIx/t3AtDYCZRCDkoCojJqaG3w==", "dev": true, "hasInstallScript": true, "dependencies": { @@ -15978,15 +16696,6 @@ "node": ">=0.10.0" } }, - "node_modules/pa11y-ci/node_modules/async": { - "version": "2.6.3", - "resolved": "https://registry.npmjs.org/async/-/async-2.6.3.tgz", - "integrity": "sha512-zflvls11DCy+dQWzTW2dzuilv8Z5X/pjfmZOWba6TNIVDm+2UDaJmXSOXlasHKfNBs8oo3M0aT50fDEWfKZjXg==", - "optional": true, - "dependencies": { - "lodash": "^4.17.14" - } - }, "node_modules/pa11y-ci/node_modules/brace-expansion": { "version": "1.1.11", "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz", @@ -17200,9 +17909,9 @@ } }, "node_modules/pretty-format": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/pretty-format/-/pretty-format-27.4.6.tgz", - "integrity": "sha512-NblstegA1y/RJW2VyML+3LlpFjzx62cUrtBIKIWDXEDkjNeleA7Od7nrzcs/VLQvAeV4CgSYhrN39DRN88Qi/g==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/pretty-format/-/pretty-format-27.5.1.tgz", + "integrity": "sha512-Qb1gy5OrP5+zDf2Bvnzdl3jsTf1qXVMazbvCoKhtKqVs4/YK4ozX4gKQJJVyNe+cajNPn0KoC0MC3FUmaHWEmQ==", "devOptional": true, "dependencies": { "ansi-regex": "^5.0.1", @@ -23837,40 +24546,469 @@ } }, "@jest/environment": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/@jest/environment/-/environment-27.4.6.tgz", - "integrity": "sha512-E6t+RXPfATEEGVidr84WngLNWZ8ffCPky8RqqRK6u1Bn0LK92INe0MDttyPl/JOzaq92BmDzOeuqk09TvM22Sg==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/@jest/environment/-/environment-27.5.1.tgz", + "integrity": "sha512-/WQjhPJe3/ghaol/4Bq480JKXV/Rfw8nQdN7f41fM8VDHLcxKXou6QyXAh3EFr9/bVG3x74z1NWDkP87EiY8gA==", "devOptional": true, "requires": { - "@jest/fake-timers": "^27.4.6", - "@jest/types": "^27.4.2", + "@jest/fake-timers": "^27.5.1", + "@jest/types": "^27.5.1", "@types/node": "*", - "jest-mock": "^27.4.6" + "jest-mock": "^27.5.1" + } + }, + "@jest/expect": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/expect/-/expect-28.1.0.tgz", + "integrity": "sha512-be9ETznPLaHOmeJqzYNIXv1ADEzENuQonIoobzThOYPuK/6GhrWNIJDVTgBLCrz3Am73PyEU2urQClZp0hLTtA==", + "dev": true, + "requires": { + "expect": "^28.1.0", + "jest-snapshot": "^28.1.0" + }, + "dependencies": { + "@jest/transform": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/transform/-/transform-28.1.0.tgz", + "integrity": "sha512-omy2xe5WxlAfqmsTjTPxw+iXRTRnf+NtX0ToG+4S0tABeb4KsKmPUHq5UBuwunHg3tJRwgEQhEp0M/8oiatLEA==", + "dev": true, + "requires": { + "@babel/core": "^7.11.6", + "@jest/types": "^28.1.0", + "@jridgewell/trace-mapping": "^0.3.7", + "babel-plugin-istanbul": "^6.1.1", + "chalk": "^4.0.0", + "convert-source-map": "^1.4.0", + "fast-json-stable-stringify": "^2.0.0", + "graceful-fs": "^4.2.9", + "jest-haste-map": "^28.1.0", + "jest-regex-util": "^28.0.2", + "jest-util": "^28.1.0", + "micromatch": "^4.0.4", + "pirates": "^4.0.4", + "slash": "^3.0.0", + "write-file-atomic": "^4.0.1" + } + }, + "@jest/types": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/types/-/types-28.1.0.tgz", + "integrity": "sha512-xmEggMPr317MIOjjDoZ4ejCSr9Lpbt/u34+dvc99t7DS8YirW5rwZEhzKPC2BMUFkUhI48qs6qLUSGw5FuL0GA==", + "dev": true, + "requires": { + "@jest/schemas": "^28.0.2", + "@types/istanbul-lib-coverage": "^2.0.0", + "@types/istanbul-reports": "^3.0.0", + "@types/node": "*", + "@types/yargs": "^17.0.8", + "chalk": "^4.0.0" + } + }, + "@types/yargs": { + "version": "17.0.10", + "resolved": "https://registry.npmjs.org/@types/yargs/-/yargs-17.0.10.tgz", + "integrity": "sha512-gmEaFwpj/7f/ROdtIlci1R1VYU1J4j95m8T+Tj3iBgiBFKg1foE/PSl93bBd5T9LDXNPo8UlNN6W0qwD8O5OaA==", + "dev": true, + "requires": { + "@types/yargs-parser": "*" + } + }, + "chalk": { + "version": "4.1.2", + "resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz", + "integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==", + "dev": true, + "requires": { + "ansi-styles": "^4.1.0", + "supports-color": "^7.1.0" + } + }, + "diff-sequences": { + "version": "28.0.2", + "resolved": "https://registry.npmjs.org/diff-sequences/-/diff-sequences-28.0.2.tgz", + "integrity": "sha512-YtEoNynLDFCRznv/XDalsKGSZDoj0U5kLnXvY0JSq3nBboRrZXjD81+eSiwi+nzcZDwedMmcowcxNwwgFW23mQ==", + "dev": true + }, + "expect": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/expect/-/expect-28.1.0.tgz", + "integrity": "sha512-qFXKl8Pmxk8TBGfaFKRtcQjfXEnKAs+dmlxdwvukJZorwrAabT7M3h8oLOG01I2utEhkmUTi17CHaPBovZsKdw==", + "dev": true, + "requires": { + "@jest/expect-utils": "^28.1.0", + "jest-get-type": "^28.0.2", + "jest-matcher-utils": "^28.1.0", + "jest-message-util": "^28.1.0", + "jest-util": "^28.1.0" + } + }, + "jest-diff": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-diff/-/jest-diff-28.1.0.tgz", + "integrity": "sha512-8eFd3U3OkIKRtlasXfiAQfbovgFgRDb0Ngcs2E+FMeBZ4rUezqIaGjuyggJBp+llosQXNEWofk/Sz4Hr5gMUhA==", + "dev": true, + "requires": { + "chalk": "^4.0.0", + "diff-sequences": "^28.0.2", + "jest-get-type": "^28.0.2", + "pretty-format": "^28.1.0" + } + }, + "jest-get-type": { + "version": "28.0.2", + "resolved": "https://registry.npmjs.org/jest-get-type/-/jest-get-type-28.0.2.tgz", + "integrity": "sha512-ioj2w9/DxSYHfOm5lJKCdcAmPJzQXmbM/Url3rhlghrPvT3tt+7a/+oXc9azkKmLvoiXjtV83bEWqi+vs5nlPA==", + "dev": true + }, + "jest-haste-map": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-haste-map/-/jest-haste-map-28.1.0.tgz", + "integrity": "sha512-xyZ9sXV8PtKi6NCrJlmq53PyNVHzxmcfXNVvIRHpHmh1j/HChC4pwKgyjj7Z9us19JMw8PpQTJsFWOsIfT93Dw==", + "dev": true, + "requires": { + "@jest/types": "^28.1.0", + "@types/graceful-fs": "^4.1.3", + "@types/node": "*", + "anymatch": "^3.0.3", + "fb-watchman": "^2.0.0", + "fsevents": "^2.3.2", + "graceful-fs": "^4.2.9", + "jest-regex-util": "^28.0.2", + "jest-util": "^28.1.0", + "jest-worker": "^28.1.0", + "micromatch": "^4.0.4", + "walker": "^1.0.7" + } + }, + "jest-matcher-utils": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-matcher-utils/-/jest-matcher-utils-28.1.0.tgz", + "integrity": "sha512-onnax0n2uTLRQFKAjC7TuaxibrPSvZgKTcSCnNUz/tOjJ9UhxNm7ZmPpoQavmTDUjXvUQ8KesWk2/VdrxIFzTQ==", + "dev": true, + "requires": { + "chalk": "^4.0.0", + "jest-diff": "^28.1.0", + "jest-get-type": "^28.0.2", + "pretty-format": "^28.1.0" + } + }, + "jest-message-util": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-message-util/-/jest-message-util-28.1.0.tgz", + "integrity": "sha512-RpA8mpaJ/B2HphDMiDlrAZdDytkmwFqgjDZovM21F35lHGeUeCvYmm6W+sbQ0ydaLpg5bFAUuWG1cjqOl8vqrw==", + "dev": true, + "requires": { + "@babel/code-frame": "^7.12.13", + "@jest/types": "^28.1.0", + "@types/stack-utils": "^2.0.0", + "chalk": "^4.0.0", + "graceful-fs": "^4.2.9", + "micromatch": "^4.0.4", + "pretty-format": "^28.1.0", + "slash": "^3.0.0", + "stack-utils": "^2.0.3" + } + }, + "jest-regex-util": { + "version": "28.0.2", + "resolved": "https://registry.npmjs.org/jest-regex-util/-/jest-regex-util-28.0.2.tgz", + "integrity": "sha512-4s0IgyNIy0y9FK+cjoVYoxamT7Zeo7MhzqRGx7YDYmaQn1wucY9rotiGkBzzcMXTtjrCAP/f7f+E0F7+fxPNdw==", + "dev": true + }, + "jest-snapshot": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-snapshot/-/jest-snapshot-28.1.0.tgz", + "integrity": "sha512-ex49M2ZrZsUyQLpLGxQtDbahvgBjlLPgklkqGM0hq/F7W/f8DyqZxVHjdy19QKBm4O93eDp+H5S23EiTbbUmHw==", + "dev": true, + "requires": { + "@babel/core": "^7.11.6", + "@babel/generator": "^7.7.2", + "@babel/plugin-syntax-typescript": "^7.7.2", + "@babel/traverse": "^7.7.2", + "@babel/types": "^7.3.3", + "@jest/expect-utils": "^28.1.0", + "@jest/transform": "^28.1.0", + "@jest/types": "^28.1.0", + "@types/babel__traverse": "^7.0.6", + "@types/prettier": "^2.1.5", + "babel-preset-current-node-syntax": "^1.0.0", + "chalk": "^4.0.0", + "expect": "^28.1.0", + "graceful-fs": "^4.2.9", + "jest-diff": "^28.1.0", + "jest-get-type": "^28.0.2", + "jest-haste-map": "^28.1.0", + "jest-matcher-utils": "^28.1.0", + "jest-message-util": "^28.1.0", + "jest-util": "^28.1.0", + "natural-compare": "^1.4.0", + "pretty-format": "^28.1.0", + "semver": "^7.3.5" + } + }, + "jest-util": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-util/-/jest-util-28.1.0.tgz", + "integrity": "sha512-qYdCKD77k4Hwkose2YBEqQk7PzUf/NSE+rutzceduFveQREeH6b+89Dc9+wjX9dAwHcgdx4yedGA3FQlU/qCTA==", + "dev": true, + "requires": { + "@jest/types": "^28.1.0", + "@types/node": "*", + "chalk": "^4.0.0", + "ci-info": "^3.2.0", + "graceful-fs": "^4.2.9", + "picomatch": "^2.2.3" + } + }, + "jest-worker": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-worker/-/jest-worker-28.1.0.tgz", + "integrity": "sha512-ZHwM6mNwaWBR52Snff8ZvsCTqQsvhCxP/bT1I6T6DAnb6ygkshsyLQIMxFwHpYxht0HOoqt23JlC01viI7T03A==", + "dev": true, + "requires": { + "@types/node": "*", + "merge-stream": "^2.0.0", + "supports-color": "^8.0.0" + }, + "dependencies": { + "supports-color": { + "version": "8.1.1", + "resolved": "https://registry.npmjs.org/supports-color/-/supports-color-8.1.1.tgz", + "integrity": "sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==", + "dev": true, + "requires": { + "has-flag": "^4.0.0" + } + } + } + }, + "pretty-format": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/pretty-format/-/pretty-format-28.1.0.tgz", + "integrity": "sha512-79Z4wWOYCdvQkEoEuSlBhHJqWeZ8D8YRPiPctJFCtvuaClGpiwiQYSCUOE6IEKUbbFukKOTFIUAXE8N4EQTo1Q==", + "dev": true, + "requires": { + "@jest/schemas": "^28.0.2", + "ansi-regex": "^5.0.1", + "ansi-styles": "^5.0.0", + "react-is": "^18.0.0" + }, + "dependencies": { + "ansi-styles": { + "version": "5.2.0", + "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-5.2.0.tgz", + "integrity": "sha512-Cxwpt2SfTzTtXcfOlzGEee8O+c+MmUgGrNiBcXnuWxuFJHe6a5Hz7qwhwe5OgaSYI0IJvkLqWX1ASG+cJOkEiA==", + "dev": true + } + } + }, + "react-is": { + "version": "18.1.0", + "resolved": "https://registry.npmjs.org/react-is/-/react-is-18.1.0.tgz", + "integrity": "sha512-Fl7FuabXsJnV5Q1qIOQwx/sagGF18kogb4gpfcG4gjLBWO0WDiiz1ko/ExayuxE7InyQkBLkxRFG5oxY6Uu3Kg==", + "dev": true + }, + "slash": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/slash/-/slash-3.0.0.tgz", + "integrity": "sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==", + "dev": true + }, + "write-file-atomic": { + "version": "4.0.1", + "resolved": "https://registry.npmjs.org/write-file-atomic/-/write-file-atomic-4.0.1.tgz", + "integrity": "sha512-nSKUxgAbyioruk6hU87QzVbY279oYT6uiwgDoujth2ju4mJ+TZau7SQBhtbTmUyuNYTuXnSyRn66FV0+eCgcrQ==", + "dev": true, + "requires": { + "imurmurhash": "^0.1.4", + "signal-exit": "^3.0.7" + } + } + } + }, + "@jest/expect-utils": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/expect-utils/-/expect-utils-28.1.0.tgz", + "integrity": "sha512-5BrG48dpC0sB80wpeIX5FU6kolDJI4K0n5BM9a5V38MGx0pyRvUBSS0u2aNTdDzmOrCjhOg8pGs6a20ivYkdmw==", + "dev": true, + "requires": { + "jest-get-type": "^28.0.2" + }, + "dependencies": { + "jest-get-type": { + "version": "28.0.2", + "resolved": "https://registry.npmjs.org/jest-get-type/-/jest-get-type-28.0.2.tgz", + "integrity": "sha512-ioj2w9/DxSYHfOm5lJKCdcAmPJzQXmbM/Url3rhlghrPvT3tt+7a/+oXc9azkKmLvoiXjtV83bEWqi+vs5nlPA==", + "dev": true + } } }, "@jest/fake-timers": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/@jest/fake-timers/-/fake-timers-27.4.6.tgz", - "integrity": "sha512-mfaethuYF8scV8ntPpiVGIHQgS0XIALbpY2jt2l7wb/bvq4Q5pDLk4EP4D7SAvYT1QrPOPVZAtbdGAOOyIgs7A==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/@jest/fake-timers/-/fake-timers-27.5.1.tgz", + "integrity": "sha512-/aPowoolwa07k7/oM3aASneNeBGCmGQsc3ugN4u6s4C/+s5M64MFo/+djTdiwcbQlRfFElGuDXWzaWj6QgKObQ==", "devOptional": true, "requires": { - "@jest/types": "^27.4.2", + "@jest/types": "^27.5.1", "@sinonjs/fake-timers": "^8.0.1", "@types/node": "*", - "jest-message-util": "^27.4.6", - "jest-mock": "^27.4.6", - "jest-util": "^27.4.2" + "jest-message-util": "^27.5.1", + "jest-mock": "^27.5.1", + "jest-util": "^27.5.1" } }, "@jest/globals": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/@jest/globals/-/globals-27.4.6.tgz", - "integrity": "sha512-kAiwMGZ7UxrgPzu8Yv9uvWmXXxsy0GciNejlHvfPIfWkSxChzv6bgTS3YqBkGuHcis+ouMFI2696n2t+XYIeFw==", + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/globals/-/globals-28.1.0.tgz", + "integrity": "sha512-3m7sTg52OTQR6dPhsEQSxAvU+LOBbMivZBwOvKEZ+Rb+GyxVnXi9HKgOTYkx/S99T8yvh17U4tNNJPIEQmtwYw==", "dev": true, "requires": { - "@jest/environment": "^27.4.6", - "@jest/types": "^27.4.2", - "expect": "^27.4.6" + "@jest/environment": "^28.1.0", + "@jest/expect": "^28.1.0", + "@jest/types": "^28.1.0" + }, + "dependencies": { + "@jest/environment": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/environment/-/environment-28.1.0.tgz", + "integrity": "sha512-S44WGSxkRngzHslhV6RoAExekfF7Qhwa6R5+IYFa81mpcj0YgdBnRSmvHe3SNwOt64yXaE5GG8Y2xM28ii5ssA==", + "dev": true, + "requires": { + "@jest/fake-timers": "^28.1.0", + "@jest/types": "^28.1.0", + "@types/node": "*", + "jest-mock": "^28.1.0" + } + }, + "@jest/fake-timers": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/fake-timers/-/fake-timers-28.1.0.tgz", + "integrity": "sha512-Xqsf/6VLeAAq78+GNPzI7FZQRf5cCHj1qgQxCjws9n8rKw8r1UYoeaALwBvyuzOkpU3c1I6emeMySPa96rxtIg==", + "dev": true, + "requires": { + "@jest/types": "^28.1.0", + "@sinonjs/fake-timers": "^9.1.1", + "@types/node": "*", + "jest-message-util": "^28.1.0", + "jest-mock": "^28.1.0", + "jest-util": "^28.1.0" + } + }, + "@jest/types": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/@jest/types/-/types-28.1.0.tgz", + "integrity": "sha512-xmEggMPr317MIOjjDoZ4ejCSr9Lpbt/u34+dvc99t7DS8YirW5rwZEhzKPC2BMUFkUhI48qs6qLUSGw5FuL0GA==", + "dev": true, + "requires": { + "@jest/schemas": "^28.0.2", + "@types/istanbul-lib-coverage": "^2.0.0", + "@types/istanbul-reports": "^3.0.0", + "@types/node": "*", + "@types/yargs": "^17.0.8", + "chalk": "^4.0.0" + } + }, + "@sinonjs/fake-timers": { + "version": "9.1.2", + "resolved": "https://registry.npmjs.org/@sinonjs/fake-timers/-/fake-timers-9.1.2.tgz", + "integrity": "sha512-BPS4ynJW/o92PUR4wgriz2Ud5gpST5vz6GQfMixEDK0Z8ZCUv2M7SkBLykH56T++Xs+8ln9zTGbOvNGIe02/jw==", + "dev": true, + "requires": { + "@sinonjs/commons": "^1.7.0" + } + }, + "@types/yargs": { + "version": "17.0.10", + "resolved": "https://registry.npmjs.org/@types/yargs/-/yargs-17.0.10.tgz", + "integrity": "sha512-gmEaFwpj/7f/ROdtIlci1R1VYU1J4j95m8T+Tj3iBgiBFKg1foE/PSl93bBd5T9LDXNPo8UlNN6W0qwD8O5OaA==", + "dev": true, + "requires": { + "@types/yargs-parser": "*" + } + }, + "chalk": { + "version": "4.1.2", + "resolved": "https://registry.npmjs.org/chalk/-/chalk-4.1.2.tgz", + "integrity": "sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==", + "dev": true, + "requires": { + "ansi-styles": "^4.1.0", + "supports-color": "^7.1.0" + } + }, + "jest-message-util": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-message-util/-/jest-message-util-28.1.0.tgz", + "integrity": "sha512-RpA8mpaJ/B2HphDMiDlrAZdDytkmwFqgjDZovM21F35lHGeUeCvYmm6W+sbQ0ydaLpg5bFAUuWG1cjqOl8vqrw==", + "dev": true, + "requires": { + "@babel/code-frame": "^7.12.13", + "@jest/types": "^28.1.0", + "@types/stack-utils": "^2.0.0", + "chalk": "^4.0.0", + "graceful-fs": "^4.2.9", + "micromatch": "^4.0.4", + "pretty-format": "^28.1.0", + "slash": "^3.0.0", + "stack-utils": "^2.0.3" + } + }, + "jest-mock": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-mock/-/jest-mock-28.1.0.tgz", + "integrity": "sha512-H7BrhggNn77WhdL7O1apG0Q/iwl0Bdd5E1ydhCJzL3oBLh/UYxAwR3EJLsBZ9XA3ZU4PA3UNw4tQjduBTCTmLw==", + "dev": true, + "requires": { + "@jest/types": "^28.1.0", + "@types/node": "*" + } + }, + "jest-util": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/jest-util/-/jest-util-28.1.0.tgz", + "integrity": "sha512-qYdCKD77k4Hwkose2YBEqQk7PzUf/NSE+rutzceduFveQREeH6b+89Dc9+wjX9dAwHcgdx4yedGA3FQlU/qCTA==", + "dev": true, + "requires": { + "@jest/types": "^28.1.0", + "@types/node": "*", + "chalk": "^4.0.0", + "ci-info": "^3.2.0", + "graceful-fs": "^4.2.9", + "picomatch": "^2.2.3" + } + }, + "pretty-format": { + "version": "28.1.0", + "resolved": "https://registry.npmjs.org/pretty-format/-/pretty-format-28.1.0.tgz", + "integrity": "sha512-79Z4wWOYCdvQkEoEuSlBhHJqWeZ8D8YRPiPctJFCtvuaClGpiwiQYSCUOE6IEKUbbFukKOTFIUAXE8N4EQTo1Q==", + "dev": true, + "requires": { + "@jest/schemas": "^28.0.2", + "ansi-regex": "^5.0.1", + "ansi-styles": "^5.0.0", + "react-is": "^18.0.0" + }, + "dependencies": { + "ansi-styles": { + "version": "5.2.0", + "resolved": "https://registry.npmjs.org/ansi-styles/-/ansi-styles-5.2.0.tgz", + "integrity": "sha512-Cxwpt2SfTzTtXcfOlzGEee8O+c+MmUgGrNiBcXnuWxuFJHe6a5Hz7qwhwe5OgaSYI0IJvkLqWX1ASG+cJOkEiA==", + "dev": true + } + } + }, + "react-is": { + "version": "18.1.0", + "resolved": "https://registry.npmjs.org/react-is/-/react-is-18.1.0.tgz", + "integrity": "sha512-Fl7FuabXsJnV5Q1qIOQwx/sagGF18kogb4gpfcG4gjLBWO0WDiiz1ko/ExayuxE7InyQkBLkxRFG5oxY6Uu3Kg==", + "dev": true + }, + "slash": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/slash/-/slash-3.0.0.tgz", + "integrity": "sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==", + "dev": true + } } }, "@jest/reporters": { @@ -23963,6 +25101,15 @@ } } }, + "@jest/schemas": { + "version": "28.0.2", + "resolved": "https://registry.npmjs.org/@jest/schemas/-/schemas-28.0.2.tgz", + "integrity": "sha512-YVDJZjd4izeTDkij00vHHAymNXQ6WWsdChFRK86qck6Jpr3DCL5W3Is3vslviRlP+bLuMYRLbdp98amMvqudhA==", + "dev": true, + "requires": { + "@sinclair/typebox": "^0.23.3" + } + }, "@jest/source-map": { "version": "27.4.0", "resolved": "https://registry.npmjs.org/@jest/source-map/-/source-map-27.4.0.tgz", @@ -24054,9 +25201,9 @@ } }, "@jest/types": { - "version": "27.4.2", - "resolved": "https://registry.npmjs.org/@jest/types/-/types-27.4.2.tgz", - "integrity": "sha512-j35yw0PMTPpZsUoOBiuHzr1zTYoad1cVIE0ajEjcrJONxxrko/IRGKkXx3os0Nsi4Hu3+5VmDbVfq5WhG/pWAg==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/@jest/types/-/types-27.5.1.tgz", + "integrity": "sha512-Cx46iJ9QpwQTjIdq5VJu2QTMMs3QlEjI0x1QbBP5W1+nMzyc2XmimiRR/CbX9TO0cPTeUlxWMOu8mslYsJ8DEw==", "devOptional": true, "requires": { "@types/istanbul-lib-coverage": "^2.0.0", @@ -24441,6 +25588,28 @@ "regenerator-runtime": "^0.13.3" } }, + "@jridgewell/resolve-uri": { + "version": "3.0.7", + "resolved": "https://registry.npmjs.org/@jridgewell/resolve-uri/-/resolve-uri-3.0.7.tgz", + "integrity": "sha512-8cXDaBBHOr2pQ7j77Y6Vp5VDT2sIqWyWQ56TjEq4ih/a4iST3dItRe8Q9fp0rrIl9DoKhWQtUQz/YpOxLkXbNA==", + "dev": true + }, + "@jridgewell/sourcemap-codec": { + "version": "1.4.13", + "resolved": "https://registry.npmjs.org/@jridgewell/sourcemap-codec/-/sourcemap-codec-1.4.13.tgz", + "integrity": "sha512-GryiOJmNcWbovBxTfZSF71V/mXbgcV3MewDe3kIMCLyIh5e7SKAeUZs+rMnJ8jkMolZ/4/VsdBmMrw3l+VdZ3w==", + "dev": true + }, + "@jridgewell/trace-mapping": { + "version": "0.3.11", + "resolved": "https://registry.npmjs.org/@jridgewell/trace-mapping/-/trace-mapping-0.3.11.tgz", + "integrity": "sha512-RllI476aSMsxzeI9TtlSMoNTgHDxEmnl6GkkHwhr0vdL8W+0WuesyI8Vd3rBOfrwtPXbPxdT9ADJdiOKgzxPQA==", + "dev": true, + "requires": { + "@jridgewell/resolve-uri": "^3.0.3", + "@jridgewell/sourcemap-codec": "^1.4.10" + } + }, "@napi-rs/triples": { "version": "1.1.0", "resolved": "https://registry.npmjs.org/@napi-rs/triples/-/triples-1.1.0.tgz", @@ -24841,6 +26010,12 @@ "integrity": "sha512-RNiOoTPkptFtSVzQevY/yWtZwf/RxyVnPy/OcA9HBM3MlGDnBEYL5B41H0MTn0Uec8Hi+2qUtTfG2WWZBmMejQ==", "devOptional": true }, + "@sinclair/typebox": { + "version": "0.23.5", + "resolved": "https://registry.npmjs.org/@sinclair/typebox/-/typebox-0.23.5.tgz", + "integrity": "sha512-AFBVi/iT4g20DHoujvMH1aEDn8fGJh4xsRGCP6d8RpLPMqsNPvW01Jcn0QysXTsg++/xj25NmJsGyH9xug/wKg==", + "dev": true + }, "@sindresorhus/is": { "version": "4.6.0", "resolved": "https://registry.npmjs.org/@sindresorhus/is/-/is-4.6.0.tgz", @@ -25231,9 +26406,9 @@ } }, "@types/react-syntax-highlighter": { - "version": "13.5.2", - "resolved": "https://registry.npmjs.org/@types/react-syntax-highlighter/-/react-syntax-highlighter-13.5.2.tgz", - "integrity": "sha512-sRZoKZBGKaE7CzMvTTgz+0x/aVR58ZYUTfB7HN76vC+yQnvo1FWtzNARBt0fGqcLGEVakEzMu/CtPzssmanu8Q==", + "version": "15.5.1", + "resolved": "https://registry.npmjs.org/@types/react-syntax-highlighter/-/react-syntax-highlighter-15.5.1.tgz", + "integrity": "sha512-+yD6D8y21JqLf89cRFEyRfptVMqo2ROHyAlysRvFwT28gT5gDo3KOiXHwGilHcq9y/OKTjlWK0f/hZUicrBFPQ==", "dev": true, "requires": { "@types/react": "*" @@ -25713,6 +26888,15 @@ "integrity": "sha512-Z7tMw1ytTXt5jqMcOP+OQteU1VuNK9Y02uuJtKQ1Sv69jXQKKg5cibLwGJow8yzZP+eAc18EmLGPal0bp36rvQ==", "dev": true }, + "async": { + "version": "2.6.4", + "resolved": "https://registry.npmjs.org/async/-/async-2.6.4.tgz", + "integrity": "sha512-mzo5dfJYwAn29PeiJ0zvwTo04zj8HDJj0Mn8TD7sno7q12prdbnasKJHhkm2c1LgrhlJ0teaea8860oxi51mGA==", + "optional": true, + "requires": { + "lodash": "^4.17.14" + } + }, "async-limiter": { "version": "1.0.1", "resolved": "https://registry.npmjs.org/async-limiter/-/async-limiter-1.0.1.tgz", @@ -26972,6 +28156,16 @@ "resolved": "https://registry.npmjs.org/builtin-status-codes/-/builtin-status-codes-3.0.0.tgz", "integrity": "sha1-hZgoeOIbmOHGZCXgPQF0eI9Wnug=" }, + "builtins": { + "version": "4.1.0", + "resolved": "https://registry.npmjs.org/builtins/-/builtins-4.1.0.tgz", + "integrity": "sha512-1bPRZQtmKaO6h7qV1YHXNtr6nCK28k0Zo95KM4dXfILcZZwoHJBN1m3lfLv9LPkcOZlrSr+J1bzMaZFO98Yq0w==", + "dev": true, + "peer": true, + "requires": { + "semver": "^7.0.0" + } + }, "cacheable-lookup": { "version": "5.0.4", "resolved": "https://registry.npmjs.org/cacheable-lookup/-/cacheable-lookup-5.0.4.tgz", @@ -27997,9 +29191,9 @@ "integrity": "sha512-/VTCrvm5Z0JGty/BWHljh+BAiw3IK+2j87NGMu8Nwc/f48WoDAC395uomO9ZD117ZOBaHmkX1oyLvkVM/aIT3w==" }, "diff-sequences": { - "version": "27.4.0", - "resolved": "https://registry.npmjs.org/diff-sequences/-/diff-sequences-27.4.0.tgz", - "integrity": "sha512-YqiQzkrsmHMH5uuh8OdQFU9/ZpADnwzml8z0O5HvRNda+5UZsaX/xN+AAxfR2hWq1Y7HZnAzO9J5lJXOuDz2Ww==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/diff-sequences/-/diff-sequences-27.5.1.tgz", + "integrity": "sha512-k1gCAXAsNgLwEL+Y8Wvl+M6oEFj5bgazfZULpS5CneoPPXRaCCW7dm+q21Ky2VEE5X+VeRDBVg1Pcvvsr4TtNQ==", "dev": true }, "diffie-hellman": { @@ -28644,9 +29838,9 @@ "requires": {} }, "eslint-config-standard": { - "version": "16.0.3", - "resolved": "https://registry.npmjs.org/eslint-config-standard/-/eslint-config-standard-16.0.3.tgz", - "integrity": "sha512-x4fmJL5hGqNJKGHSjnLdgA6U6h1YW/G2dW9fA+cyVur4SK6lyue8+UgNKWlZtUDTXvgKDD/Oa3GQjmB5kjtVvg==", + "version": "17.0.0", + "resolved": "https://registry.npmjs.org/eslint-config-standard/-/eslint-config-standard-17.0.0.tgz", + "integrity": "sha512-/2ks1GKyqSOkH7JFvXJicu0iMpoojkwB+f5Du/1SC0PtBL+s8v30k9njRZ21pm2drKYm2342jFnGWzttxPmZVg==", "dev": true, "requires": {} }, @@ -28692,6 +29886,17 @@ } } }, + "eslint-plugin-es": { + "version": "4.1.0", + "resolved": "https://registry.npmjs.org/eslint-plugin-es/-/eslint-plugin-es-4.1.0.tgz", + "integrity": "sha512-GILhQTnjYE2WorX5Jyi5i4dz5ALWxBIdQECVQavL6s7cI76IZTDWleTHkxz/QT3kvcs2QlGHvKLYsSlPOlPXnQ==", + "dev": true, + "peer": true, + "requires": { + "eslint-utils": "^2.0.0", + "regexpp": "^3.0.0" + } + }, "eslint-plugin-import": { "version": "2.25.4", "resolved": "https://registry.npmjs.org/eslint-plugin-import/-/eslint-plugin-import-2.25.4.tgz", @@ -28799,6 +30004,63 @@ } } }, + "eslint-plugin-n": { + "version": "15.2.0", + "resolved": "https://registry.npmjs.org/eslint-plugin-n/-/eslint-plugin-n-15.2.0.tgz", + "integrity": "sha512-lWLg++jGwC88GDGGBX3CMkk0GIWq0y41aH51lavWApOKcMQcYoL3Ayd0lEdtD3SnQtR+3qBvWQS3qGbR2BxRWg==", + "dev": true, + "peer": true, + "requires": { + "builtins": "^4.0.0", + "eslint-plugin-es": "^4.1.0", + "eslint-utils": "^3.0.0", + "ignore": "^5.1.1", + "is-core-module": "^2.3.0", + "minimatch": "^3.0.4", + "resolve": "^1.10.1", + "semver": "^6.3.0" + }, + "dependencies": { + "brace-expansion": { + "version": "1.1.11", + "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz", + "integrity": "sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==", + "dev": true, + "peer": true, + "requires": { + "balanced-match": "^1.0.0", + "concat-map": "0.0.1" + } + }, + "eslint-utils": { + "version": "3.0.0", + "resolved": "https://registry.npmjs.org/eslint-utils/-/eslint-utils-3.0.0.tgz", + "integrity": "sha512-uuQC43IGctw68pJA1RgbQS8/NP7rch6Cwd4j3ZBtgo4/8Flj4eGE7ZYSZRN3iq5pVUv6GPdW5Z1RFleo84uLDA==", + "dev": true, + "peer": true, + "requires": { + "eslint-visitor-keys": "^2.0.0" + } + }, + "minimatch": { + "version": "3.1.2", + "resolved": "https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz", + "integrity": "sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==", + "dev": true, + "peer": true, + "requires": { + "brace-expansion": "^1.1.7" + } + }, + "semver": { + "version": "6.3.0", + "resolved": "https://registry.npmjs.org/semver/-/semver-6.3.0.tgz", + "integrity": "sha512-b39TBaTSfV6yBrapU89p5fKekE2m/NwnDocOVruQFS1/veMgdzuPcnOM34M6CwxW8jH/lxEa5rBoDeUwu5HHTw==", + "dev": true, + "peer": true + } + } + }, "eslint-plugin-node": { "version": "11.1.0", "resolved": "https://registry.npmjs.org/eslint-plugin-node/-/eslint-plugin-node-11.1.0.tgz", @@ -29071,15 +30333,15 @@ } }, "expect": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/expect/-/expect-27.4.6.tgz", - "integrity": "sha512-1M/0kAALIaj5LaG66sFJTbRsWTADnylly82cu4bspI0nl+pgP4E6Bh/aqdHlTUjul06K7xQnnrAoqfxVU0+/ag==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/expect/-/expect-27.5.1.tgz", + "integrity": "sha512-E1q5hSUG2AmYQwQJ041nvgpkODHQvB+RKlB4IYdru6uJsyFTRyZAP463M+1lINorwbqAmUggi6+WwkD8lCS/Dw==", "dev": true, "requires": { - "@jest/types": "^27.4.2", - "jest-get-type": "^27.4.0", - "jest-matcher-utils": "^27.4.6", - "jest-message-util": "^27.4.6" + "@jest/types": "^27.5.1", + "jest-get-type": "^27.5.1", + "jest-matcher-utils": "^27.5.1", + "jest-message-util": "^27.5.1" } }, "expect-puppeteer": { @@ -29529,6 +30791,12 @@ "integrity": "sha1-FQStJSMVjKpA20onh8sBQRmU6k8=", "devOptional": true }, + "fsevents": { + "version": "2.3.2", + "resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.2.tgz", + "integrity": "sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT7jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt812P9ab+DDKA==", + "optional": true + }, "function-bind": { "version": "1.1.1", "resolved": "https://registry.npmjs.org/function-bind/-/function-bind-1.1.1.tgz", @@ -29885,9 +31153,9 @@ } }, "graceful-fs": { - "version": "4.2.8", - "resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.8.tgz", - "integrity": "sha512-qkIilPUYcNhJpd33n0GBXTB1MMPp14TxEsEs0pTrsSVucApsYzW5V+Q8Qxhik6KU3evy+qkAAowTByymK0avdg==" + "version": "4.2.10", + "resolved": "https://registry.npmjs.org/graceful-fs/-/graceful-fs-4.2.10.tgz", + "integrity": "sha512-9ByhssR2fPVsNZj478qUUbKfmL0+t5BDVyjShtyZZLiK7ZDAArFFfopyOTj0M05wE2tJPisA4iTnnXl2YoPvOA==" }, "graphql": { "version": "16.3.0", @@ -31175,15 +32443,15 @@ } }, "jest-diff": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/jest-diff/-/jest-diff-27.4.6.tgz", - "integrity": "sha512-zjaB0sh0Lb13VyPsd92V7HkqF6yKRH9vm33rwBt7rPYrpQvS1nCvlIy2pICbKta+ZjWngYLNn4cCK4nyZkjS/w==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/jest-diff/-/jest-diff-27.5.1.tgz", + "integrity": "sha512-m0NvkX55LDt9T4mctTEgnZk3fmEg3NRYutvMPWM/0iPnkFj2wIeF45O1718cMSOFO1vINkqmxqD8vE37uTEbqw==", "dev": true, "requires": { "chalk": "^4.0.0", - "diff-sequences": "^27.4.0", - "jest-get-type": "^27.4.0", - "pretty-format": "^27.4.6" + "diff-sequences": "^27.5.1", + "jest-get-type": "^27.5.1", + "pretty-format": "^27.5.1" }, "dependencies": { "chalk": { @@ -31308,9 +32576,9 @@ } }, "jest-get-type": { - "version": "27.4.0", - "resolved": "https://registry.npmjs.org/jest-get-type/-/jest-get-type-27.4.0.tgz", - "integrity": "sha512-tk9o+ld5TWq41DkK14L4wox4s2D9MtTpKaAVzXfr5CUKm5ZK2ExcaFE0qls2W71zE/6R2TxxrK9w2r6svAFDBQ==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/jest-get-type/-/jest-get-type-27.5.1.tgz", + "integrity": "sha512-2KY95ksYSaK7DMBWQn6dQz3kqAf3BB64y2udeG+hv4KfSOb9qwcYQstTJc1KCbsix+wLZWZYN8t7nwX3GOBLRw==", "dev": true }, "jest-github-actions-reporter": { @@ -31391,15 +32659,15 @@ } }, "jest-matcher-utils": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/jest-matcher-utils/-/jest-matcher-utils-27.4.6.tgz", - "integrity": "sha512-XD4PKT3Wn1LQnRAq7ZsTI0VRuEc9OrCPFiO1XL7bftTGmfNF0DcEwMHRgqiu7NGf8ZoZDREpGrCniDkjt79WbA==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/jest-matcher-utils/-/jest-matcher-utils-27.5.1.tgz", + "integrity": "sha512-z2uTx/T6LBaCoNWNFWwChLBKYxTMcGBRjAt+2SbP929/Fflb9aa5LGma654Rz8z9HLxsrUaYzxE9T/EFIL/PAw==", "dev": true, "requires": { "chalk": "^4.0.0", - "jest-diff": "^27.4.6", - "jest-get-type": "^27.4.0", - "pretty-format": "^27.4.6" + "jest-diff": "^27.5.1", + "jest-get-type": "^27.5.1", + "pretty-format": "^27.5.1" }, "dependencies": { "chalk": { @@ -31415,18 +32683,18 @@ } }, "jest-message-util": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/jest-message-util/-/jest-message-util-27.4.6.tgz", - "integrity": "sha512-0p5szriFU0U74czRSFjH6RyS7UYIAkn/ntwMuOwTGWrQIOh5NzXXrq72LOqIkJKKvFbPq+byZKuBz78fjBERBA==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/jest-message-util/-/jest-message-util-27.5.1.tgz", + "integrity": "sha512-rMyFe1+jnyAAf+NHwTclDz0eAaLkVDdKVHHBFWsBWHnnh5YeJMNWWsv7AbFYXfK3oTqvL7VTWkhNLu1jX24D+g==", "devOptional": true, "requires": { "@babel/code-frame": "^7.12.13", - "@jest/types": "^27.4.2", + "@jest/types": "^27.5.1", "@types/stack-utils": "^2.0.0", "chalk": "^4.0.0", - "graceful-fs": "^4.2.4", + "graceful-fs": "^4.2.9", "micromatch": "^4.0.4", - "pretty-format": "^27.4.6", + "pretty-format": "^27.5.1", "slash": "^3.0.0", "stack-utils": "^2.0.3" }, @@ -31450,12 +32718,12 @@ } }, "jest-mock": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/jest-mock/-/jest-mock-27.4.6.tgz", - "integrity": "sha512-kvojdYRkst8iVSZ1EJ+vc1RRD9llueBjKzXzeCytH3dMM7zvPV/ULcfI2nr0v0VUgm3Bjt3hBCQvOeaBz+ZTHw==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/jest-mock/-/jest-mock-27.5.1.tgz", + "integrity": "sha512-K4jKbY1d4ENhbrG2zuPWaQBvDly+iZ2yAW+T1fATN78hc0sInwn7wZB8XtlNnvHug5RMwV897Xm4LqmPM4e2Og==", "devOptional": true, "requires": { - "@jest/types": "^27.4.2", + "@jest/types": "^27.5.1", "@types/node": "*" } }, @@ -31601,6 +32869,17 @@ "strip-bom": "^4.0.0" }, "dependencies": { + "@jest/globals": { + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/@jest/globals/-/globals-27.5.1.tgz", + "integrity": "sha512-ZEJNB41OBQQgGzgyInAv0UUfDDj3upmHydjieSxFvTRuZElrx7tXg/uVQ5hYVEwiXs3+aMsAeEc9X7xiSKCm4Q==", + "dev": true, + "requires": { + "@jest/environment": "^27.5.1", + "@jest/types": "^27.5.1", + "expect": "^27.5.1" + } + }, "brace-expansion": { "version": "1.1.11", "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz", @@ -31711,16 +32990,16 @@ } }, "jest-util": { - "version": "27.4.2", - "resolved": "https://registry.npmjs.org/jest-util/-/jest-util-27.4.2.tgz", - "integrity": "sha512-YuxxpXU6nlMan9qyLuxHaMMOzXAl5aGZWCSzben5DhLHemYQxCc4YK+4L3ZrCutT8GPQ+ui9k5D8rUJoDioMnA==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/jest-util/-/jest-util-27.5.1.tgz", + "integrity": "sha512-Kv2o/8jNvX1MQ0KGtw480E/w4fBCDOnH6+6DmeKi6LZUIlKA5kwY0YNdlzaWTiVgxqAqik11QyxDOKk543aKXw==", "devOptional": true, "requires": { - "@jest/types": "^27.4.2", + "@jest/types": "^27.5.1", "@types/node": "*", "chalk": "^4.0.0", "ci-info": "^3.2.0", - "graceful-fs": "^4.2.4", + "graceful-fs": "^4.2.9", "picomatch": "^2.2.3" }, "dependencies": { @@ -31994,9 +33273,9 @@ } }, "kill-port": { - "version": "1.6.1", - "resolved": "https://registry.npmjs.org/kill-port/-/kill-port-1.6.1.tgz", - "integrity": "sha512-un0Y55cOM7JKGaLnGja28T38tDDop0AQ8N0KlAdyh+B1nmMoX8AnNmqPNZbS3mUMgiST51DCVqmbFT1gNJpVNw==", + "version": "2.0.0", + "resolved": "https://registry.npmjs.org/kill-port/-/kill-port-2.0.0.tgz", + "integrity": "sha512-TWGAJ/SGy52aKhYpPSCw4S/WR0rTYkC2+6oRp5xBlLo4UvJe3Gt0MwROO8hI+Hu4YkTDhe27EPKKeFUtqNNfdA==", "dev": true, "requires": { "get-them-args": "1.3.2", @@ -33823,9 +35102,9 @@ } }, "nodemon": { - "version": "2.0.15", - "resolved": "https://registry.npmjs.org/nodemon/-/nodemon-2.0.15.tgz", - "integrity": "sha512-gdHMNx47Gw7b3kWxJV64NI+Q5nfl0y5DgDbiVtShiwa7Z0IZ07Ll4RLFo6AjrhzMtoEZn5PDE3/c2AbVsiCkpA==", + "version": "2.0.16", + "resolved": "https://registry.npmjs.org/nodemon/-/nodemon-2.0.16.tgz", + "integrity": "sha512-zsrcaOfTWRuUzBn3P44RDliLlp263Z/76FPoHFr3cFFkOz0lTPAcIw8dCzfdVIx/t3AtDYCZRCDkoCojJqaG3w==", "dev": true, "requires": { "chokidar": "^3.5.2", @@ -34418,15 +35697,6 @@ "array-uniq": "^1.0.1" } }, - "async": { - "version": "2.6.3", - "resolved": "https://registry.npmjs.org/async/-/async-2.6.3.tgz", - "integrity": "sha512-zflvls11DCy+dQWzTW2dzuilv8Z5X/pjfmZOWba6TNIVDm+2UDaJmXSOXlasHKfNBs8oo3M0aT50fDEWfKZjXg==", - "optional": true, - "requires": { - "lodash": "^4.17.14" - } - }, "brace-expansion": { "version": "1.1.11", "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz", @@ -35260,9 +36530,9 @@ "dev": true }, "pretty-format": { - "version": "27.4.6", - "resolved": "https://registry.npmjs.org/pretty-format/-/pretty-format-27.4.6.tgz", - "integrity": "sha512-NblstegA1y/RJW2VyML+3LlpFjzx62cUrtBIKIWDXEDkjNeleA7Od7nrzcs/VLQvAeV4CgSYhrN39DRN88Qi/g==", + "version": "27.5.1", + "resolved": "https://registry.npmjs.org/pretty-format/-/pretty-format-27.5.1.tgz", + "integrity": "sha512-Qb1gy5OrP5+zDf2Bvnzdl3jsTf1qXVMazbvCoKhtKqVs4/YK4ozX4gKQJJVyNe+cajNPn0KoC0MC3FUmaHWEmQ==", "devOptional": true, "requires": { "ansi-regex": "^5.0.1", diff --git a/package.json b/package.json index 3baed2ec8f..b4b9dfa09f 100644 --- a/package.json +++ b/package.json @@ -103,7 +103,7 @@ "@babel/preset-env": "^7.16.11", "@graphql-inspector/core": "^3.1.1", "@graphql-tools/load": "^7.4.1", - "@jest/globals": "^27.4.6", + "@jest/globals": "^28.1.0", "@octokit/graphql": "4.8.0", "@octokit/rest": "^18.12.0", "@types/github-slugger": "^1.3.0", @@ -112,7 +112,7 @@ "@types/lodash": "^4.14.178", "@types/react": "^17.0.38", "@types/react-dom": "^18.0.0", - "@types/react-syntax-highlighter": "^13.5.2", + "@types/react-syntax-highlighter": "^15.5.1", "@types/uuid": "^8.3.4", "@typescript-eslint/eslint-plugin": "5.23.0", "@typescript-eslint/parser": "5.23.0", @@ -128,7 +128,7 @@ "domwaiter": "^1.3.0", "eslint": "8.11.0", "eslint-config-prettier": "^8.3.0", - "eslint-config-standard": "^16.0.3", + "eslint-config-standard": "^17.0.0", "eslint-plugin-import": "^2.25.4", "eslint-plugin-jsx-a11y": "^6.5.1", "eslint-plugin-node": "^11.1.0", @@ -145,7 +145,7 @@ "jest-fail-on-console": "^2.2.3", "jest-github-actions-reporter": "^1.0.3", "jest-slow-test-reporter": "^1.0.0", - "kill-port": "1.6.1", + "kill-port": "2.0.0", "linkinator": "^3.0.3", "lint-staged": "^12.3.3", "make-promises-safe": "^5.1.0", @@ -153,7 +153,7 @@ "mkdirp": "^1.0.4", "mockdate": "^3.0.5", "nock": "^13.2.2", - "nodemon": "^2.0.15", + "nodemon": "2.0.16", "npm-merge-driver-install": "^3.0.0", "postcss": "^8.4.6", "prettier": "^2.5.1", diff --git a/pages/[versionId]/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.tsx b/pages/[versionId]/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.tsx deleted file mode 100644 index 97fab2133b..0000000000 --- a/pages/[versionId]/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.tsx +++ /dev/null @@ -1,5 +0,0 @@ -import PlaygroundArticlePage from 'components/playground/PlaygroundArticlePage' - -export { getServerSideProps } from 'components/playground/PlaygroundArticlePage' - -export default PlaygroundArticlePage diff --git a/pages/_app.tsx b/pages/_app.tsx index 5b5fd697b8..eab4108e82 100644 --- a/pages/_app.tsx +++ b/pages/_app.tsx @@ -4,17 +4,17 @@ import type { AppProps, AppContext } from 'next/app' import Head from 'next/head' import { ThemeProvider, ThemeProviderProps } from '@primer/react' import { SSRProvider } from '@react-aria/ssr' -import { defaultComponentThemeProps, getThemeProps } from 'components/lib/getThemeProps' import '../stylesheets/index.scss' import events from 'components/lib/events' import experiment from 'components/lib/experiment' import { LanguagesContext, LanguagesContextT } from 'components/context/LanguagesContext' +import { defaultComponentTheme } from 'lib/get-theme.js' type MyAppProps = AppProps & { csrfToken: string - themeProps: typeof defaultComponentThemeProps & Pick + themeProps: typeof defaultComponentTheme & Pick languagesContext: LanguagesContextT } const MyApp = ({ Component, pageProps, csrfToken, themeProps, languagesContext }: MyAppProps) => { @@ -72,9 +72,11 @@ MyApp.getInitialProps = async (appContext: AppContext) => { const appProps = await App.getInitialProps(appContext) const req: any = ctx.req + const { getTheme } = await import('lib/get-theme.js') + return { ...appProps, - themeProps: getThemeProps(req), + themeProps: getTheme(req), csrfToken: req?.csrfToken?.() || '', languagesContext: { languages: req.context.languages }, } diff --git a/pages/_document.tsx b/pages/_document.tsx index 9dc7388c4c..71736d6e66 100644 --- a/pages/_document.tsx +++ b/pages/_document.tsx @@ -2,7 +2,7 @@ import Document, { DocumentContext, Html, Head, Main, NextScript } from 'next/do import { ServerStyleSheet } from 'styled-components' -import { getThemeProps } from 'components/lib/getThemeProps' +import { getTheme } from 'lib/get-theme.js' export default class MyDocument extends Document { static async getInitialProps(ctx: DocumentContext) { @@ -18,7 +18,7 @@ export default class MyDocument extends Document { const initialProps = await Document.getInitialProps(ctx) return { ...initialProps, - cssThemeProps: getThemeProps(ctx.req, 'css'), + cssThemeProps: getTheme(ctx.req, true), styles: ( <> {initialProps.styles} diff --git a/script/check-english-links.js b/script/check-english-links.js index 3b2411bab2..edba4263c7 100755 --- a/script/check-english-links.js +++ b/script/check-english-links.js @@ -25,7 +25,7 @@ import libLanguages from '../lib/languages.js' const __dirname = path.dirname(fileURLToPath(import.meta.url)) const checker = new LinkChecker() -const root = 'https://docs.github.com' +const root = 'http://localhost:4000' const englishRoot = `${root}/en` // Links with these codes may or may not really be broken. @@ -66,7 +66,13 @@ const config = { recurse: !program.opts().dryRun, silent: true, // The values in this array are treated as regexes. - linksToSkip: linksToSkipFactory([enterpriseReleasesToSkip, ...languagesToSkip, ...excludedLinks]), + linksToSkip: linksToSkipFactory([ + enterpriseReleasesToSkip, + ...languagesToSkip, + ...excludedLinks, + // Don't leak into the production site + /https:\/\/docs\.github\.com/, + ]), } // Return a function that can as quickly as possible check if a certain diff --git a/script/helpers/get-liquid-conditionals.js b/script/helpers/get-liquid-conditionals.js index 44ec9899a3..9143f92058 100644 --- a/script/helpers/get-liquid-conditionals.js +++ b/script/helpers/get-liquid-conditionals.js @@ -72,7 +72,9 @@ function getLiquidConditionalsWithContent(str, tagName) { function groupTokens(tokens, tagName, endTagName, newArray = []) { const startIndex = tokens.findIndex((token) => token.conditional === tagName) // The end tag name is currently in a separate token, but we want to group it with the start tag and content. - const endIndex = tokens.findIndex((token) => token.conditional === endTagName) + const endIndex = tokens.findIndex( + (token, index) => token.conditional === endTagName && index > startIndex + ) // Once all tags are grouped and removed from `tokens`, this findIndex will not find anything, // so we can return the grouped result at this point. if (startIndex === -1) return newArray diff --git a/script/helpers/get-version-blocks.js b/script/helpers/get-version-blocks.js index 69f88d88df..1340868581 100644 --- a/script/helpers/get-version-blocks.js +++ b/script/helpers/get-version-blocks.js @@ -33,7 +33,7 @@ export default function getVersionBlocks(rawBlocks) { innerText = innerText.slice(0, indexOfLastEndif) // Remove any nested conditional content so we can check the top-level only. - const topLevelContent = innerText.replace(/{%-? ifversion[\S\s]+?{%-? endif -?%}/g, '') + const topLevelContent = innerText.replace(/{%-? ifversion[\S\s]+{%-? endif -?%}/g, '') versionBlocks.push({ condKeyword, diff --git a/script/helpers/remove-liquid-statements.js b/script/helpers/remove-liquid-statements.js index 21ec29d413..d7ec06b577 100644 --- a/script/helpers/remove-liquid-statements.js +++ b/script/helpers/remove-liquid-statements.js @@ -6,6 +6,8 @@ const supportedShortVersions = Object.values(allVersions).map((v) => v.shortName const updateRangeKeepGhes = 'updateRangeKeepGhes' const updateRangeRemoveGhes = 'updateRangeRemoveGhes' const removeRangeAndContent = 'removeRangeAndContent' +const removeConditionals = 'removeConditionals' + const tokenize = (str) => { const tokenizer = new Tokenizer(str) return tokenizer.readTopLevelTokens() @@ -33,6 +35,10 @@ export default function removeLiquidStatements(content, release, nextOldestRelea const isSafeToRemoveContent = versionBlock.isGhesOnly && (versionBlock.hasSingleRange || versionBlock.andGhesRanges.length) + if (isConditionalNecessary(supportedShortVersions, versionBlock.condArgs)) { + actionMap[removeConditionals] = true + } + for (const rangeArgs of versionBlock.ranges) { const rangeOperator = rangeArgs[1] const releaseNumber = rangeArgs[2] @@ -134,6 +140,7 @@ export default function removeLiquidStatements(content, release, nextOldestRelea } // ----- UPDATE RANGE AND KEEP `GHES` ----- + let containsAllSupportedVersions if (versionBlock.action.updateRangeKeepGhes) { const replacement = versionBlock.action.updateRangeKeepGhes.replace(/ghes.+$/, 'ghes') @@ -145,9 +152,9 @@ export default function removeLiquidStatements(content, release, nextOldestRelea // If the new conditional contains all the currently supported versions, no conditional // is actually needed, and it can be removed. Any `else` statements and their content should // also be removed. - const containsAllSupportedVersions = supportedShortVersions.every( - (v) => newCondWithLiquid.includes(v) && !newCondWithLiquid.includes('issue') - // The writers are using "issue" versions for upcoming GHAE releases + containsAllSupportedVersions = isConditionalNecessary( + supportedShortVersions, + newCondWithLiquid ) if (!containsAllSupportedVersions) { @@ -156,62 +163,66 @@ export default function removeLiquidStatements(content, release, nextOldestRelea newCondWithLiquid ) } + } - if (containsAllSupportedVersions) { - versionBlock.newContent = versionBlock.content + // ----- REMOVE CONDITIONALS ----- + // this happens if either: + // (a) the the conditional was updated in a previous step to contain all the currently supported versions, or + // (b) the conditional was not touched but its arguments already contained all supported versions, making it unnecessary + if (containsAllSupportedVersions || versionBlock.action.removeConditionals) { + versionBlock.newContent = versionBlock.content - // If this block does not contain else/elsifs, start by removing the final endif. - // (We'll handle the endif separately in those scenarios.) - if (!versionBlock.hasElse && !versionBlock.hasElsif) { - const indexOfLastEndif = lastIndexOfRegex(versionBlock.content, /{%-? endif -?%}/g) + // If this block does not contain else/elsifs, start by removing the final endif. + // (We'll handle the endif separately in those scenarios.) + if (!versionBlock.hasElse && !versionBlock.hasElsif) { + const indexOfLastEndif = lastIndexOfRegex(versionBlock.content, /{%-? endif -?%}/g) - versionBlock.newContent = versionBlock.newContent.slice(0, indexOfLastEndif) + versionBlock.newContent = versionBlock.newContent.slice(0, indexOfLastEndif) - if (versionBlock.endTagColumn1 && versionBlock.newContent.endsWith('\n')) - versionBlock.newContent = versionBlock.newContent.slice(0, -1) - } + if (versionBlock.endTagColumn1 && versionBlock.newContent.endsWith('\n')) + versionBlock.newContent = versionBlock.newContent.slice(0, -1) + } - // If start tag is on it's own line, remove line ending (\\n?) - // and remove white space (//s*) after line ending to - // preserve indentation of next line - const removeStartTagRegex = versionBlock.startTagColumn1 - ? new RegExp(`${versionBlock.condWithLiquid}\\n?\\s*`) - : new RegExp(`${versionBlock.condWithLiquid}`) + // If start tag is on it's own line, remove line ending (\\n?) + // and remove white space (//s*) after line ending to + // preserve indentation of next line + const removeStartTagRegex = versionBlock.startTagColumn1 + ? new RegExp(`${versionBlock.condWithLiquid}\\n?\\s*`) + : new RegExp(`${versionBlock.condWithLiquid}`) - // For ALL scenarios, remove the start tag. - versionBlock.newContent = versionBlock.newContent.replace(removeStartTagRegex, '') + // For ALL scenarios, remove the start tag. + versionBlock.newContent = versionBlock.newContent.replace(removeStartTagRegex, '') - // If the block has an elsif, change the elsif to an if (or leave it an elsif this this block is itself an elsif), - // leaving the content inside the elsif block as is. Also leave the endif in this scenario. - if (versionBlock.hasElsif) { - versionBlock.newContent = versionBlock.newContent.replace( - /({%-) elsif/, - `$1 ${versionBlock.condKeyword}` - ) - } + // If the block has an elsif, change the elsif to an if (or leave it an elsif this this block is itself an elsif), + // leaving the content inside the elsif block as is. Also leave the endif in this scenario. + if (versionBlock.hasElsif) { + versionBlock.newContent = versionBlock.newContent.replace( + /({%-) elsif/, + `$1 ${versionBlock.condKeyword}` + ) + } - // If the block has an else, remove the else, its content, and the endif. - if (versionBlock.hasElse) { - let elseStartIndex - let ifCondFlag = false - // tokenize the content including the nested conditionals to find - // the unmatched else tag. Remove content from the start of the - // else tag to the end of the content. The tokens return have different - // `kind`s and can be liquid tags, HTML, and a variety of things. - // A value of 4 is a liquid tag. See https://liquidjs.com/api/enums/parser_token_kind_.tokenkind.html. - tokenize(versionBlock.newContent) - .filter((elem) => elem.kind === 4) - .forEach((tag) => { - if (tag.name === 'ifversion' || tag.name === 'if') { - ifCondFlag = true - } else if (tag.name === 'endif' && ifCondFlag === true) { - ifCondFlag = false - } else if (tag.name === 'else' && ifCondFlag === false) { - elseStartIndex = tag.begin - } - }) - versionBlock.newContent = versionBlock.newContent.slice(0, elseStartIndex) - } + // If the block has an else, remove the else, its content, and the endif. + if (versionBlock.hasElse) { + let elseStartIndex + let ifCondFlag = false + // tokenize the content including the nested conditionals to find + // the unmatched else tag. Remove content from the start of the + // else tag to the end of the content. The tokens return have different + // `kind`s and can be liquid tags, HTML, and a variety of things. + // A value of 4 is a liquid tag. See https://liquidjs.com/api/enums/parser_token_kind_.tokenkind.html. + tokenize(versionBlock.newContent) + .filter((elem) => elem.kind === 4) + .forEach((tag) => { + if (tag.name === 'ifversion' || tag.name === 'if') { + ifCondFlag = true + } else if (tag.name === 'endif' && ifCondFlag === true) { + ifCondFlag = false + } else if (tag.name === 'else' && ifCondFlag === false) { + elseStartIndex = tag.begin + } + }) + versionBlock.newContent = versionBlock.newContent.slice(0, elseStartIndex) } } }) @@ -244,3 +255,14 @@ function lastIndexOfRegex(str, regex, fromIndex) { return match ? myStr.lastIndexOf(match[match.length - 1]) : -1 } + +// Checks if a conditional is necessary given all the supported versions and the arguments in a conditional +// If all supported versions show up in the arguments, it's not necessary! Additionally, builds in support +// for when feature-based versioning is used, which looks like "issue" versions for upcoming GHAE releases +function isConditionalNecessary(supportedVersions, conditionalArguments) { + return supportedVersions.every( + (arg) => + (conditionalArguments.includes(arg) || conditionalArguments.includes('or ' + arg)) && + !conditionalArguments.includes('issue') + ) +} diff --git a/tests/content/featured-links.js b/tests/content/featured-links.js index 0a60885ad3..4a15e55b4c 100644 --- a/tests/content/featured-links.js +++ b/tests/content/featured-links.js @@ -45,9 +45,9 @@ describe('featuredLinks', () => { expect($featuredLinks.eq(8).attr('href')).toBe('/en/pages') expect($featuredLinks.eq(8).children('h3').text().startsWith('GitHub Pages')).toBe(true) - expect($featuredLinks.eq(8).children('p').text().startsWith('You can create a website')).toBe( - true - ) + expect( + $featuredLinks.eq(8).children('p').text().startsWith('Learn how to create a website') + ).toBe(true) }) test('localized intro links link to localized pages', async () => { diff --git a/tests/content/remove-liquid-statements.js b/tests/content/remove-liquid-statements.js index 2c65fca324..cdd0cc9894 100644 --- a/tests/content/remove-liquid-statements.js +++ b/tests/content/remove-liquid-statements.js @@ -14,6 +14,7 @@ const nextOldestVersion = '2.14' // Remove liquid only const greaterThan = path.join(removeLiquidStatementsFixtures, 'greater-than.md') +const unnecessary = path.join(removeLiquidStatementsFixtures, 'unnecessary.md') const andGreaterThan1 = path.join(removeLiquidStatementsFixtures, 'and-greater-than1.md') const andGreaterThan2 = path.join(removeLiquidStatementsFixtures, 'and-greater-than2.md') const notEquals = path.join(removeLiquidStatementsFixtures, 'not-equals.md') @@ -63,6 +64,24 @@ Alpha\n\n{% else %}\n\nBravo\n\n{% ifversion ghes > 2.16 %}\n\nCharlie\n expect($('.example10').text().trim()).toBe(`{% ifversion ghes %}\n\nAlpha\n {% else %}\n\nBravo\n\n{% endif %}`) }) + test('removes liquid statements that specify all known versions, including some nested conditionals"', async () => { + let contents = await readFileAsync(unnecessary, 'utf8') + contents = removeLiquidStatements(contents, versionToDeprecate, nextOldestVersion) + const $ = cheerio.load(contents) + expect($('.example1').text().trim()).toBe(`Alpha`) + expect($('.example2').text().trim()).toBe( + `Alpha\n {% ifversion fpt or ghec %}\n Bravo\n {% endif %}` + ) + expect($('.example3').text().trim()).toBe( + `Alpha\n {% ifversion fpt or ghec %}\n Bravo\n {% else %}\n Delta\n {% endif %}` + ) + expect($('.example4').text().trim()).toBe( + `Alpha\n {% ifversion fpt or ghec %}\n Bravo\n {% ifversion ghae %}\n Charlie\n {% endif %}\n {% endif %}` + ) + expect($('.example5').text().trim()).toBe( + `Alpha\n {% ifversion fpt or ghec %}\n Bravo\n {% ifversion ghae %}\n Charlie\n {% endif %}\n {% else %}\n Delta\n {% endif %}` + ) + }) test('removes liquid statements that specify "and greater than version to deprecate"', async () => { let contents = await readFileAsync(andGreaterThan1, 'utf8') diff --git a/tests/fixtures/remove-liquid-statements/unnecessary.md b/tests/fixtures/remove-liquid-statements/unnecessary.md new file mode 100644 index 0000000000..fa529ecf1a --- /dev/null +++ b/tests/fixtures/remove-liquid-statements/unnecessary.md @@ -0,0 +1,72 @@ +--- +title: Remove unnecessary conditionals including nested +intro: Remove liquid only +--- + +## 1 +
+ +{% ifversion fpt or ghes or ghae or ghec %} +Alpha +{% endif %} + +
+ +## 2 +
+ +{% ifversion fpt or ghes or ghae or ghec %} +Alpha + {% ifversion fpt or ghec %} + Bravo + {% endif %} +{% endif %} + +
+ +## 3 +
+ +{% ifversion fpt or ghes or ghae or ghec %} +Alpha + {% ifversion fpt or ghec %} + Bravo + {% else %} + Delta + {% endif %} +{% endif %} + +
+ +## 4 +
+ +{% ifversion fpt or ghes or ghae or ghec %} +Alpha + {% ifversion fpt or ghec %} + Bravo + {% ifversion ghae %} + Charlie + {% endif %} + {% endif %} +{% endif %} + +
+ +## 5 +
+ +{% ifversion fpt or ghes or ghae or ghec %} +Alpha + {% ifversion fpt or ghec %} + Bravo + {% ifversion ghae %} + Charlie + {% endif %} + {% else %} + Delta + {% endif %} +{% endif %} + +
+ diff --git a/tests/meta/repository-references.js b/tests/meta/repository-references.js index 822a2c0c8e..b70eeede18 100644 --- a/tests/meta/repository-references.js +++ b/tests/meta/repository-references.js @@ -11,7 +11,7 @@ If this test is failing... (1) edit the file to remove the reference; or (2) the repository is public, add the repository name to PUBLIC_REPOS; or -(3) the feature references a docs repository, +(3) the file references a docs repository, add the file name to ALLOW_DOCS_PATHS. */ @@ -132,7 +132,15 @@ describe('check if a GitHub-owned private repository is referenced', () => { }) expect( matches, - `Please edit ${filename} to remove references to ${matches.join(', ')}` + `This test exists to make sure we don't reference private GitHub owned repositories in our open-source repository. + + In '${filename}' we found references to these private repositories: ${matches.join(', ')} + + You can: + + (1) edit the file to remove the repository reference; or + (2) if the repository is public, add the repository name to the 'PUBLIC_REPOS' variable in this test file; or + (3) if the file references a docs repository, add the file name to the 'ALLOW_DOCS_PATHS' variable in this test file.` ).toHaveLength(0) }) }) diff --git a/tests/rendering/breadcrumbs.js b/tests/rendering/breadcrumbs.js index 363416717f..588138efcf 100644 --- a/tests/rendering/breadcrumbs.js +++ b/tests/rendering/breadcrumbs.js @@ -17,7 +17,7 @@ describe('breadcrumbs', () => { test('article pages have breadcrumbs with product, category, maptopic, and article', async () => { const $ = await getDOM( - '/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account' + '/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account' ) const $breadcrumbs = $('[data-testid=breadcrumbs] a') @@ -30,7 +30,7 @@ describe('breadcrumbs', () => { test('maptopic pages include their own grayed-out breadcrumb', async () => { const $ = await getDOM( - '/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences' + '/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences' ) const $breadcrumbs = $('[data-testid=breadcrumbs] a') @@ -43,7 +43,7 @@ describe('breadcrumbs', () => { test('works for enterprise user pages', async () => { const $ = await getDOM( - '/en/enterprise-server/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account' + '/en/enterprise-server/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account' ) const $breadcrumbs = $('[data-testid=breadcrumbs] a') expect($breadcrumbs).toHaveLength(8) @@ -149,7 +149,7 @@ describe('breadcrumbs', () => { test('works on maptopic pages', async () => { const breadcrumbs = await getJSON( - '/en/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings?json=breadcrumbs' + '/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings?json=breadcrumbs' ) const expected = [ { @@ -157,11 +157,11 @@ describe('breadcrumbs', () => { title: 'Account and profile', }, { - href: '/en/account-and-profile/setting-up-and-managing-your-github-user-account', + href: '/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github', title: 'Personal accounts', }, { - href: '/en/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings', + href: '/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings', title: 'Personal account settings', }, ] @@ -170,7 +170,7 @@ describe('breadcrumbs', () => { test('works on articles that DO have maptopics ', async () => { const breadcrumbs = await getJSON( - '/en/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard?json=breadcrumbs' + '/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard?json=breadcrumbs' ) const expected = [ { @@ -178,15 +178,15 @@ describe('breadcrumbs', () => { title: 'Account and profile', }, { - href: '/en/account-and-profile/setting-up-and-managing-your-github-user-account', + href: '/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github', title: 'Personal accounts', }, { - href: '/en/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings', + href: '/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings', title: 'Personal account settings', }, { - href: '/en/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard', + href: '/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard', title: 'Your personal dashboard', }, ] diff --git a/tests/rendering/rest.js b/tests/rendering/rest.js index 4143490242..559d38f36b 100644 --- a/tests/rendering/rest.js +++ b/tests/rendering/rest.js @@ -78,6 +78,6 @@ function formatErrors(differences) { } } errorMessage += - 'This means the categories and subcategories in the content/rest directory do not match the decorated files in lib/static/decorated directory from the OpenAPI schema. Please run ./script/rest/update-files.js --decorated-only and push up the file changes with your updates.\n' + 'If you have made changes to the categories or subcategories in the content/rest directory, either in the frontmatter or the structure of the directory, you will need to ensure that it matches the operations in the OpenAPI description. For example, if an operation is available in GHAE, the frontmatter versioning in the relevant docs category and subcategory files also need to be versioned for GHAE. If you are adding category or subcategory files to the content/rest directory, the OpenAPI dereferenced files must have at least one operation that will be shown for the versions in the category or subcategory files. If this is the case, it is likely that the description files have not been updated from github/github yet. Please contact #docs-engineering or #docs-apis-and-events if you need help.\n' return errorMessage } diff --git a/tests/unit/get-theme.js b/tests/unit/get-theme.js new file mode 100644 index 0000000000..aba0a20bcb --- /dev/null +++ b/tests/unit/get-theme.js @@ -0,0 +1,80 @@ +import { describe, expect, test } from '@jest/globals' + +import { getTheme, defaultCSSTheme, defaultComponentTheme } from '../../lib/get-theme.js' + +function serializeCookieValue(obj) { + return encodeURIComponent(JSON.stringify(obj)) +} + +describe('getTheme basics', () => { + test('always return an object with certain keys', () => { + const req = {} // doesn't even have a `.cookies`. + const theme = getTheme(req) + expect(theme.colorMode).toBe(defaultComponentTheme.colorMode) + expect(theme.nightTheme).toBe(defaultComponentTheme.nightTheme) + expect(theme.dayTheme).toBe(defaultComponentTheme.dayTheme) + const cssTheme = getTheme(req, true) + expect(cssTheme.colorMode).toBe(defaultCSSTheme.colorMode) + expect(cssTheme.nightTheme).toBe(defaultCSSTheme.nightTheme) + expect(cssTheme.dayTheme).toBe(defaultCSSTheme.dayTheme) + }) + + test('respect the color_mode cookie value', () => { + const req = { + cookies: { + color_mode: serializeCookieValue({ + color_mode: 'dark', + light_theme: { name: 'light_colorblind', color_mode: 'light' }, + dark_theme: { name: 'dark_tritanopia', color_mode: 'dark' }, + }), + }, + } + const theme = getTheme(req) + expect(theme.colorMode).toBe('night') + expect(theme.nightTheme).toBe(defaultComponentTheme.nightTheme) + expect(theme.dayTheme).toBe(defaultComponentTheme.dayTheme) + + const cssTheme = getTheme(req, true) + expect(cssTheme.colorMode).toBe('dark') + expect(cssTheme.nightTheme).toBe(defaultCSSTheme.nightTheme) + expect(cssTheme.dayTheme).toBe(defaultCSSTheme.dayTheme) + }) + + test('respect the color_mode cookie value', () => { + const req = { + cookies: { + color_mode: serializeCookieValue({ + color_mode: 'dark', + light_theme: { name: 'light_colorblind', color_mode: 'light' }, + dark_theme: { name: 'dark_tritanopia', color_mode: 'dark' }, + }), + }, + } + const theme = getTheme(req) + expect(theme.colorMode).toBe('night') + expect(theme.nightTheme).toBe(defaultComponentTheme.nightTheme) + expect(theme.dayTheme).toBe(defaultComponentTheme.dayTheme) + + const cssTheme = getTheme(req, true) + expect(cssTheme.colorMode).toBe('dark') + expect(cssTheme.nightTheme).toBe(defaultCSSTheme.nightTheme) + expect(cssTheme.dayTheme).toBe(defaultCSSTheme.dayTheme) + }) + + test('ignore "junk" cookie values', () => { + const req = { + cookies: { + color_mode: '[This is not valid JSON}', + }, + } + const theme = getTheme(req) + expect(theme.colorMode).toBe('auto') + expect(theme.nightTheme).toBe(defaultComponentTheme.nightTheme) + expect(theme.dayTheme).toBe(defaultComponentTheme.dayTheme) + + const cssTheme = getTheme(req, true) + expect(cssTheme.colorMode).toBe('auto') + expect(cssTheme.nightTheme).toBe(defaultCSSTheme.nightTheme) + expect(cssTheme.dayTheme).toBe(defaultCSSTheme.dayTheme) + }) +}) diff --git a/translations/es-ES/content/account-and-profile/index.md b/translations/es-ES/content/account-and-profile/index.md index 046187445d..39550da7b8 100644 --- a/translations/es-ES/content/account-and-profile/index.md +++ b/translations/es-ES/content/account-and-profile/index.md @@ -37,7 +37,7 @@ topics: - Profiles - Notifications children: - - /setting-up-and-managing-your-github-user-account + - /setting-up-and-managing-your-personal-account-on-github - /setting-up-and-managing-your-github-profile - /managing-subscriptions-and-notifications-on-github --- diff --git a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md index 8bf7e159fe..9f48a72b7c 100644 --- a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md @@ -129,8 +129,8 @@ Email notifications from {% data variables.product.product_location %} contain t | --- | --- | | `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. | | `To` field | This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} | -| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
  • `assign`: You were assigned to an issue or pull request.
  • `author`: You created an issue or pull request.
  • `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
  • `comment`: You commented on an issue or pull request.
  • `manual`: There was an update to an issue or pull request you manually subscribed to.
  • `mention`: You were mentioned on an issue or pull request.
  • `push`: Someone committed to a pull request you're subscribed to.
  • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
    • {% endif %}
  • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
  • `subscribed`: There was an update in a repository you're watching.
  • `team_mention`: A team you belong to was mentioned on an issue or pull request.
  • `your_activity`: You opened, commented on, or closed an issue or pull request.
| -| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
  • `assign`: You were assigned to an issue or pull request.
  • `author`: You created an issue or pull request.
  • `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
  • `comment`: You commented on an issue or pull request.
  • `manual`: There was an update to an issue or pull request you manually subscribed to.
  • `mention`: You were mentioned on an issue or pull request.
  • `push`: Someone committed to a pull request you're subscribed to.
  • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • {% ifversion fpt or ghes or ghae or ghec %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
    • {% endif %}
  • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
  • `subscribed`: There was an update in a repository you're watching.
  • `team_mention`: A team you belong to was mentioned on an issue or pull request.
  • `your_activity`: You opened, commented on, or closed an issue or pull request.
| +| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae or ghec %} | `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
  • `low`
  • `moderate`
  • `high`
  • `critical`
For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %} ## Choosing your notification settings @@ -139,7 +139,7 @@ Email notifications from {% data variables.product.product_location %} contain t {% data reusables.notifications-v2.manage-notifications %} 3. On the notifications settings page, choose how you receive notifications when: - There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)." - - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} + - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae or ghec %} - There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% endif %} {% ifversion fpt or ghec %} - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5668 %} - There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."{% endif %} @@ -194,7 +194,7 @@ If you are a member of more than one organization, you can configure each one to 5. Select one of your verified email addresses, then click **Save**. ![Switching your per-org email address](/assets/images/help/notifications/notifications_switching_org_email.gif) -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## {% data variables.product.prodname_dependabot_alerts %} notification options {% data reusables.notifications.vulnerable-dependency-notification-enable %} diff --git a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md index bac654275e..7f2de60a8c 100644 --- a/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md +++ b/translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md @@ -112,13 +112,13 @@ To filter notifications for specific activity on {% data variables.product.produ - `is:gist` - `is:issue-or-pull-request` - `is:release` -- `is:repository-invitation`{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +- `is:repository-invitation`{% ifversion fpt or ghes or ghae or ghec %} - `is:repository-vulnerability-alert`{% endif %}{% ifversion fpt or ghec %} - `is:repository-advisory`{% endif %} - `is:team-discussion`{% ifversion fpt or ghec %} - `is:discussion`{% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." {% endif %} @@ -142,7 +142,7 @@ To filter notifications by why you've received an update, you can use the `reaso | `reason:invitation` | When you're invited to a team, organization, or repository. | `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to. | `reason:mention` | You were directly @mentioned. -| `reason:review-requested` | You or a team you're on have been requested to review a pull request.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| `reason:review-requested` | You or a team you're on have been requested to review a pull request.{% ifversion fpt or ghes or ghae or ghec %} | `reason:security-alert` | When a security alert is issued for a repository.{% endif %} | `reason:state-change` | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged. | `reason:team-mention` | When a team you're a member of is @mentioned. @@ -161,7 +161,7 @@ For example, to see notifications from the octo-org organization, use `org:octo- {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## {% data variables.product.prodname_dependabot %} custom filters {% ifversion fpt or ghec or ghes > 3.2 %} @@ -173,7 +173,7 @@ If you use {% data variables.product.prodname_dependabot %} to keep your depende For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." {% endif %} -{% ifversion ghes < 3.3 or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae %} If you use {% data variables.product.prodname_dependabot %} to tell you about vulnerable dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}: - `is:repository_vulnerability_alert` diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md index b85d7de8b2..49c2dda126 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md @@ -92,10 +92,7 @@ La sección de actividad de contribuciones incluye una cronología detallada de ![Filtro de tiempo de actividad de contribuciones](/assets/images/help/profile/contributions_activity_time_filter.png) -{% ifversion fpt or ghes or ghae or ghec %} - ## Ver contribuciones de {% data variables.product.prodname_enterprise %} en {% data variables.product.prodname_dotcom_the_website %} Si utilizas {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} o {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} y tu propietario de empresa habilita las {% data variables.product.prodname_unified_contributions %}, puedes enviar los conteos de contribución de empresa desde tu perfil de {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Enviar contribuciones empresariales a tu perfil de {% data variables.product.prodname_dotcom_the_website %}](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)". -{% endif %} diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md deleted file mode 100644 index f5591683eb..0000000000 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -title: Deleting your user account -intro: 'You can delete your personal account on {% data variables.product.product_name %} at any time.' -redirect_from: - - /articles/deleting-a-user-account - - /articles/deleting-your-user-account - - /github/setting-up-and-managing-your-github-user-account/deleting-your-user-account - - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account -versions: - fpt: '*' - ghes: '*' - ghec: '*' -topics: - - Accounts -shortTitle: Delete your personal account ---- -Deleting your personal account removes all repositories, forks of private repositories, wikis, issues, pull requests, and pages owned by your account. {% ifversion fpt or ghec %} Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted - instead, they'll be associated with our [Ghost user](https://github.com/ghost).{% else %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted.{% endif %} - -{% ifversion fpt or ghec %} When you delete your account we stop billing you. The email address associated with the account becomes available for use with a different account on {% data variables.product.product_location %}. After 90 days, the account name also becomes available to anyone else to use on a new account. {% endif %} - -If you’re the only owner of an organization, you must transfer ownership to another person or delete the organization before you can delete your personal account. If there are other owners in the organization, you must remove yourself from the organization before you can delete your personal account. - -For more information, see: -- "[Transferring organization ownership](/articles/transferring-organization-ownership)" -- "[Deleting an organization account](/articles/deleting-an-organization-account)" -- "[Removing yourself from an organization](/articles/removing-yourself-from-an-organization/)" - -## Back up your account data - -Before you delete your personal account, make a copy of all repositories, private forks, wikis, issues, and pull requests owned by your account. - -{% warning %} - -**Warning:** Once your personal account has been deleted, GitHub cannot restore your content. - -{% endwarning %} - -## Delete your personal account - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.account_settings %} -3. At the bottom of the Account Settings page, under "Delete account", click **Delete your account**. Before you can delete your personal account: - - If you're the only owner in the organization, you must transfer ownership to another person or delete your organization. - - If there are other organization owners in the organization, you must remove yourself from the organization. - ![Account deletion button](/assets/images/help/settings/settings-account-delete.png) -4. In the "Make sure you want to do this" dialog box, complete the steps to confirm you understand what happens when your account is deleted: - ![Delete account confirmation dialog](/assets/images/help/settings/settings-account-deleteconfirm.png) - {% ifversion fpt or ghec %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and {% data variables.product.prodname_pages %} sites owned by your account will be deleted and your billing will end immediately, and your username will be available to anyone for use on {% data variables.product.product_name %} after 90 days. - {% else %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and pages owned by your account will be deleted, and your username will be available for use on {% data variables.product.product_name %}. - {% endif %}- In the first field, type your {% data variables.product.product_name %} username or email. - - In the second field, type the phrase from the prompt. diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md deleted file mode 100644 index b64c8c5285..0000000000 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Managing security and analysis settings for your user account -intro: 'You can control features that secure and analyze the code in your projects on {% data variables.product.prodname_dotcom %}.' -versions: - fpt: '*' - ghec: '*' - ghes: '>3.2' -topics: - - Accounts -redirect_from: - - /github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account - - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account -shortTitle: Manage security & analysis ---- -## About management of security and analysis settings - -{% data variables.product.prodname_dotcom %} can help secure your repositories. This topic tells you how you can manage the security and analysis features for all your existing or new repositories. - -You can still manage the security and analysis features for individual repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." - -You can also review the security log for all activity on your personal account. For more information, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)." - -{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} - -{% data reusables.security.security-and-analysis-features-enable-read-only %} - -For an overview of repository-level security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)." - -## Enabling or disabling features for existing repositories - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.security-analysis %} -3. Under "Code security and analysis", to the right of the feature, click **Disable all** or **Enable all**. - {% ifversion ghes > 3.2 %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/settings/security-and-analysis-disable-or-enable-all.png){% else %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png){% endif %} -6. Optionally, enable the feature by default for new repositories that you own. - {% ifversion ghes > 3.2 %}!["Enable by default" option for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-by-default-in-modal.png){% else %}!["Enable by default" option for new repositories](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png){% endif %} -7. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories you own. - {% ifversion ghes > 3.2 %}![Button to disable or enable feature](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-dependency-graph.png){% else %}![Button to disable or enable feature](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png){% endif %} - -{% data reusables.security.displayed-information %} - -## Enabling or disabling features for new repositories - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.security-analysis %} -3. Under "Code security and analysis", to the right of the feature, enable or disable the feature by default for new repositories that you own. - {% ifversion ghes > 3.2 %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% else %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %} - -## Further reading - -- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" -- "[Keeping your dependencies updated automatically](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)" diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md deleted file mode 100644 index 17103b8a96..0000000000 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -title: Managing your tab size rendering preference -intro: You can manage the number of spaces a tab is equal to for your personal account. -versions: - fpt: '*' - ghae: issue-5083 - ghes: '>=3.4' - ghec: '*' -topics: - - Accounts -shortTitle: Managing your tab size ---- - -If you feel that tabbed indentation in code rendered on {% data variables.product.product_name %} takes up too much, or too little space, you can change this in your settings. - -{% data reusables.user-settings.access_settings %} -1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**. -2. Under "Tab size preference", select the drop-down menu and choose your preference. - ![Tab size preference button](/assets/images/help/settings/tab-size-preference.png ) diff --git a/translations/es-ES/content/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 deleted file mode 100644 index 4a21753a14..0000000000 --- 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 +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Managing your theme settings -intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.' -versions: - fpt: '*' - ghae: '*' - ghes: '>=3.2' - ghec: '*' -topics: - - Accounts -redirect_from: - - /github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings - - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings -shortTitle: Manage theme settings ---- - -For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings. - -You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks. - -{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes. - -{% endif %} - -{% data reusables.user-settings.access_settings %} -{% data reusables.user-settings.appearance-settings %} - -1. Under "Theme mode", select the drop-down menu, then click a theme preference. - - ![Drop-down menu under "Theme mode" for selection of theme preference](/assets/images/help/settings/theme-mode-drop-down-menu.png) -1. Click the theme you'd like to use. - - If you chose a single theme, click a theme. - - {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} - - If you chose to follow your system settings, click a day theme and a night theme. - - {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} - {% ifversion fpt or ghec %} - - If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %} - -{% if command-palette %} - -{% note %} - -**Note:** You can also change your theme settings with the command palette. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)". - -{% endnote %} - -{% endif %} - -## Further reading - -- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md deleted file mode 100644 index ebfa80dd2b..0000000000 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: Merging multiple user accounts -intro: 'If you have separate accounts for work and personal use, you can merge the accounts.' -redirect_from: - - /articles/can-i-merge-two-accounts - - /articles/keeping-work-and-personal-repositories-separate - - /articles/merging-multiple-user-accounts - - /github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts - - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts -versions: - fpt: '*' - ghec: '*' -topics: - - Accounts -shortTitle: Merge multiple personal accounts ---- -{% tip %} - -{% ifversion ghec %} - -**Tip:** {% data variables.product.prodname_emus %} allow an enterprise to provision unique personal accounts for its members through an identity provider (IdP). For more information, see "[About Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)." For other use cases, we recommend using only one personal account to manage both personal and professional repositories. - -{% else %} - -**Tip:** We recommend using only one personal account to manage both personal and professional repositories. - -{% endif %} - -{% endtip %} - -{% warning %} - -**Warning:** -- Organization and repository access permissions aren't transferable between accounts. If the account you want to delete has an existing access permission, an organization owner or repository administrator will need to invite the account that you want to keep. -- Any commits authored with a GitHub-provided `noreply` email address cannot be transferred from one account to another. If the account you want to delete used the **Keep my email address private** option, it won't be possible to transfer the commits authored by the account you are deleting to the account you want to keep. - -{% endwarning %} - -1. [Transfer any repositories](/articles/how-to-transfer-a-repository) from the account you want to delete to the account you want to keep. Issues, pull requests, and wikis are transferred as well. Verify the repositories exist on the account you want to keep. -2. [Update the remote URLs](/github/getting-started-with-github/managing-remote-repositories) in any local clones of the repositories that were moved. -3. [Delete the account](/articles/deleting-your-user-account) you no longer want to use. -4. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. For more information, see "[Why are my contributions not showing up on my profile?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)" - -## Further reading - -- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)" diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md similarity index 50% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md index 16980d4711..cdc8f7a80c 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md @@ -1,10 +1,11 @@ --- -title: Configurar y administrar tu cuenta de usuario de GitHub -intro: 'Puedes administrar los ajustes en tu cuenta personal de GitHub, incluyendo las preferencias de correo electrónico, acceso de colaborador para los repositorios personales y membrecías de organización.' +title: Setting up and managing your personal account on GitHub +intro: 'You can manage settings for your personal account on {% data variables.product.prodname_dotcom %}, including email preferences, collaborator access for personal repositories, and organization memberships.' shortTitle: Cuentas personales redirect_from: - /categories/setting-up-and-managing-your-github-user-account - /github/setting-up-and-managing-your-github-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account versions: fpt: '*' ghes: '*' @@ -13,7 +14,7 @@ versions: topics: - Accounts children: - - /managing-user-account-settings + - /managing-personal-account-settings - /managing-email-preferences - /managing-access-to-your-personal-repositories - /managing-your-membership-in-organizations diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md similarity index 80% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md index 32c2a7ebf3..21488e2171 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md @@ -6,6 +6,7 @@ redirect_from: - /categories/managing-repository-collaborators - /articles/managing-access-to-your-personal-repositories - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' @@ -19,7 +20,7 @@ children: - /inviting-collaborators-to-a-personal-repository - /removing-a-collaborator-from-a-personal-repository - /removing-yourself-from-a-collaborators-repository - - /maintaining-ownership-continuity-of-your-user-accounts-repositories + - /maintaining-ownership-continuity-of-your-personal-accounts-repositories shortTitle: Acceder a tus repositorios --- 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-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md similarity index 88% rename from 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 rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index a8a37f47ae..fe7cc0db1f 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-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md @@ -7,6 +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 + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' @@ -41,7 +42,7 @@ Si eres un miembro de una {% data variables.product.prodname_emu_enterprise %}, {% 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) +2. Comienza a teclear el nombre de la persona que deseas invitar dentro del campo de búsqueda. Posteriormente, da clic en algún nombre de la lista de coincidencias. ![Campo de búsqueda para teclear el nombre de una persona que se desea invitar al repositorio](/assets/images/help/repository/manage-access-invite-search-field-user.png) 3. Da clic en **Añadir NOMBRE a REPOSITORIO**. ![Botón para añadir un colaborador](/assets/images/help/repository/add-collaborator-user-repo.png) {% else %} 5. En la barra lateral izquierda, haz clic en **Collaborators** (Colaboradores). ![Barra lateral de configuraciones del repositorio con Colaboradores resaltados](/assets/images/help/repository/user-account-repo-settings-collaborators.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/maintaining-ownership-continuity-of-your-user-accounts-repositories.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md similarity index 90% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md index 65f90b1864..28e3422677 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md @@ -1,5 +1,5 @@ --- -title: Mantener la continuidad de la propiedad para los repositorios de tu cuenta de usuario +title: Maintaining ownership continuity of your personal account's repositories intro: Puedes invitar a alguien para administrar los repositorios que pertenezcan a tu usuario si no puedes hacerlo tú mismo. versions: fpt: '*' @@ -10,6 +10,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories shortTitle: Continuidad de la propiedad --- 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md similarity index 93% rename from 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 rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md index 9c9e625b8d..2d8a7e028f 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md @@ -10,6 +10,7 @@ redirect_from: - /articles/removing-a-collaborator-from-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md similarity index 90% rename from 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 rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md index 1aa1a0f56d..64e52af36e 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md @@ -9,6 +9,7 @@ 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 + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md similarity index 92% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md index 832bdeefe3..72eac50226 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -5,6 +5,7 @@ redirect_from: - /articles/adding-an-email-address-to-your-github-account - /github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md similarity index 92% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md index 9450eb3349..8d7a3bc12c 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/blocking-command-line-pushes-that-expose-your-personal-email-address - /github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address versions: fpt: '*' ghec: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md similarity index 94% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md index 47d1b3c9eb..9cacd48868 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/changing-your-primary-email-address - /github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md similarity index 91% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md index 8fac88cdd1..c09a131b72 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md @@ -5,6 +5,7 @@ redirect_from: - /categories/managing-email-preferences - /articles/managing-email-preferences - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md similarity index 94% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md index 10a1e7d68c..8c1d696415 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md @@ -5,6 +5,7 @@ redirect_from: - /articles/managing-marketing-emails-from-github - /github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github versions: fpt: '*' ghec: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md similarity index 96% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md index 249d9dedfb..1833038f6c 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md @@ -7,6 +7,7 @@ redirect_from: - /articles/remembering-your-github-username-or-email - /github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md similarity index 91% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md index 71f8c0eebd..264d8bf42a 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/setting-a-backup-email-address - /github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md similarity index 98% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md index db776e496b..cb9947c6a9 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md @@ -12,6 +12,7 @@ redirect_from: - /articles/setting-your-commit-email-address - /github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md similarity index 96% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md index 1dd216b4ad..cefe2170ad 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md @@ -5,6 +5,7 @@ redirect_from: - /articles/types-of-emails-github-sends - /github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends versions: fpt: '*' ghec: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md similarity index 97% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md index c97ce571f9..cc84eec54a 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md @@ -6,6 +6,7 @@ redirect_from: - /articles/about-your-personal-dashboard - /github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard intro: 'Puedes visitar tu tablero personal para hacer un seguimiento de las propuestas y las solicitudes de extracción que estás siguiendo o en las que estás trabajando, navegar hacia las páginas de equipo y tus repositorios principales, estar actualizado sobres las actividadess recientes en las organizaciones y los repositorios en los que estás suscripto y explorar los repositorios recomendados.' versions: fpt: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md similarity index 95% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md index 9de74af74b..309d58733f 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md @@ -5,6 +5,7 @@ redirect_from: - /articles/best-practices-for-leaving-your-company - /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company versions: fpt: '*' ghec: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md new file mode 100644 index 0000000000..c98edc1f07 --- /dev/null +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md @@ -0,0 +1,89 @@ +--- +title: Cambiar tu nombre de usuario de GitHub +intro: 'Puedes cambiar el nombre de usuario de tu cuenta en {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %} si tu instancia utiliza la autenticación integrada{% endif %}.' +redirect_from: + - /articles/how-to-change-your-username + - /articles/changing-your-github-user-name + - /articles/renaming-a-user + - /articles/what-happens-when-i-change-my-username + - /articles/changing-your-github-username + - /github/setting-up-and-managing-your-github-user-account/changing-your-github-username + - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username +versions: + fpt: '*' + ghes: '*' + ghec: '*' +topics: + - Accounts +shortTitle: Cambiar tu nombre de usuario +--- + +{% ifversion ghec or ghes %} + +{% note %} + +{% ifversion ghec %} + +**Nota**: Los miembros de una {% data variables.product.prodname_emu_enterprise %} no pueden cambiar nombres de usuario. El administrador del IdP de tu empresa controla tu nombre de usuario para {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". + +{% elsif ghes %} + +**Nota**: Si inicias sesión en {% data variables.product.product_location %} con credenciales de LDAP o inicio de sesión único (SSO), solo tu administrador local podrá cambiar tu nombre de usuario. Para obtener más información acerca de los métodos de autenticación para {% data variables.product.product_name %}, consulta la sección "[Autenticación de usuarios para {% data variables.product.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)". + +{% endif %} + +{% endnote %} + +{% endif %} + +## Acerca de los cambios de nombre de usuario + +Puedes cambiar tu nombre de usuario a otro que no esté en uso actualmente.{% ifversion fpt or ghec %} si el nombre de usuario que quieres no está disponible, considera otros nombres o variaciones únicas. El utilizar un número, guion o una ortografía alternativa podría ayudarte a encontrar un nombre de usuario similar que esté disponible. + +Si tienes una marca comercial para el nombre de usuario, puedes encontrar más información sobre cómo hacer un reclamo de una marca comercial en nuestra página de [Política de Marcas Comerciales](/free-pro-team@latest/github/site-policy/github-trademark-policy). + +Si no tienes una marca comercial para el nombre, puedes elegir otro nombre de usuario o mantener el actual. {% data variables.contact.github_support %} no puede publicar el nombre de usuario que no está disponible para ti. Para obtener más información, consulta "[Cambiar tu nombre de usuario](#changing-your-username)".{% endif %} + +Una vez que cambies tu nombre de usuario, el nombre de usuario anterior estará disponible para todas las personas que lo reclamen. La mayoría de las referencias a tus repositorios con el nombre de usuario anterior automáticamente cambian al nombre de usuario nuevo. Sin embargo, algunos enlaces a tu perfil no se redirigirán automáticamente. + +{% data variables.product.product_name %} no puede configurar redirecciones para: +- [@menciones](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) con tu nombre de usuario anterior +- Enlaces a los [gists](/articles/creating-gists) que incluyen tu nombre de usuario anterior + +{% ifversion fpt or ghec %} + +Si eres un miembro de una {% data variables.product.prodname_emu_enterprise %}, no puedes hacer cambios a tu nombre de usuario. {% data reusables.enterprise-accounts.emu-more-info-account %} + +{% endif %} + +## Referencias del repositorio + +Después de cambiar tu nombre de usuario, {% data variables.product.product_name %} automáticamente redirigirá las referencias a tus repositorios. +- Los enlaces web a tus repositorios existentes seguirán funcionando. Esto puede tardar algunos minutos en completarse después de realizar el cambio. +- Las inserciones de la línea de comando desde tus clones de repositorio local hasta las URL del registro remoto anterior seguirán funcionando. + +Si el nuevo propietario de tu nombre de usuario anterior crea un repositorio con el mismo nombre que tu repositorio, se sobrescribirá el registro de redirección y tu redirección dejará de funcionar. Debido a esta posibilidad, recomendamos que actualices todas las URL de repositorios remotos existentes luego de cambiar tu nombre de usuario. Para obtener más información, consulta "[Administrar repositorios remotos](/github/getting-started-with-github/managing-remote-repositories)." + +## Enlaces a tu página de perfil anterior + +Luego de cambiar tu nombre de usuario, los enlaces a tu página de perfil anterior, como `https://{% data variables.command_line.backticks %}/previoususername`, arrojarán un error 404. Te recomendamos actualizar cualquier enlace a tu cuenta en {% data variables.product.product_location %} desde cualquier otra parte{% ifversion fpt or ghec %}, tal como tu perfil de LinkedIn o Twitter{% endif %}. + +## Tus confirmaciones Git + +{% ifversion fpt or ghec %}Las confirmaciones de Git que se asociaron con tun dirección de correo electrónico de tipo `noreply` que proporcionó {% data variables.product.product_name %} no se atribuirán a tu nombre de usuario nuevo y no aparecerán en tu gráfica de contribuciones.{% endif %} si tus confirmaciones de Git se asociaron con otra dirección de correo electrónico que hayas [agregado a tu cuenta de GitHub](/articles/adding-an-email-address-to-your-github-account),{% ifversion fpt or ghec %}incluyendo la dirección de correo electrónico de tipo `noreply` basada en tu ID, la cual proporcionó {% data variables.product.product_name %},{% endif %} se te seguirán atribuyendo y aparecerán en tu gráfica de contribuciones después de que hayas cambiado tu nombre de usuario. Para obtener más información sobre cómo establecer tu dirección de correo electrónico, consulta "[Establecer tu dirección de correo electrónico de confirmación](/articles/setting-your-commit-email-address)". + +## Cambiar tu nombre de usuario + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.account_settings %} +3. In the "Change username" section, click **Change username**. ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %} +4. Lee las advertencias sobre cómo cambiar tu nombre de usuario. If you still want to change your username, click **I understand, let's change my username**. ![Cambiar botón Username warning (Advertencia de nombre de usuario)](/assets/images/help/settings/settings-change-username-warning-button.png) +5. Escribe un nuevo nombre de usuario. ![Campo New username (Nuevo nombre de usuario)](/assets/images/help/settings/settings-change-username-enter-new-username.png) +6. If the username you've chosen is available, click **Change my username**. Si el nombre de usuario que elegiste no está disponible, puedes probar un nombre de usuario diferente o una de las sugerencias que ves. ![Cambiar botón Username warning (Advertencia de nombre de usuario)](/assets/images/help/settings/settings-change-my-username-button.png) +{% endif %} + +## Leer más + +- "[¿Por qué se enlazaron mis confirmaciones con el usuario incorrecto?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"{% ifversion fpt or ghec %} +- "[Política de nombres de usuario de {% data variables.product.prodname_dotcom %}](/free-pro-team@latest/github/site-policy/github-username-policy)"{% endif %} diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md similarity index 97% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md index 3dea4e9b1f..3933b91d1f 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md @@ -6,6 +6,7 @@ redirect_from: - /articles/converting-a-user-into-an-organization - /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization intro: Puedes convertir tu cuenta personal en una organización. Esto permite que haya más permisos granulares para repositorios que pertenecen a la organización. versions: fpt: '*' @@ -52,7 +53,7 @@ También puedes convertir tu cuenta personal directamente en una organización. 6. En el cuadro de diálogo Account Transformation Warning (Advertencia de transformación de la cuenta), revisa y confirma la confirmación. Ten en cuenta que la información en este cuadro es la misma que la advertencia en la parte superior de este artículo. ![Advertencia de conversión](/assets/images/help/organizations/organization-account-transformation-warning.png) 7. En la página "Transform your user into an organization" (Transformar tu usuario en una organización), debajo de "Choose an organization owner" (Elegir un propietario de la organización), elige la cuenta personal secundaria que creaste en la sección anterior u otro usuario en quien confías para administrar la organización. ![Página Add organization owner (Agregar propietario de la organización)](/assets/images/help/organizations/organization-add-owner.png) 8. Escoge la nueva suscripción de la organización y escribe tu información de facturación si se te solicita. -9. Haz clic en **Create Organization** (Crear organización). +9. Click **Create Organization**. 10. Inicia sesión en la cuenta personal nueva que creaste en el paso uno y luego utiliza el alternador de contexto para acceder a tu organización nueva. {% tip %} diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md new file mode 100644 index 0000000000..23d646bd21 --- /dev/null +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md @@ -0,0 +1,51 @@ +--- +title: Deleting your personal account +intro: 'Puedes borrar tu cuenta personal de {% data variables.product.product_name %} en cualquier momento.' +redirect_from: + - /articles/deleting-a-user-account + - /articles/deleting-your-user-account + - /github/setting-up-and-managing-your-github-user-account/deleting-your-user-account + - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account +versions: + fpt: '*' + ghes: '*' + ghec: '*' +topics: + - Accounts +shortTitle: Borrar tu cuenta personal +--- + +El borrar tu cuenta personal elimina todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de cambios y páginas que pertenecen a tu cuenta. {% ifversion fpt or ghec %}No se eliminarán las propuestas ni las solicitudes de extracción que hayas creado ni los comentarios que hayas hecho en repositorios que sean propiedad de otros usuarios. En lugar de eliminarlos, se los asociará con nuestro [Usuario fantasma](https://github.com/ghost).{% else %}No se eliminarán las propuestas ni las solicitudes de extracción que hayas creado ni los comentarios que hayas hecho en repositorios que sean propiedad de otros usuarios.{% endif %} + +{% ifversion fpt or ghec %} Dejaremos de cobrarte cuando borras tu cuenta. La dirección asociada con la cuenta se hace disponible para utilizarse con una cuenta diferente en {% data variables.product.product_location %}. Después de 90 días, el nombre de cuenta también pone disponible para que cualquiera con una cuenta nueva lo utilice. {% endif %} + +Si eres el único propietario de una organización, deberás transferir la propiedad a otra persona o borrar la organización antes de que puedas borrar tu cuenta personal. Si existen otros propietarios en la organización, debes eliminarte de ella antes de que puedas borrar tu cuenta personal. + +Para obtener más información, consulta: +- "[Transferir la propiedad de la organización](/articles/transferring-organization-ownership)" +- "[Eliminar una cuenta de la organización](/articles/deleting-an-organization-account)" +- "[Eliminarte de una organización](/articles/removing-yourself-from-an-organization/)" + +## Copias de seguridad de los datos de tu cuenta + +Antes de que borres tu cuenta personal, haz una copia de todos los repositorios, bifurcaciones privadas, wikis, propuestas y solicitudes de cambios que le pertenezcan a tu cuenta. + +{% warning %} + +**Advertencia** Una vez que tu cuenta personal se haya borrado, GitHub no podrá restablecer tu contenido. + +{% endwarning %} + +## Borrar tu cuenta personal + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.account_settings %} +3. En la parte inferior de la página de configuración de la cuenta, en "Eliminar cuenta", haz clic en **Eliminar tu cuenta**. Antes de que puedas borrar tu cuenta personal: + - Si eres el único propietario de la organización, debes transferir la propiedad a otra persona o eliminar tu organización. + - Si hay otros propietarios de la organización dentro de la organización, debes eliminarte de la organización. ![Botón Eliminación de cuenta](/assets/images/help/settings/settings-account-delete.png) +4. En el cuadro de diálogo "Make sure you want to do this" (Asegúrate de que quieres hacer esto), realiza los siguientes pasos para confirmar que comprendes lo que sucede cuando se elimina tu cuenta: ![Diálogo de confirmación para eliminar cuenta](/assets/images/help/settings/settings-account-deleteconfirm.png) + {% ifversion fpt or ghec %}- Recuerda que todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de cambios y sitios de {% data variables.product.prodname_pages %} que le pertenecen a tu cuenta se borrarán y tu facturación terminará de inmediato y tu nombre de usuario se pondrá disponible para que cualquiera lo utilice en {% data variables.product.product_name %} después de 90 días. + {% else %}-Recuerda que se eliminarán todos los repositorios, bifurcaciones de repositorios privados, wikis, propuestas, solicitudes de extracción y páginas que sean propiedad de tu cuenta, y tu nombre de usuario pasará a estar disponible para que cualquier otra persona lo use en {% data variables.product.product_name %}. + {% endif %}- En el primer campo, escribe tu nombre de usuario de {% data variables.product.product_name %} o tu correo electrónico. + - En el segundo campo, escribe la frase que se indica. diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md similarity index 69% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md index 69988070a4..1288b54218 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md @@ -6,6 +6,7 @@ redirect_from: - /categories/user-accounts - /articles/managing-user-account-settings - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings versions: fpt: '*' ghes: '*' @@ -18,15 +19,15 @@ children: - /managing-your-theme-settings - /managing-your-tab-size-rendering-preference - /changing-your-github-username - - /merging-multiple-user-accounts + - /merging-multiple-personal-accounts - /converting-a-user-into-an-organization - - /deleting-your-user-account - - /permission-levels-for-a-user-account-repository - - /permission-levels-for-user-owned-project-boards + - /deleting-your-personal-account + - /permission-levels-for-a-personal-account-repository + - /permission-levels-for-a-project-board-owned-by-a-personal-account - /managing-accessibility-settings - /managing-the-default-branch-name-for-your-repositories - - /managing-security-and-analysis-settings-for-your-user-account - - /managing-access-to-your-user-accounts-project-boards + - /managing-security-and-analysis-settings-for-your-personal-account + - /managing-access-to-your-personal-accounts-project-boards - /integrating-jira-with-your-personal-projects - /best-practices-for-leaving-your-company - /what-does-the-available-for-hire-checkbox-do diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md similarity index 93% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md index 5020f9432d..6a39e89fa3 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md @@ -5,6 +5,7 @@ redirect_from: - /articles/integrating-jira-with-your-personal-projects - /github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects versions: ghes: '*' ghae: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md similarity index 92% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md index bf8eb32851..329cdf59e4 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md @@ -1,5 +1,5 @@ --- -title: Administrar el acceso a los tableros de proyecto de tu cuenta de usuario +title: Managing access to your personal account's project boards intro: 'Como propietario de un tablero de proyecto, puedes agregar o eliminar a un colaborador y personalizar sus permisos a un tablero de proyecto.' redirect_from: - /articles/managing-project-boards-in-your-repository-or-organization @@ -7,6 +7,7 @@ redirect_from: - /articles/managing-access-to-your-user-accounts-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md similarity index 90% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md index e83ba29411..6230ff75ff 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md @@ -3,6 +3,8 @@ title: Administrar los ajustes de accesibilidad intro: 'Puedes inhabilitar las teclas de atajo de {% data variables.product.prodname_dotcom %} en tus ajustes de accesibilidad.' versions: feature: keyboard-shortcut-accessibility-setting +redirect_from: + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings --- ## Acerca de los ajustes de accesibilidad diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md new file mode 100644 index 0000000000..937ae455e6 --- /dev/null +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md @@ -0,0 +1,55 @@ +--- +title: Managing security and analysis settings for your personal account +intro: 'Puedes controlar las características que dan seguridad y analizan tu código en tus proyectos dentro de {% data variables.product.prodname_dotcom %}.' +versions: + fpt: '*' + ghec: '*' + ghes: '>3.2' +topics: + - Accounts +redirect_from: + - /github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account + - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account +shortTitle: Administrar el análisis & seguridad +--- + +## Acerca de la administración de los parámetros de seguridad y análisis + +{% data variables.product.prodname_dotcom %} puede ayudarte a asegurar tus repositorios. Este tema te muestra cómo puedes administrar las características de seguridad y análisis para todos tus repositorios existentes o nuevos. + +Aún puedes administrar las características de seguridad y análisis para los repositorios individuales. Para obtener más información, consulta la sección "[Administrar la configuración de seguridad y análisis para tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)". + +También puedes revisar la bitácora de seguridad para ver toda la actividad de tu cuenta personal. Para obtener más información, consulta "[Revisar tu registro de seguridad](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)". + +{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %} + +{% data reusables.security.security-and-analysis-features-enable-read-only %} + +Para obtener un resumen de la seguridad a nivel de repositorio, consulta la sección "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository)". + +## Habilitar o inhabilitar las características para los repositorios existentes + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.security-analysis %} +3. Debajo de "Análisis y seguridad de código", a la derecha de la característica, haz clic en **Inhabilitar todo** o en **Habilitar todo**. + {% ifversion ghes > 3.2 %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/settings/security-and-analysis-disable-or-enable-all.png){% else %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png){% endif %} +6. Opcionalmente, habilita la característica predeterminada para los repositorios nuevos que te pertenezcan. + {% ifversion ghes > 3.2 %}!["Enable by default" option for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-by-default-in-modal.png){% else %}!["Enable by default" option for new repositories](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png){% endif %} +7. Da clic en **Inhabilitar CARACTERÍSTICA** o **Habilitar CARACTERÍSTICA** para inhabilitar o habilitar la característica para todos los repositorios que te pertenezcan. + {% ifversion ghes > 3.2 %}![Button to disable or enable feature](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-dependency-graph.png){% else %}![Button to disable or enable feature](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png){% endif %} + +{% data reusables.security.displayed-information %} + +## Habilitar o inhabilitar las características para los repositorios nuevos + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.security-analysis %} +3. Debajo de "Análisis y seguridad del código", a la derecha de la característica, habilítala o inhabilítala predeterminadamente para los repositorios nuevos que te pertenezcan. + {% ifversion ghes > 3.2 %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% else %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %} + +## Leer más + +- "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" +- "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" +- "[Mantener tus dependencias actualizacas automáticamente](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)" diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md similarity index 100% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md new file mode 100644 index 0000000000..d81d458903 --- /dev/null +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md @@ -0,0 +1,20 @@ +--- +title: Administrar tu preferencia de representación de tamaño de pestaña +intro: Puedes administrar la cantidad de espacios que iguale la pestaña para tu cuenta personal. +versions: + fpt: '*' + ghae: issue-5083 + ghes: '>=3.4' + ghec: '*' +topics: + - Accounts +shortTitle: Administrar el tamaño de tu pestaña +redirect_from: + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference +--- + +Si crees que la sangría del código que se interpreta en {% data variables.product.product_name %} es demasiado grande o pequeña, puedes cambiar esto en tus ajustes. + +{% data reusables.user-settings.access_settings %} +1. En la barra lateral, haz clic en **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Apariencia**. +2. Debajo de "Preferencia de tamaño de pestaña"; selecciona el menú desplegable y elige tu preferencia. ![Botón de preferencia de tamaño de pestaña](/assets/images/help/settings/tab-size-preference.png) diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md new file mode 100644 index 0000000000..c6f0217eaa --- /dev/null +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md @@ -0,0 +1,54 @@ +--- +title: Administrar la configuración de tu tema +intro: 'Puedes administrar la forma en que {% data variables.product.product_name %} te ve si configuras las preferencias de tema que ya sea siguen la configuración de tu sistema o siempre utilzian un modo claro u oscuro.' +versions: + fpt: '*' + ghae: '*' + ghes: '>=3.2' + ghec: '*' +topics: + - Accounts +redirect_from: + - /github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings + - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings +shortTitle: Administrar la configuración de temas +--- + +Para obtener elecciones y flexibilidad en la forma y momento de utilizar {% data variables.product.product_name %}, puedes configurar los ajustes de tema para cambiar la forma en la que ves a {% data variables.product.product_name %}. Puedes elegir de entre los temas claros u oscuros o puedes configurar a {% data variables.product.product_name %} para que siga la configuración de tu sistema. + +Puede que quieras utilizar un tema oscuro para reducir el consumo de energía en algunos dispositivos, para reducir la fatiga ocular en condiciones de luz baja o porque te gusta más cómo se ve. + +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Si tu visión es limitada, puedes beneficiarte de un tema de contraste alto, con mayor contraste entre los elementos en primer y segundo plano.{% endif %}{% ifversion fpt or ghae or ghec %} Si tienes daltonismo, puedes beneficiarte de nuestros temas claro y oscuro para daltónicos. + +{% endif %} + +{% data reusables.user-settings.access_settings %} +{% data reusables.user-settings.appearance-settings %} + +1. Debajo de "Modo del tema", selecciona el menú desplegable y haz clic en una preferencia de tema. + + ![Menú desplegable debajo de "Modo del tema" para la selección de las preferencias del tema](/assets/images/help/settings/theme-mode-drop-down-menu.png) +1. Haz clic en el tema que quieres usar. + - Si eliges un tema simple, haz clic en un tema. + + {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} + - Si eliges seguir tu configuración de sistema, haz clic en un tema de día y de noche. + + {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} + {% ifversion fpt or ghec %} + - Si te gustaría elegir un tema que se encuentre actualmente en beta público, primero necesitas habilitarlo con la vista previa de características. Para obtener más información, consulta la sección [Explorar los lanzamientos de acceso adelantado con vista previa de características](/get-started/using-github/exploring-early-access-releases-with-feature-preview)".{% endif %} + +{% if command-palette %} + +{% note %} + +**Nota:** También puedes cambiar los ajustes de tu tema con la paleta de comandos. Para obtener más información, consulta la sección "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)". + +{% endnote %} + +{% endif %} + +## Leer más + +- "[Configurar un tema para {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)" diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md new file mode 100644 index 0000000000..e4c08c19a7 --- /dev/null +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md @@ -0,0 +1,48 @@ +--- +title: Merging multiple personal accounts +intro: 'Si tienes cuentas separadas para uso laboral y personal, puedes fusionar las cuentas.' +redirect_from: + - /articles/can-i-merge-two-accounts + - /articles/keeping-work-and-personal-repositories-separate + - /articles/merging-multiple-user-accounts + - /github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts + - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts +versions: + fpt: '*' + ghec: '*' +topics: + - Accounts +shortTitle: Fusionar cuentas personales múltiples +--- + +{% tip %} + +{% ifversion ghec %} + +**Tip:** {% data variables.product.prodname_emus %} permite que una empresa aprovisione cuentas personales únicas para sus miembros mediante un proveedor de identidad (IdP). Para obtener más información, consulta la sección "[Acerca de los Usuarios Empresariales Administrados](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)". Para otros casos de uso, te recomendamos utilizar solo una cuenta personal para administrar los repositorios tanto profesionales como personales. + +{% else %} + +**Tip:** Te recomendamos utilizar solo una cuenta personal para administrar tanto los repositorios profesionales como personales. + +{% endif %} + +{% endtip %} + +{% warning %} + +**Advertencia:** +- No se pueden transferir los permisos a repositorios y organizaciones entre cuentas. Si la cuenta que quieres borrar tiene un permiso de acceso existente, un propietario de organización o administrador de repositorio necesitará invitar a la cuenta que quieras mantener. +- Cualquier confirmación que se haya creado con una dirección de correo electrónico de tipo `no-reply` que haya proporcionado GitHub no se podrá transferir de una cuenta a otra. Si la cuenta que quieres borrar utilizó la opción de **Mantener mi dirección de correo electrónico como privada**, no será posible transferir las confirmaciones que haya creado la cuenta que vas a borrar a la cuenta que vas a mantener. + +{% endwarning %} + +1. [Transfiere cualquier repositorio](/articles/how-to-transfer-a-repository) desde la cuenta que deseas eliminar a la cuenta que deseas mantener. También se transfieren propuestas, solicitudes de extracción y wikis. Verifica que los repositorios existan en la cuenta que deseas mantener. +2. [Actualiza las URL remotas](/github/getting-started-with-github/managing-remote-repositories) en cualquier clon local de los repositorios que se movieron. +3. [Elimina la cuenta](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account) que ya no deseas utilizar. +4. Para atribuir las confirmaciones pasadas a la cuenta nueva, agrega la dirección de correo electrónico que utilizaste para crear dichas confirmaciones a la cuenta que vas a conservar. Para obtener más información, consulta"[¿Por qué mis contribuciones no se muestran en mi perfil?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)" + +## Leer más + +- [Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/articles/types-of-github-accounts)" diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md new file mode 100644 index 0000000000..b0f156e67d --- /dev/null +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md @@ -0,0 +1,99 @@ +--- +title: Permission levels for a personal account repository +intro: 'Un repositorio que pertenece a una cuenta personal y tiene dos niveles de permiso: el propietario del repositorio y los colaboradores.' +redirect_from: + - /articles/permission-levels-for-a-user-account-repository + - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository + - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Accounts +shortTitle: Permisos de repositorio +--- + +## Acerca de los niveles de permisos para un repositorio de una cuenta personal + +Los repositorios que pertenecen a las cuentas personales tienen un propietario. Los permisos de propiedad no pueden compartirse con otra cuenta personal. + +También puedes {% ifversion fpt or ghec %}invitar{% else %}agregar{% endif %} usuarios de {% data variables.product.product_name %} a tu repositorio como colaboradores. Para obtener más información, consulta la sección "[Invitar colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)". + +{% tip %} + +**Tip:** Si necesitas un acceso más granular para un repositorio que le pertenezca a tu cuenta personal, considera transferirlo a una organización. Para obtener más información, consulta "[Transferir un repositorio](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)". + +{% endtip %} + +## Acceso de propietarios a un repositorio que pertenezca a una cuenta personal + +El propietario del repositorio tiene control completo del repositorio. Adicionalmente a las acciones que pudiera realizar cualquier colaborador, el propietario del repositorio puede realizar las siguientes. + +| Acción | Más información | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% ifversion fpt or ghec %}Invitar colaboradores{% else %}Agregar colaboradores{% endif %} | | +| "[Invitar colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | | +| Cambiar la visibilidad del repositorio | "[Configurar la visibilidad del repositorio](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %} +| Limitar las interacciones con el repositorio | "[Limitar las interacciones en tu repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" +{% endif %} +| Renombrar una rama, incluyendo la rama predeterminada | "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)" | +| Fusionar una solicitud de extracción sobre una rama protegida, incluso si no hay revisiones de aprobación | "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)" | +| Eliminar el repositorio | "[Borrar un repositorio](/repositories/creating-and-managing-repositories/deleting-a-repository)" | +| Administrar los temas del repositorio | "[Clasificar tu repositorio con temas](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %} +| Administrar la seguridad y la configuración de análisis del repositorio | "[Administrar la configuración de análisis y seguridad de tu repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %} +| Habilitar la gráfica de dependencias para un repositorio privado | "[Explorar las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.1 or ghec or ghae %} +| Borrar y restablecer paquetes | "[Borrar y restablecer un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)" +{% endif %} +| Personalizar la vista previa de las redes sociales de un repositorio | "[Personalizar la vista previa de las redes sociales de tu repositorio](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | +| Crear una plantilla del repositorio | "[Crear un repositorio de plantilla](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae or ghec %} +| Acceso de control a las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables | "[Administrar la configuración de análisis y seguridad de tu repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %} +| Descartar las {% data variables.product.prodname_dependabot_alerts %} en el repositorio | "[Visualizar las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | +| Administrar el uso de datos para un repositorio privado | "[Administrar la configuración del uso de datos para tu repositorio privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)" +{% endif %} +| Definir propietarios del código para un repositorio | "[Acerca de los propietarios del código](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | +| Archivar el repositorio | "[Archivar repositorios](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %} +| Crear asesorías de seguridad | "[Acerca de las {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | +| Mostrar el botón del patrocinador | "[Mostrar un botón de patrocinador en tu repositorio](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" +{% endif %} +| Permitir o dejar de permitir la fusión automática para las solicitudes de cambios | "[Administrar la fusión automática para las solicitudes de cambios en tu repositorio](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | + +## Acceso de colaborador para un repositorio que pertenezca a una cuenta personal + +Los colaboradores de un repositorio personal pueden extraer (leer) el contienido del mismo y subir (escribir) los cambios al repositorio. + +{% note %} + +**Nota:** en un repositorio privado, los propietarios del repositorio solo pueden otorgar acceso de escritura a los colaboradores. Los colaboradores no pueden tener acceso de solo lectura a los repositorios que pertenezcan a una cuenta personal. + +{% endnote %} + +Los colaboradores también pueden realizar las siguientes acciones. + +| Acción | Más información | +|:-------------------------------------------------------------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Bifurcar el repositorio | "[Acerca de las bifurcaciones](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +| Renombrar una rama diferente a la predeterminada | "[Renombrar una rama](/github/administering-a-repository/renaming-a-branch)" +{% endif %} +| Crear, editar, y borrar comentarios en las confirmaciones, solicitudes de cambios y propuestas del repositorio |
  • "[Acerca de las propuestas](/github/managing-your-work-on-github/about-issues)"
  • "[Comentar en una solicitud de cambios](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"
  • "[Administrar los comentarios perjudiciales](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"
| +| Crear, asignar, cerrar y volver a abrir las propuestas en el repositorio | "[Administrar tu trabajo con las propuestas](/github/managing-your-work-on-github/managing-your-work-with-issues)" | +| Administrar las etiquetas para las propuestas y solicitudes de cambios en el repositorio | "[Etiquetar las propuestas y solicitudes de cambios](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | +| Administrar hitos para las propuestas y solicitudes de cambios en el repositorio | "[Crear y editar hitos para propuestas y solicitudes de extracción](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" | +| Marcar una propuesta o solicitud de cambios en el repositorio como duplicada | "[Acerca de las propuestas y soicitudes de cambio duplicadas](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" | +| Crear, fusionar y cerrar las solicitudes de cambios en el repositorio | "[Proponer cambios en tu trabajo con solicitudes de cambios](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" | +| Habilitar e inhabilitar la fusión automática para una solicitud de cambios | "[Fusionar automáticamente una solicitud de cambios](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" | +| Aplicar los cambios sugeridos a las solicitudes de cambios en el repositorio | "[Incorporar retroalimentación en tu solicitud de cambios](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" | +| Crear una solicitud de cambios desde una bifurcación del repositorio | "[Crear una solicitud de extracción desde una bifurcación](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" | +| Emitir una revisión de una solicitud de cambios que afecte la capacidad de fusión de una solicitud de cambios | "[Revisar los cambios propuestos en una solicitud de extracción](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" | +| Crear y editar un wiki para el repositorio | "[Acerca de los wikis](/communities/documenting-your-project-with-wikis/about-wikis)" | +| Crear y editar los lanzamientos del repositorio | "[Administrar los lanzamientos en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository)" | +| Actuar como propietario del código del repositorio | "[Acerca de los propietarios del código](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %} +| Publicar, ver o instalar paquetes | "[Publicar y mantener paquetes](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" +{% endif %} +| Eliminarse como colaboradores del repositorio | "[Eliminarte a ti mismo del repositorio de un colaborador](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" | + +## Leer más + +- "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md similarity index 92% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md index 353e308e44..8a30ec8667 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md @@ -1,10 +1,11 @@ --- -title: Niveles de permiso para tableros de proyecto propiedad del usuario +title: Permission levels for a project board owned by a personal account intro: 'Un tablero de proyecto que le pertenezca a una cuenta personal tiene dos niveles de permiso: el propietario del tablero del proyecto y los colaboradores.' redirect_from: - /articles/permission-levels-for-user-owned-project-boards - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards versions: fpt: '*' ghes: '*' @@ -12,7 +13,7 @@ versions: ghec: '*' topics: - Accounts -shortTitle: Permiso para utilizar tableros de proyecto +shortTitle: Permisos del tablero de proyecto --- ## Resumen de permisos diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md similarity index 92% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md index 4b8bda5d69..e4cbfbdf49 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md @@ -5,6 +5,7 @@ redirect_from: - /articles/what-does-the-available-for-hire-checkbox-do - /github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do versions: fpt: '*' ghec: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md similarity index 96% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md index 3696dad246..2ba991aa16 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md @@ -5,6 +5,7 @@ redirect_from: - /articles/about-organization-membership - /github/setting-up-and-managing-your-github-user-account/about-organization-membership - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md similarity index 86% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md index 73a773d358..c22f7c3621 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md @@ -8,6 +8,7 @@ redirect_from: - /articles/accessing-an-organization - /github/setting-up-and-managing-your-github-user-account/accessing-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md similarity index 87% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md index 27d72cf4d0..46b143839f 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md @@ -4,6 +4,7 @@ intro: 'Si eres un miembro de una organización, puedes publicar u ocultar tu me redirect_from: - /articles/managing-your-membership-in-organizations - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md similarity index 96% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md index a616427c4a..67ea255532 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md @@ -9,6 +9,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders shortTitle: Administrar los recordatorios programados --- diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md similarity index 90% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md index 18be48b28e..ce0ec91300 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md @@ -6,6 +6,7 @@ redirect_from: - /articles/publicizing-or-hiding-organization-membership - /github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md similarity index 91% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md index fd886c2335..dc161a5532 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md @@ -6,6 +6,7 @@ redirect_from: - /articles/removing-yourself-from-an-organization - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization versions: fpt: '*' ghes: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md similarity index 93% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md index dd824bb715..ed21c07b25 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md @@ -7,6 +7,7 @@ redirect_from: - /articles/requesting-organization-approval-for-oauth-apps - /github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps versions: fpt: '*' ghec: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md similarity index 96% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md rename to translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md index e2bc0fc985..ec72efaff2 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md +++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md @@ -7,6 +7,7 @@ redirect_from: - /articles/viewing-peoples-roles-in-an-organization - /github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization versions: fpt: '*' ghes: '*' @@ -46,7 +47,7 @@ También puedes ver si un propietario de empresa tiene un rol específico en la | **Roles en la empresa** | **Roles en la organización** | **Acceso o impacto a la organización** | | ----------------------- | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Propietario de empresa | Desafiliado o sin rol oficial en la organización | No puede acceder al contenido de la organización ni a sus repositorios, pero administra los ajustes y políticas de la empresa que impactan a tu organización. | -| Propietario de empresa | Propietario de la organización | Puede configurar los ajustes de la organización y administrar el acceso a los recursos de la misma mediante equipos, etc. | +| Propietario de empresa | Propietario de organización | Puede configurar los ajustes de la organización y administrar el acceso a los recursos de la misma mediante equipos, etc. | | Propietario de empresa | Miembro de la organización | Puede acceder a los recursos y contenido de la organización, tales como repositorios, sin acceder a los ajustes de la misma. | Para revisar todos los roles en una organización, consulta la sección "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)". {% if custom-repository-roles %} Los miembros de la organización también pueden tener roles personalizados para un repositorio específico. Para obtener más información, consulta la sección "[Administrar los roles personalizados de repositorio en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)".{% endif %} diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md deleted file mode 100644 index c3f320b8cb..0000000000 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Crear y probar Node.js o Python -shortTitle: Crear & probar Node.js o Python -intro: Puedes crear un flujo de trabajo de integración continua (CI) para crear y probar tu proyecto. Utiliza el selector de lenguaje para mostrar ejemplos de tu lenguaje seleccionado. -redirect_from: - - /actions/guides/building-and-testing-nodejs-or-python -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: tutorial -topics: - - CI ---- - - - diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index 09860e8fa2..3f07f34fbc 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -11,13 +11,11 @@ versions: ghae: '*' ghec: '*' type: tutorial -hidden: true topics: - CI - Node - JavaScript shortTitle: Crear & probar con Node.js -hasExperimentalAlternative: true --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md index 0ea9602878..716e9a80f3 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -11,12 +11,10 @@ versions: ghae: '*' ghec: '*' type: tutorial -hidden: true topics: - CI - Python shortTitle: Build & test Python -hasExperimentalAlternative: true --- {% data reusables.actions.enterprise-beta %} @@ -246,7 +244,7 @@ steps: - run: pip test ``` -By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip or `Pipfile.lock` for pipenv) in the whole repository. For more information, see "[Caching packages dependencies](https://github.com/actions/setup-python#caching-packages-dependencies)" in the `setup-python` README. +By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip, `Pipfile.lock` for pipenv or `poetry.lock` for poetry) in the whole repository. For more information, see "[Caching packages dependencies](https://github.com/actions/setup-python#caching-packages-dependencies)" in the `setup-python` README. If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). Pip caches dependencies in different locations, depending on the operating system of the runner. The path you'll need to cache may differ from the Ubuntu example above, depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip) in the `cache` action repository. diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/index.md b/translations/es-ES/content/actions/automating-builds-and-tests/index.md index 99a1939d62..12e4fe8e49 100644 --- a/translations/es-ES/content/actions/automating-builds-and-tests/index.md +++ b/translations/es-ES/content/actions/automating-builds-and-tests/index.md @@ -14,13 +14,14 @@ redirect_from: - /actions/language-and-framework-guides/github-actions-for-java - /actions/language-and-framework-guides/github-actions-for-javascript-and-typescript - /actions/language-and-framework-guides/github-actions-for-python + - /actions/guides/building-and-testing-nodejs-or-python + - /actions/automating-builds-and-tests/building-and-testing-nodejs-or-python children: - /about-continuous-integration - /building-and-testing-java-with-ant - /building-and-testing-java-with-gradle - /building-and-testing-java-with-maven - /building-and-testing-net - - /building-and-testing-nodejs-or-python - /building-and-testing-nodejs - /building-and-testing-powershell - /building-and-testing-python 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 c3f9a28be1..48a2553ec4 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 @@ -223,7 +223,7 @@ Por ejemplo, este `cleanup.js` únicamente se ejecutará en ejecutores basados e ### `runs.steps` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Requerido** Los pasos que planeas ejecutar en esta acción. Estos pueden ser ya sea pasos de `run` o de `uses`. {% else %} **Requerido** Los pasos que planeas ejecutar en esta acción. @@ -231,7 +231,7 @@ Por ejemplo, este `cleanup.js` únicamente se ejecutará en ejecutores basados e #### `runs.steps[*].run` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Opcional** El comando que quieres ejecutar. Este puede estar dentro de la línea o ser un script en tu repositorio de la acción: {% else %} **Requerido** El comando que quieres ejecutar. Este puede estar dentro de la línea o ser un script en tu repositorio de la acción: @@ -261,7 +261,7 @@ Para obtener más información, consulta la sección "[``](/actions/reference/co #### `runs.steps[*].shell` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Opcional** El shell en donde quieres ejecutar el comando. Puedes utilizar cualquiera de los shells listados [aquí](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Requerido si se configuró `run`. {% else %} **Requerido** El shell en donde quieres ejecutar el comando. Puedes utilizar cualquiera de los shells listados [aquí](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Requerido si se configuró `run`. @@ -314,7 +314,7 @@ steps: **Opcional** Especifica el directorio de trabajo en donde se ejecuta un comando. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} #### `runs.steps[*].uses` **Opcional** Selecciona una acción a ejecutar como parte de un paso en tu job. Una acción es una unidad de código reutilizable. Puedes usar una acción definida en el mismo repositorio que el flujo de trabajo, un repositorio público o en una [imagen del contenedor Docker publicada](https://hub.docker.com/). diff --git a/translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md index 216f980a8d..0f1b28a8b6 100644 --- a/translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md +++ b/translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md @@ -156,7 +156,7 @@ También puedes crear una app que utilice despliegues y webhooks de estados de d ## Elegir un ejecutor -Puedes ejecutar tu flujo de trabajo de despliegue en los ejecutores hospedados en {% data variables.product.company_short %} o en los auto-hospedados. El tráfico de los ejecutores hospedados en {% data variables.product.company_short %} puede venir desde un [rango amplio de direcciones de red](/rest/reference/meta#get-github-meta-information). Si estás desplegando hacia un ambiente interno y tu compañía restringe el tráfico externo en las redes privadas, podría ser que los flujos de trabajo de {% data variables.product.prodname_actions %} que se ejecuten en ejecutores hospedados en {% data variables.product.company_short %} no se estén comunicando con tus servicios o recursos internos. Para superar esto, puedes hospedar tus propios ejecutores. Para obtener más información, consulta las secciones "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" y "[Acercad e los ejecutores hospedados en GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners)". +Puedes ejecutar tu flujo de trabajo de despliegue en los ejecutores hospedados en {% data variables.product.company_short %} o en los auto-hospedados. El tráfico de los ejecutores hospedados en {% data variables.product.company_short %} puede venir desde un [rango amplio de direcciones de red](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be able to communicate with your internal services or resources. Para superar esto, puedes hospedar tus propios ejecutores. Para obtener más información, consulta las secciones "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" y "[Acercad e los ejecutores hospedados en GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners)". {% endif %} diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md index 5b0d1e8b70..80527d4667 100644 --- a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md +++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md @@ -134,4 +134,4 @@ Los siguientes recursos también pueden ser útiles: * Para encontrar el flujo de trabajo inicial original, consulta el archivo [`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml) en el repositorio `starter-workflows` de {% data variables.product.prodname_actions %}. * La acción que se utilizó para desplegar la app web es la acción oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) de Azure. * Para encontrar más ejemplos de flujos de trabajo de GitHub Actions que desplieguen a Azure, consulta el repositorio [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples). -* La guía rápida de "[Crear una app web de Node.js en Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" dentro de la documentación de la app web de Azure demuestra cómo utilizar VS Code con la [Extensión de Azure App Service](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice). +* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using {% data variables.product.prodname_vscode %} with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice). diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index c1e1ea2515..3c82ac9aa4 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -69,7 +69,7 @@ You can use any machine as a self-hosted runner as long at it meets these requir * 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. -{% ifversion fpt or ghes > 3.2 or ghec or ghae-issue-4462 %} +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## Autoscaling your self-hosted runners You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." diff --git a/translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md index 5967079516..31a5c4f94c 100644 --- a/translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md +++ b/translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md @@ -5,7 +5,7 @@ versions: fpt: '*' ghec: '*' ghes: '>3.2' - ghae: 'issue-4462' + ghae: '*' type: overview --- diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index 627e854a8f..27275244b1 100644 --- a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -181,7 +181,7 @@ GitHub Actions -For more information, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)." +Para obtener más información, consulta la sección "[Datos de flujo de trabajo persistentes que utilizan artefactos](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)". ## Usar bases de datos y contenedores de servicio diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md index c7783d3948..39504c57ce 100644 --- a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -208,7 +208,8 @@ Los jobs simultáneos y los tiempos de ejecución de los flujos de trabajo en {% ### Utilizar lenguajes diferentes en {% data variables.product.prodname_actions %} Cuando trabajas con lenguajes diferentes en {% data variables.product.prodname_actions %}, pueeds crear un paso en tu job para configurar tus dependencias de lenguaje. Para obtener más información acerca de cómo trabajar con un lenguaje en particular, consulta la guía específica: - - [Crear y probar Node.js o Python](/actions/guides/building-and-testing-nodejs-or-python) + - [Crear y probar en Node.js](/actions/guides/building-and-testing-nodejs) + - [Crear y probar en Python](/actions/guides/building-and-testing-python) - [Compilar y probar PowerShell](/actions/guides/building-and-testing-powershell) - [Construir y probar Java con Maven](/actions/guides/building-and-testing-java-with-maven) - [Construir y probar Java con Gradle](/actions/guides/building-and-testing-java-with-gradle) diff --git a/translations/es-ES/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/es-ES/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md index a13c9d6ab2..8be88c21a1 100644 --- a/translations/es-ES/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md +++ b/translations/es-ES/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md @@ -37,7 +37,7 @@ To cache dependencies for a job, you can use {% data variables.product.prodname_ setup-node - pip, pipenv + pip, pipenv, poetry setup-python 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 ea47c1bf49..a4c75c31b1 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 @@ -24,7 +24,7 @@ Los activadores de los flujos de trabajo son eventos que ocasionan que se ejecut Algunos eventos tienen tipos de actividad múltiple. Para ellos, puedes especificar qué tipos de actividad activarán una ejecución de flujo de trabajo. Para obtener más información sobre qué significa cada tipo de actividad, consulta la sección "[Cargas útiles y eventos de webhook](/developers/webhooks-and-events/webhook-events-and-payloads)". Nota que no todos los eventos de webhook activan flujos de trabajo. -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4968 %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae %} ### `branch_protection_rule` | Carga del evento Webhook | Tipos de actividad | `GITHUB_SHA` | `GITHUB_REF` | @@ -1051,7 +1051,7 @@ on: {% endnote %} -Ejecuta tu flujo de trabajo cuando ocurre una actividad de lanzamiento en tu repositorio. Para obtener más información sobre las API de lanzamiento, consulta la sección de "[Lanzamiento](/graphql/reference/objects#release)" en la documentación de la API de GraphQL o "[Lanzamientos](/rest/reference/repos#releases)" en la documentación de la API de REST. +Ejecuta tu flujo de trabajo cuando ocurre una actividad de lanzamiento en tu repositorio. Para obtener más información sobre las API de lanzamiento, consulta la sección de "[Lanzamiento](/graphql/reference/objects#release)" en la documentación de la API de GraphQL o "[Lanzamientos](/rest/reference/releases)" en la documentación de la API de REST. Por ejemplo, puedes ejecutar un flujo de trabajo cuando un lanzamiento ha sido `publicado`. 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 fc13df5f8f..f8e633ce06 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 @@ -99,18 +99,18 @@ Puedes utilizar el comando `set-output` en tu flujo de trabajo para configurar e La siguiente tabla muestra qué funciones del toolkit se encuentran disponibles dentro de un flujo de trabajo: -| Funcion del Toolkit | Comando equivalente del flujo de trabajo | -| --------------------- | --------------------------------------------------------------------- | -| `core.addPath` | Accesible utilizando el archivo de ambiente `GITHUB_PATH` | -| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +| Funcion del Toolkit | Comando equivalente del flujo de trabajo | +| --------------------- | ----------------------------------------------------------- | +| `core.addPath` | Accesible utilizando el archivo de ambiente `GITHUB_PATH` | +| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `core.notice` | `notice` {% endif %} -| `core.error` | `error` | -| `core.endGroup` | `endgroup` | -| `core.exportVariable` | Accesible utilizando el archivo de ambiente `GITHUB_ENV` | -| `core.getInput` | Accesible utilizando la variable de ambiente `INPUT_{NAME}` | -| `core.getState` | Accesible utilizando la variable de ambiente`STATE_{NAME}` | -| `core.isDebug` | Accesible utilizando la variable de ambiente `RUNNER_DEBUG` | +| `core.error` | `error` | +| `core.endGroup` | `endgroup` | +| `core.exportVariable` | Accesible utilizando el archivo de ambiente `GITHUB_ENV` | +| `core.getInput` | Accesible utilizando la variable de ambiente `INPUT_{NAME}` | +| `core.getState` | Accesible utilizando la variable de ambiente`STATE_{NAME}` | +| `core.isDebug` | Accesible utilizando la variable de ambiente `RUNNER_DEBUG` | {%- if actions-job-summaries %} | `core.summary` | Accessible using environment variable `GITHUB_STEP_SUMMARY` | {%- endif %} @@ -170,7 +170,7 @@ Write-Output "::debug::Set the Octocat variable" {% endpowershell %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ## Configurar un mensaje de aviso diff --git a/translations/es-ES/content/admin/code-security/index.md b/translations/es-ES/content/admin/code-security/index.md index ce85a61e40..970c4013fb 100644 --- a/translations/es-ES/content/admin/code-security/index.md +++ b/translations/es-ES/content/admin/code-security/index.md @@ -5,7 +5,7 @@ intro: 'You can build security into your developers'' workflow with features tha versions: ghes: '*' ghec: '*' - ghae: issue-4864 + ghae: '*' topics: - Enterprise children: diff --git a/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md index 8afea7fc0c..2b4be13bda 100644 --- a/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md +++ b/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md @@ -5,7 +5,7 @@ shortTitle: Acerca de la seguridad de la cadena de suministro permissions: '' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise diff --git a/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md b/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md index f7bddda3c3..08434e1f9e 100644 --- a/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md +++ b/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md @@ -4,7 +4,7 @@ shortTitle: Seguridad de la cadena de suministro intro: 'You can visualize, maintain, and secure the dependencies in your developers'' software supply chain.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' topics: - Enterprise children: diff --git a/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md b/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md index 198c98b198..219f4522b2 100644 --- a/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md +++ b/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md @@ -5,7 +5,7 @@ shortTitle: View vulnerability data permissions: 'Site administrators can view vulnerability data on {% data variables.product.product_location %}.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md index 28ff87b6b6..df32c51872 100644 --- a/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -12,7 +12,7 @@ topics: ## Acerca de {% data variables.product.prodname_github_connect %} -{% data variables.product.prodname_github_connect %} amplía a {% data variables.product.product_name %} permitiendo a {% data variables.product.product_location %} beneficiarse del poder de {% data variables.product.prodname_dotcom_the_website %} de forma limitada. Después de que habilites {% data variables.product.prodname_github_connect %}, podrás habilitar características y flujos de trabajo adicionales que dependen de {% data variables.product.prodname_dotcom_the_website %}, tales como {% ifversion ghes or ghae-issue-4864 %}las {% data variables.product.prodname_dependabot_alerts %} para las vulnerabilidades de seguridad que se rastrean en la {% data variables.product.prodname_advisory_database %}{% else %}permitiendo a los usuarios utilizar acciones impulsadas por la comunidad de {% data variables.product.prodname_dotcom_the_website %} en sus archivos de flujo de trabajo{% endif %}. +{% data variables.product.prodname_github_connect %} amplía a {% data variables.product.product_name %} permitiendo a {% data variables.product.product_location %} beneficiarse del poder de {% data variables.product.prodname_dotcom_the_website %} de forma limitada. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}. {% data variables.product.prodname_github_connect %} no abre {% data variables.product.product_location %} al internet público. Ninguno de los datos privados de tu empresa se exponen a los usuarios de {% data variables.product.prodname_dotcom_the_website %}. En vez de esto, {% data variables.product.prodname_github_connect %} transmite solo los datos limitados que se necesitan para las características individuales que eliges habilitar. A menos de que habilites la sincronización de licencias, {% data variables.product.prodname_github_connect %} no transmite ninguno de los datos personales. Para obtener más información sobre los datos que transmite {% data variables.product.prodname_github_connect %}, consulta la sección "[Transmisión de datos para {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)". @@ -28,10 +28,10 @@ Después de que configuras la conexión entre {% data variables.product.product_ | Característica | Descripción | Más información | | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %} -| Sincronización automática de licencias de usuario | Administra el uso de licencias en todos los despliegues de tu {% data variables.product.prodname_enterprise %} sincronizando las licencias de usuario automáticamente desde {% data variables.product.product_location %} hacia {% data variables.product.prodname_ghe_cloud %}. | "[Habilitar la sincronización automática de licencias de usuario para tu empresa](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae-issue-4864 %} +| Sincronización automática de licencias de usuario | Administra el uso de licencias en todos los despliegues de tu {% data variables.product.prodname_enterprise %} sincronizando las licencias de usuario automáticamente desde {% data variables.product.product_location %} hacia {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} | {% data variables.product.prodname_dependabot %} | Permitir que los usuarios encuentren y corrijan vulnerabilidades en las dependencias de código. | "[Habilitar el {% data variables.product.prodname_dependabot %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} | Acciones de {% data variables.product.prodname_dotcom_the_website %} | Permite que los usuarios utilicen acciones desde {% data variables.product.prodname_dotcom_the_website %} en los archivos de flujo de trabajo. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% if server-statistics %} -| {% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} +| {% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Habilitar el {% data variables.product.prodname_server_statistics %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} | Búsqueda unificada | Permite que los usuarios incluyan repositorios en {% data variables.product.prodname_dotcom_the_website %} en los resultados de la bùsqueda cuando buscas desde {% data variables.product.product_location %}. | "[Habilitar la {% data variables.product.prodname_unified_search %} para tu empresa](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" | | Contribuciones unificadas | Permitir que los usuarios incluyan conteos de contribuciones anonimizadas para su trabajo en {% data variables.product.product_location %} en su gráfica de contribuciones en{% data variables.product.prodname_dotcom_the_website %}. | "[Habilitar las {% data variables.product.prodname_unified_contributions %} para tu empresa](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" | @@ -62,9 +62,9 @@ Cuando habilitas {% data variables.product.prodname_github_connect %} o caracter Los datos adicionales se transmiten si habilitas las características individuales de {% data variables.product.prodname_github_connect %}. -| Característica | Datos | ¿De qué forma fluyen los datos? | ¿Dónde se utilizan los datos? | -| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |{% ifversion ghes %} -| Sincronización automática de licencias de usuario | Cada ID de usuario y dirección de correo electrónico de un usuario de {% data variables.product.product_name %} | Desde {% data variables.product.product_name %} hacia {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %} +| Característica | Datos | ¿De qué forma fluyen los datos? | ¿Dónde se utilizan los datos? | +| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------ |{% ifversion ghes %} +| Sincronización automática de licencias de usuario | Cada ID de usuario y dirección de correo electrónico de un usuario de {% data variables.product.product_name %} | Desde {% data variables.product.product_name %} hacia {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %} | {% data variables.product.prodname_dependabot_alerts %} | Alertas de vulnerabilidades | Desde {% data variables.product.prodname_dotcom_the_website %} hasta {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %} | {% data variables.product.prodname_dependabot_updates %} | Las dependencias y los metadatos de cada repositorio de una dependencia

Si una dependencia se almacena en un repositorio privado de {% data variables.product.prodname_dotcom_the_website %}, los datos solo se transmitirán si el {% data variables.product.prodname_dependabot %} se configura y se autoriza su acceso a dicho repositorio. | Desde {% data variables.product.prodname_dotcom_the_website %} hasta {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} | Acciones de {% data variables.product.prodname_dotcom_the_website %} | Nombre de la acción, acción (archivo YAML de {% data variables.product.prodname_marketplace %}) | De {% data variables.product.prodname_dotcom_the_website %} a {% data variables.product.product_name %}

De {% data variables.product.product_name %} a {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% if server-statistics %} diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md index 6e444aa113..6cb812451d 100644 --- a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md +++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -15,7 +15,7 @@ redirect_from: permissions: 'Enterprise owners can enable {% data variables.product.prodname_dependabot %}.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise @@ -64,6 +64,8 @@ After you enable {% data variables.product.prodname_dependabot_alerts %}, you ca {% endnote %} +By default, {% data variables.product.prodname_actions %} runners used by {% data variables.product.prodname_dependabot %} need access to the internet, to download updated packages from upstream package managers. For {% data variables.product.prodname_dependabot_updates %} powered by {% data variables.product.prodname_github_connect %}, internet access provides your runners with a token that allows access to dependencies and advisories hosted on {% data variables.product.prodname_dotcom_the_website %}. + With {% data variables.product.prodname_dependabot_updates %}, {% data variables.product.company_short %} automatically creates pull requests to update dependencies in two ways. - **{% data variables.product.prodname_dependabot_version_updates %}**: Los usuarios agregan un archivo de configuración del {% data variables.product.prodname_dependabot %} al repositorio para habilitar el {% data variables.product.prodname_dependabot %} para que cree solicitudes de cambios cuando se lance una versión nueva de una dependencia rastreada. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)". @@ -120,6 +122,11 @@ Before you enable {% data variables.product.prodname_dependabot_updates %}, you ![Screenshot of the dropdown menu to enable updating vulnerable dependencies](/assets/images/enterprise/site-admin-settings/dependabot-updates-button.png) -{% elsif ghes > 3.2 %} -Cuando habilitas las {% data variables.product.prodname_dependabot_alerts %}, deberías considerar también configurar las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_dependabot_security_updates %}. Esta característica permite que los desarrolladores arreglen las vulnerabilidades en sus dependencias. Para obtener más información, consulta la sección "[Administrar los ejecutores auto-hospedados para las {% data variables.product.prodname_dependabot_updates %} en tu empresa](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)". +{% endif %} +{% ifversion ghes > 3.2 %} + +Cuando habilitas las {% data variables.product.prodname_dependabot_alerts %}, deberías considerar también configurar las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_dependabot_security_updates %}. Esta característica permite que los desarrolladores arreglen las vulnerabilidades en sus dependencias. Para obtener más información, consulta la sección "[Administrar los ejecutores auto-hospedados para las {% data variables.product.prodname_dependabot_updates %} en tu empresa](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)". + +If you need enhanced security, we recommend configuring {% data variables.product.prodname_dependabot %} to use private registries. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_dependabot %}](/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot)." + {% endif %} 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 bbd29e52aa..3335f4cc4d 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 @@ -673,6 +673,12 @@ This utility manually repackages a repository network to optimize pack storage. You can add the optional `--prune` argument to remove unreachable Git objects that aren't referenced from a branch, tag, or any other ref. This is particularly useful for immediately removing [previously expunged sensitive information](/enterprise/user/articles/remove-sensitive-data/). +{% warning %} + +**Warning**: Before using the `--prune` argument to remove unreachable Git objects, put {% data variables.product.product_location %} into maintenance mode, or ensure the repository is offline. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)." + +{% endwarning %} + ```shell ghe-repo-gc username/reponame ``` diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md index 6913f58355..ede3b243a4 100644 --- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md +++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md @@ -43,7 +43,7 @@ Cuando la instancia está en modo de mantenimiento, se rechazan todos los acceso {% if ip-exception-list %} -You can perform initial validation of your maintenance operation by configuring an IP exception list to allow access to {% data variables.product.product_location %} from only the IP addresses and ranges provided. Attempts to access {% data variables.product.product_location %} from IP addresses not specified on the IP exception list will receive a response consistent with those sent when the instance is in maintenance mode. +Puedes llevar a cabo una validación inicial de tu operación de mantenimiento si configuras una lista de IP de excepción para permitir el acceso a {% data variables.product.product_location %} solo desde las direcciones IP y rangos de ellas que proporcionaste. Los intentos para acceder a {% data variables.product.product_location %} desde las direcciones IP que no se especifican en la lista de excepciones IP recibirán una respuesta consistente con aquellas enviadas cuando la instancia esté en modo de mantenimiento. {% endif %} diff --git a/translations/es-ES/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md b/translations/es-ES/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md index b071b281ac..00fe89ba84 100644 --- a/translations/es-ES/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md +++ b/translations/es-ES/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md @@ -33,12 +33,13 @@ Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will ins ## Configuring a repository cache -1. During the beta, you must enable the feature flag for repository caching on your primary {% data variables.product.prodname_ghe_server %} appliance. +{% ifversion ghes = 3.3 %} +1. On your primary {% data variables.product.prodname_ghe_server %} appliance, enable the feature flag for repository caching. ``` $ ghe-config cluster.cache-enabled true ``` - +{%- endif %} 1. Set up a new {% data variables.product.prodname_ghe_server %} appliance on your desired platform. This appliance will be your repository cache. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)." {% data reusables.enterprise_installation.replica-steps %} 1. Connect to the repository cache's IP address using SSH. @@ -46,7 +47,13 @@ Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will ins ```shell $ ssh -p 122 admin@REPLICA IP ``` - +{%- ifversion ghes = 3.3 %} +1. On your cache replica, enable the feature flag for repository caching. + + ``` + $ ghe-config cluster.cache-enabled true + ``` +{%- endif %} {% data reusables.enterprise_installation.generate-replication-key-pair %} {% data reusables.enterprise_installation.add-ssh-key-to-primary %} 1. To verify the connection to the primary and enable replica mode for the repository cache, run `ghe-repl-setup` again. diff --git a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md index eea6843caf..64955a7f5a 100644 --- a/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md +++ b/translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md @@ -18,7 +18,7 @@ topics: SNMP es una norma común para controlar dispositivos en una red. Recomendamos firmemente habilitar SNMP para que puedas controlar la salud de {% data variables.product.product_location %} y saber cuándo agregar más memoria, almacenamiento, o rendimiento del procesador a la máquina del servidor. -{% data variables.product.prodname_enterprise %} tiene una instalación SNMP estándar, para poder aprovechar los [diversos plugins](http://www.monitoring-plugins.org/doc/man/check_snmp.html) disponibles para Nagios o para cualquier otro sistema de control. +{% data variables.product.prodname_enterprise %} tiene una instalación SNMP estándar, para poder aprovechar los [diversos plugins](https://www.monitoring-plugins.org/doc/man/check_snmp.html) disponibles para Nagios o para cualquier otro sistema de control. ## Configurar SNMP v2c @@ -66,7 +66,7 @@ Si habilitas el SNMP v3, puedes aprovechar la seguridad en base al usuario aumen #### Consultar datos de SNMP -Tanto la información del nivel de software como de hardware sobre tu aparato está disponible con SNMP v3. Debido a la falta de cifrado y privacidad para los niveles de seguridad `noAuthNoPriv` y `authNoPriv`, excluimos la tabla de `hrSWRun` (1.3.6.1.2.1.25.4) de los reportes de SNMP resultantes. Incluimos esta tabla si estás usando el nivel de seguridad `authPriv`. Para obtener más información, consulta la "[Documentación de referencia de OID](http://oidref.com/1.3.6.1.2.1.25.4)". +Tanto la información del nivel de software como de hardware sobre tu aparato está disponible con SNMP v3. Debido a la falta de cifrado y privacidad para los niveles de seguridad `noAuthNoPriv` y `authNoPriv`, excluimos la tabla de `hrSWRun` (1.3.6.1.2.1.25.4) de los reportes de SNMP resultantes. Incluimos esta tabla si estás usando el nivel de seguridad `authPriv`. Para obtener más información, consulta la "[Documentación de referencia de OID](https://oidref.com/1.3.6.1.2.1.25.4)". Con SNMP v2c, solo está disponible la información del nivel de hardware de tu aparato. Estas aplicaciones y servicios dentro de {% data variables.product.prodname_enterprise %} no tienen configurado OID para informar métricas. Hay varios MIB disponibles, que puedes ver ejecutando `snmpwalk` en una estación de trabajo separada con soporte SNMP en tu red: diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index ed31203bba..434dee7092 100644 --- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -32,7 +32,7 @@ This guide shows you how to apply a centralized management approach to self-host 1. Deploy a self-hosted runner for your enterprise 1. Create a group to manage access to the runners available to your enterprise 1. Optionally, further restrict the repositories that can use the runner -{%- ifversion ghec or ghae-issue-4462 or ghes > 3.2 %} +{%- ifversion ghec or ghae or ghes > 3.2 %} 1. Optionally, build custom tooling to automatically scale your self-hosted runners {% endif %} @@ -59,7 +59,7 @@ Primero, habilita las {% data variables.product.prodname_actions %} para todas l 1. Select {% data reusables.actions.policy-label-for-select-actions-workflows %} and **Allow actions created by GitHub** to allow local actions{% if actions-workflow-policy %} and reusable workflows{% endif %}, and actions created by {% data variables.product.company_short %}. {% if actions-workflow-policy %} - ![Screenshot of "Allow select actions" and "Allow actions created by {% data variables.product.company_short %}" for {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-allow-select-actions-and-actions-from-github-with-workflows.png) + ![Captura de pantalla de "Permitir acciones seleccionadas" y "Permitir acciones creadas por {% data variables.product.company_short %}" para las {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-allow-select-actions-and-actions-from-github-with-workflows.png) {%- else %} ![Captura de pantalla de "Permitir acciones seleccionadas" y "Permitir acciones creadas por {% data variables.product.company_short %}" para las {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-allow-select-actions-and-actions-from-github.png) {%- endif %} @@ -122,7 +122,7 @@ Optionally, organization owners can further restrict the access policy of the ru Para obtener más información, consulta la sección "[Administrar el acceso a los ejecutores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)". -{% ifversion ghec or ghae-issue-4462 or ghes > 3.2 %} +{% ifversion ghec or ghae or ghes > 3.2 %} ## 5. Automatically scale your self-hosted runners diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index f539aeca8d..7ea2bb0b09 100644 --- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -46,7 +46,7 @@ Before enabling access to all actions from {% data variables.product.prodname_do ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) 1. {% data reusables.actions.enterprise-limit-actions-use %} -{% ifversion ghes > 3.2 or ghae-issue-4815 %} +{% ifversion ghes > 3.2 or ghae %} ## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md index 1af5a98dfd..3f5f872968 100644 --- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md +++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md @@ -33,7 +33,7 @@ If your machine has access to both systems at the same time, you can do the sync The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories. -{% ifversion ghes > 3.2 or ghae-issue-4815 %} +{% ifversion ghes > 3.2 or ghae %} {% note %} **Note:** The `actions-sync` tool is intended for use in systems where {% data variables.product.prodname_github_connect %} is not enabled. If you run the tool on a system with {% data variables.product.prodname_github_connect %} enabled, you may see the error `The repository has been retired and cannot be reused`. This indicates that a workflow has used that action directly on {% data variables.product.prodname_dotcom_the_website %} and the namespace is retired on {% data variables.product.product_location %}. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." diff --git a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index 97e81a3546..5d4d770631 100644 --- a/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -47,7 +47,7 @@ Once {% data variables.product.prodname_github_connect %} is configured, you can 1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`. 1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}. - {% ifversion ghes > 3.2 or ghae-issue-4815 %} + {% ifversion ghes > 3.2 or ghae %} {% note %} **Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.product.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index 2cefee09bc..cf7f6fd4cc 100644 --- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -188,7 +188,7 @@ topics: | `config_entry.update` | A configuration setting was edited. Estos eventos solo se pueden ver en la bitácora de auditoría del administrador de sitio. El tipo de eventos registrado se relaciona con:
- Políticas y ajustes de empresa
- Permisos y ajustes de repositorio y organización
- Git, LFS de Git, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, proyecto, y ajustes de seguridad de código. | {%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} ### Acciones de la categoría `dependabot_alerts` | Acción | Descripción | @@ -226,7 +226,7 @@ topics: | `dependabot_security_updates_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. | {%- endif %} -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} ### Acciones de la categoría `dependency_graph` | Acción | Descripción | @@ -620,7 +620,7 @@ topics: {%- ifversion fpt or ghec %} | `org.oauth_app_access_approved` | An owner [granted organization access to an {% data variables.product.prodname_oauth_app %}](/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization). | `org.oauth_app_access_denied` | An owner [disabled a previously approved {% data variables.product.prodname_oauth_app %}'s access](/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to an organization. | `org.oauth_app_access_requested` | An organization member requested that an owner grant an {% data variables.product.prodname_oauth_app %} access to an organization. {%- endif %} -| `org.recreate` | An organization was restored. | `org.register_self_hosted_runner` | A new self-hosted runner was registered. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una organización](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". | `org.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was removed. | `org.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was removed from an organization. | `org.remove_billing_manager` | An owner removed a billing manager from an organization. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Eliminar a un gerente de factguración de tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization)"{% endif %}{% ifversion not ghae %} o cuando se requiera [la autenticación bifactorial en una organización](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) y un gerente de facturación no haya usado la 2FA o la haya inhabilitado.{% endif %}| | `org.remove_member` | Un [propietario eliminó a un miembro de una organización](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} o cuando [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) un miembro de la organización no utiliza 2FA o la inhabilita{% endif %}. Also an [organization member removed themselves](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization) from an organization. | `org.remove_outside_collaborator` | Un propietario eliminó a un colaborador externo de una organización{% ifversion not ghae %} o cuando [se requirió la autenticación bifactorial en una organización](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) y un colaborador externo no la utilizó o la inhabilitó{% endif %}. | `org.remove_self_hosted_runner` | A self-hosted runner was removed. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de una organización](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)". | `org.rename` | An organization was renamed. | `org.restore_member` | An organization member was restored. For more information, see "[Reinstating a former member of your organization](/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization)." +| `org.recreate` | An organization was restored. | `org.register_self_hosted_runner` | A new self-hosted runner was registered. Para obtener más información, consulta la sección "[Agregar un ejecutor auto-hospedado a una organización](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". | `org.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was removed. | `org.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was removed from an organization. | `org.remove_billing_manager` | An owner removed a billing manager from an organization. |{% ifversion fpt or ghec %}Para obtener más información, consulta la sección "[Eliminar a un gerente de factguración de tu organización](/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization)"{% endif %}{% ifversion not ghae %} o cuando se requiera [la autenticación bifactorial en una organización](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) y un gerente de facturación no haya usado la 2FA o la haya inhabilitado.{% endif %}| | `org.remove_member` | Un [propietario eliminó a un miembro de una organización](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} o cuando [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) un miembro de la organización no utiliza 2FA o la inhabilita{% endif %}. Also an [organization member removed themselves](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization) from an organization. | `org.remove_outside_collaborator` | Un propietario eliminó a un colaborador externo de una organización{% ifversion not ghae %} o cuando [se requirió la autenticación bifactorial en una organización](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) y un colaborador externo no la utilizó o la inhabilitó{% endif %}. | `org.remove_self_hosted_runner` | A self-hosted runner was removed. Para obtener más información, consulta la sección "[Eliminar a un ejecutor de una organización](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)". | `org.rename` | An organization was renamed. | `org.restore_member` | An organization member was restored. For more information, see "[Reinstating a former member of your organization](/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization)." {%- ifversion ghec %} | `org.revoke_external_identity` | An organization owner revoked a member's linked identity. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)". | `org.revoke_sso_session` | An organization owner revoked a member's SAML session. Para obtener más información, consulta la sección "[Visualizar y administrar el acceso de SAML de un miembro a tu organización](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)". {%- endif %} @@ -862,7 +862,7 @@ topics: | ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `pull_request.close` | A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." | | `pull_request.converted_to_draft` | A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)." | -| `pull_request.create` | A pull request was created. For more information, see "[Creating a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." | +| `pull_request.create` | A pull request was created. Para obtener más información, consulta la sección"[Crear una solicitud de extracción](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." | | `pull_request.create_review_request` | A review was requested on a pull request. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request.in_progress` | A pull request was marked as in progress. | | `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch. | @@ -1014,7 +1014,7 @@ topics: | `repository_visibility_change.disable` | The ability for enterprise members to update a repository's visibility was disabled. Members are unable to change repository visibilities in an organization, or all organizations in an enterprise. | | `repository_visibility_change.enable` | The ability for enterprise members to update a repository's visibility was enabled. Members are able to change repository visibilities in an organization, or all organizations in an enterprise. | -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} ### acciones de la categoría `repository_vulnerability_alert` | Acción | Descripción | diff --git a/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md index df5c9b065e..b7d618ff16 100644 --- a/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md +++ b/translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Configurar la compatibilidad del ecosistema de paquetes para tu empresa -intro: 'You can configure {% data variables.product.prodname_registry %} for your enterprise by globally enabling or disabling individual package ecosystems on your enterprise, including {% ifversion ghes > 3.4 %}{% data variables.product.prodname_container_registry %}, {% endif %}Docker, and npm. Aprende sobre otros requisitos de configuración para hacer compatibles algunos ecosistemas de paquetes específicos.' +intro: 'Puedes configurar el {% data variables.product.prodname_registry %} para tu empresa si habilitas o inhabilitas globalmente los ecosistemas de paquetes individuales en ella, incluyendo {% ifversion ghes > 3.4 %}el {% data variables.product.prodname_container_registry %}, {% endif %} Docker y npm. Aprende sobre otros requisitos de configuración para hacer compatibles algunos ecosistemas de paquetes específicos.' redirect_from: - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise - /admin/packages/configuring-packages-support-for-your-enterprise @@ -24,8 +24,8 @@ Para prevenir que los paquetes nuevos se carguen, puedes configurar un ecosistem {% data reusables.enterprise_site_admin_settings.packages-tab %} 1. Debajo de "Alternación de ecosistema", para cada tipo de paquete, selecciona **Enabled**, **Read-Only**, o **Disabled**. {%- ifversion ghes > 3.4 %}{% note -%} -**Note**: Subdomain isolation must be enabled to toggle the - Opciones de las {% data variables.product.prodname_container_registry %}. +**Nota**: El aislamiento de subdominios debe estar habilitado para alternar las + opciones del {% data variables.product.prodname_container_registry %}. {%- endnote %}{%- endif %}{%- ifversion ghes > 3.1 %} ![Alternación de ecosistemas](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png){% else %} ![Ecosystem toggles](/assets/images/enterprise/3.1/site-admin-settings/ecosystem-toggles.png){% endif %} diff --git a/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md index e3c9168c5d..5c716f6f64 100644 --- a/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md +++ b/translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -37,10 +37,10 @@ Para habilitar el {% data variables.product.prodname_registry %} y configurar el ## Paso 3: Especifica los ecosistemas de paquetes que serán compatibles con tu instancia -Elige qué ecosistemas de paquetes te gustaría habilitar, inhabilitar o configurar como de solo lectura en tu {% data variables.product.product_location %}. Available options are {% ifversion ghes > 3.4 %}{% data variables.product.prodname_container_registry %}, {% endif %}Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. Para obtener más información, consulta la sección "[Configurar la compatibilidad de ecosistemas de paquetes para tu empresa](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)". +Elige qué ecosistemas de paquetes te gustaría habilitar, inhabilitar o configurar como de solo lectura en tu {% data variables.product.product_location %}. Las opciones disponibles son {% ifversion ghes > 3.4 %}el {% data variables.product.prodname_container_registry %}, {% endif %}Docker, RubyGems, npm, Apache Maven, Gradle o NuGet. Para obtener más información, consulta la sección "[Configurar la compatibilidad de ecosistemas de paquetes para tu empresa](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)". ## Paso 4: De ser necesario, asegúrate de que tienes un certificado de TLS para la URL de hospedaje de tu paquete -If subdomain isolation is enabled for {% data variables.product.product_location %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `{% data reusables.package_registry.container-registry-hostname %}`. Asegúrate de que cada URL de host de paquete incluya `https://`. +Si el aislamiento de subdominios se habilita para {% data variables.product.product_location %}, necesitarás crear y cargar un certificado TLS que permita la URL del host de paquetes para cada ecosistema que quieras utilizar, tal como `{% data reusables.package_registry.container-registry-hostname %}`. Asegúrate de que cada URL de host de paquete incluya `https://`. Puedes crear el certificado manualmente, o puedes utilizar _Let's Encrypt_. Si ya utilizas _Let's Encrypt_, debes solicitar un certificado TLS nuevo después de habilitar el {% data variables.product.prodname_registry %}. Para obtener más información acerca de las URL del host de los paquetes, consulta "[Habilitar el aislamiento de subdominios](/enterprise/admin/configuration/enabling-subdomain-isolation)". Para obtener más información sobre cómo cargar certificados TLS a {% data variables.product.product_name %}, consulta la sección "[Configurar el TLS](/enterprise/admin/configuration/configuring-tls)". diff --git a/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md index 388d0011a3..5232ddb865 100644 --- a/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md +++ b/translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md @@ -33,7 +33,7 @@ Para obtener más información acerca las opciones que tienes, consulta los [doc **Advertencia**: MinIO anunció la eliminación de MinIO Gateways. Desde el 1 de junio de 2022, tanto el soporte como las correcciones de errores para la implementación de la puerta de enlace de la NAS de MinIO estarán disponibles únicamente para los clientes con suscripciones de pago a través de su contrato de soporte LTS. Si quieres seguir utilizando MinIO Gateways con {% data variables.product.prodname_registry %}, te recomendamos migrarte al soporte LTS de MinIO. Para obtener más información, consulta el [programa para eliminar a MinIO Gateway para GCS, Azure, HDFS](https://github.com/minio/minio/issues/14331) en el repositorio minio/minio. -Other modes of MinIO remain available with standard support. +Otros modos de MinIO siguen disponibles con el soporte estándar. {% endwarning %} diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md index b8afc75441..ac8de2f8e5 100644 --- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md +++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md @@ -66,7 +66,7 @@ Puedes elegir inhabilitar {% data variables.product.prodname_actions %} para tod 1. Debajo de "Políticas", selecciona {% data reusables.actions.policy-label-for-select-actions-workflows %} y agrega tus acciones{% if actions-workflow-policy %} y flujos de trabajo reutilizables{% endif %} requeridos a la lista. {% if actions-workflow-policy %} ![Agrega acciones y flujos de trabajo reutilizables a la lista de elementos permitidos](/assets/images/help/organizations/enterprise-actions-policy-allow-list-with-workflows.png) - {%- elsif ghes or ghae-issue-5094 %} + {%- elsif ghes or ghae %} ![Agregar acciones a la lista de elementos permitidos](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) {%- elsif ghae %} ![Agregar acciones a la lista de elementos permitidos](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) diff --git a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md index a725faf1c7..c3beae0da5 100644 --- a/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md +++ b/translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md @@ -68,7 +68,15 @@ You can view more information about the person's access to your enterprise, such {% ifversion ghec %} ## Viewing pending invitations -You can see all the pending invitations to become administrators, members, or outside collaborators in your enterprise. You can filter the list in useful ways, such as by organization. You can find a specific person by searching for their username or display name. +You can see all the pending invitations to become members, administrators, or outside collaborators in your enterprise. You can filter the list in useful ways, such as by organization. You can find a specific person by searching for their username or display name. + +In the list of pending members, for any individual account, you can cancel all invitations to join organizations owned by your enterprise. This does not cancel any invitations for that same person to become an enterprise administrator or outside collaborator. + +{% note %} + +**Note:** If an invitation was provisioned via SCIM, you must cancel the invitation via your identity provider (IdP) instead of on {% data variables.product.prodname_dotcom %}. + +{% endnote %} If you use {% data variables.product.prodname_vss_ghe %}, the list of pending invitations includes all {% data variables.product.prodname_vs %} subscribers that haven't joined any of your organizations on {% data variables.product.prodname_dotcom %}, even if the subscriber does not have a pending invitation to join an organization. For more information about how to get {% data variables.product.prodname_vs %} subscribers access to {% data variables.product.prodname_enterprise %}, see "[Setting up {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)." @@ -77,7 +85,9 @@ If you use {% data variables.product.prodname_vss_ghe %}, the list of pending in 1. Under "People", click **Pending invitations**. ![Screenshot of the "Pending invitations" tab in the sidebar](/assets/images/help/enterprises/pending-invitations-tab.png) +1. Optionally, to cancel all invitations for an account to join organizations owned by your enterprise, to the right of the account, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Cancel invitation**. + ![Screenshot of the "Cancel invitation" button](/assets/images/help/enterprises/cancel-enterprise-member-invitation.png) 1. Optionally, to view pending invitations for enterprise administrators or outside collaborators, under "Pending members", click **Administrators** or **Outside collaborators**. ![Screenshot of the "Members", "Administrators", and "Outside collaborators" tabs](/assets/images/help/enterprises/pending-invitations-type-tabs.png) diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index b0c87d6303..113e3394b5 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -16,7 +16,7 @@ shortTitle: Authentication to GitHub --- ## About authentication to {% data variables.product.prodname_dotcom %} -To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. +To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. You can access your resources in {% data variables.product.product_name %} in a variety of ways: in the browser, via {% data variables.product.prodname_desktop %} or another desktop application, with the API, or via the command line. Each way of accessing {% data variables.product.product_name %} supports different modes of authentication. {%- ifversion not fpt %} @@ -27,35 +27,47 @@ You can access your resources in {% data variables.product.product_name %} in a ## Authenticating in your browser -You can authenticate to {% data variables.product.product_name %} in your browser {% ifversion ghae %}using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."{% else %}in different ways. +{% ifversion ghae %} + +You can authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)." + +{% else %} {% ifversion fpt or ghec %} -- If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} - If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also be required to enable two-factor authentication. +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} + +If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also use two-factor authentication and SAML single sign-on, which can be required by organization and enterprise owners. + +{% else %} + +You can authenticate to {% data variables.product.product_name %} in your browser in a number of ways. + {% endif %} - **Username and password only** - You'll create a password when you create your account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)."{% ifversion fpt or ghec %} - If you have not enabled 2FA, {% data variables.product.product_name %} will ask for additional verification when you first sign in from an unrecognized device, such as a new browser profile, a browser where the cookies have been deleted, or a new computer. - - After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the GitHub Mobile application installed, you'll receive a notification there instead.{% endif %} + + After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the {% data variables.product.prodname_mobile %} application installed, you'll receive a notification there instead. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."{% endif %} - **Two-factor authentication (2FA)** (recommended) - If you enable 2FA, after you successfully enter your username and password, we'll also prompt you to provide a code that's generated by a time-based one time password (TOTP) application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)." - - In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% endif %}{% ifversion ghes %} -- **Identity provider (IdP) authentication** - - Your site administrator may configure {% data variables.product.product_location %} to use authentication with an IdP instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)." + - In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% ifversion ghes %} +- **External authentication** + - Your site administrator may configure {% data variables.product.product_location %} to use external authentication instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)."{% endif %}{% ifversion fpt or ghec %} +- **SAML single sign-on** + - Before you can access resources owned by an organization or enterprise account that uses SAML single sign-on, you may need to also authenticate through an IdP. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} + {% endif %} ## Authenticating with {% data variables.product.prodname_desktop %} - You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." ## Authenticating with the API You can authenticate with the API in different ways. -- **Personal access tokens** +- **Personal access tokens** - In limited situations, such as testing, you can use a personal access token to access the API. Using a personal access token enables you to revoke access at any time. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." - **Web application flow** - For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)." @@ -68,11 +80,11 @@ You can access repositories on {% data variables.product.product_name %} from th ### HTTPS -You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. +You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a personal access token or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). -If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a personal access token. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git). +If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a personal access token. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them with a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git). ### SSH diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index 569faa19b0..921eddc4d0 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -44,7 +44,7 @@ Un token sin alcances asignados solo puede acceder a información pública. Para {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.personal_access_tokens %} {% data reusables.user-settings.generate_new_token %} -5. Asígnale a tu token un nombre descriptivo. ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %} +5. Asígnale a tu token un nombre descriptivo. ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae or ghec %} 6. Para dar un vencimiento a tu token, selecciona el menú desplegable de **Vencimiento** y luego haz clic en uno predeterminado o utiliza el selector de calendario. ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %} 7. Selecciona los alcances o permisos que deseas otorgarle a este token. Para usar tu token para acceder a repositorios desde la línea de comando, selecciona **repo**. {% ifversion fpt or ghes or ghec %} @@ -80,5 +80,5 @@ En vez de ingresar tu PAT manualmente para cada operación de HTTPS de Git, pued ## Leer más -- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} - "[Vencimiento y revocación de token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md index 15402730d8..758735fc15 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md @@ -25,9 +25,9 @@ Puedes eliminar el archivo desde la última confirmación con `git rm`. Para obt {% warning %} -Este artículo te dice cómo hacer que las confirmaciones con datos sensibles sean inalcanzables para las personas que intenten violar la seguridad o para las etiquetas de tu repositorio de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Sin embargo, es importante tener en cuenta que esas confirmaciones pueden seguir siendo accesibles desde cualquier clon o bifurcación de tu repositorio, directamente por medio de sus hashes de SHA-1 en las visualizaciones cacheadas en {% data variables.product.product_name %} y a través de cualquier solicitud de extracción que las referencie. No puedes eliminar los datos sensibles desde los clones o bifurcaciones de tu repositorio que tengan otros usuarios, pero puedes eliminar las vistas almacenadas en caché permanentemente, así como las referencias a los datos sensibles en las solicitudes de cambios en {% data variables.product.product_name %} si contactas al {% data variables.contact.contact_support %}. +**Warning**: This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. However, those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. No puedes eliminar los datos sensibles desde los clones o bifurcaciones de tu repositorio que tengan otros usuarios, pero puedes eliminar las vistas almacenadas en caché permanentemente, así como las referencias a los datos sensibles en las solicitudes de cambios en {% data variables.product.product_name %} si contactas al {% data variables.contact.contact_support %}. -**Advertencia: Una vez que hayas subido una confirmación a {% data variables.product.product_name %}, deberías considerar cualquier dato sensible en la confirmación como puesto en riesgo.** Si confirmaste una contraseña, ¡cámbiala! Si confirmaste una clave, genera una nueva. El eliminar los datos puestos en riesgo no resuelve su exposición inicial, especialmente en clones o bifurcaciones de tu repositorio existentes. Considera estas limitaciones en tu decisión para reescribir el historial de tu repositorio. +**Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! Si confirmaste una clave, genera una nueva. El eliminar los datos puestos en riesgo no resuelve su exposición inicial, especialmente en clones o bifurcaciones de tu repositorio existentes. Considera estas limitaciones en tu decisión para reescribir el historial de tu repositorio. {% endwarning %} @@ -152,7 +152,7 @@ Para ilustrar cómo funciona `git filter-repo`, te mostraremos cómo eliminar tu Después de utilizar ya sea la herramienta de BFG o `git filter-repo` para eliminar los datos sensibles y subir tus cambios a {% data variables.product.product_name %}, debes tomar algunos pasos adicionales para eliminar los datos de {% data variables.product.product_name %} completamente. -1. Contáctate con {% data variables.contact.contact_support %} y pregúntale cómo eliminar visualizaciones cacheadas y referencias a los datos confidenciales en las solicitudes de extracción en {% data variables.product.product_name %}. Por favor, proporciona el nombre del repositorio o un enlace a la confirmación que necesitas eliminar. +1. Contáctate con {% data variables.contact.contact_support %} y pregúntale cómo eliminar visualizaciones cacheadas y referencias a los datos confidenciales en las solicitudes de extracción en {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed.{% ifversion ghes %} For more information about how site administrators can remove unreachable Git objects, see "[Command line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repo-gc)."{% endif %} 2. Pídeles a tus colaboradores que [rebasen](https://git-scm.com/book/en/Git-Branching-Rebasing), *no* fusionen, cualquier rama que hayan creado fuera del historial de tu repositorio antiguo (contaminado). Una confirmación de fusión podría volver a introducir algo o todo el historial contaminado sobre el que acabas de tomarte el trabajo de purgar. 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 a3f6efb1db..0e84bf911a 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 @@ -28,15 +28,11 @@ La bitácora de seguridad lista todas las acciones que se llevaron a cabo en los 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) {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} ## Buscar tu registro de seguridad {% data reusables.audit_log.audit-log-search %} ### Búsqueda basada en la acción realizada -{% else %} -## Entender los eventos en tu registro de seguridad -{% endif %} Tus acciones activan los eventos que se listan en tu bitácora de seguridad. Las acciones se agrupan en las siguientes categorías: @@ -109,10 +105,10 @@ Un resumen de algunas de las acciones más frecuentes que se registran como even ### Acciones de la categoría `oauth_authorization` -| Acción | Descripción | -| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `create (crear)` | Se activa cuando [obtienes acceso a una {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps). | -| `destroy (destruir)` | Se activa cuando [revocas el acceso de una {% data variables.product.prodname_oauth_app %} a tu cuenta](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} y cuando[las autorizaciones se revocan o vencen](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %} +| Acción | Descripción | +| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `create (crear)` | Se activa cuando [obtienes acceso a una {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps). | +| `destroy (destruir)` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %} {% ifversion fpt or ghec %} @@ -178,25 +174,25 @@ Un resumen de algunas de las acciones más frecuentes que se registran como even {% ifversion fpt or ghec %} ### acciones de la categoría `sponsors` -| Acción | Descripción | -| ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `custom_amount_settings_change` | Se activa cuando habilitas o inhabilitas las cantidades personalizadas o cuando cambias la cantidad personalizada sugerida (consulta la secicón "[Administrar tus niveles de patrocinio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | -| `repo_funding_links_file_action (acción de archivo de enlaces de financiamiento del repositorio)` | Se activa cuando cambias el archivo FUNDING de tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)") | -| `sponsor_sponsorship_cancel (cancelación del patrocinio del patrocinador)` | Se activa cuando cancelas un patrocinio (consulta "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)") | -| `sponsor_sponsorship_create (creación de un patrocinio de patrocinador)` | Se activa cuando patrocinas una cuenta (consulta la sección "[Patrocinar a un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | -| `sponsor_sponsorship_payment_complete` | Se activa después de que patrocinas una cuenta y se procesa tu pago (consulta la sección "[Patrocinar a un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | -| `sponsor_sponsorship_preference_change (cambio de preferencia de patrocinio de patrocinador)` | Se activa cuando cambias si deseas recibir actualizaciones por correo electrónico de un programador patrocinado o no (consulta la sección "[Administrar tu patrocinio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)") | -| `sponsor_sponsorship_tier_change (cambiar nivel de patrocinio de patrocinador)` | Se activa cuando subes o bajas de categoría tu patrocinio (consulta "[Subir de categoría un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)") | -| `sponsored_developer_approve (aprobación de programador patrocinado)` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `sponsored_developer_create (creación de programador patrocinado)` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +| Acción | Descripción | +| ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `custom_amount_settings_change` | Se activa cuando habilitas o inhabilitas las cantidades personalizadas o cuando cambias la cantidad personalizada sugerida (consulta la secicón "[Administrar tus niveles de patrocinio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | +| `repo_funding_links_file_action (acción de archivo de enlaces de financiamiento del repositorio)` | Se activa cuando cambias el archivo FUNDING de tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `sponsor_sponsorship_cancel (cancelación del patrocinio del patrocinador)` | Se activa cuando cancelas un patrocinio (consulta "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)") | +| `sponsor_sponsorship_create (creación de un patrocinio de patrocinador)` | Se activa cuando patrocinas una cuenta (consulta la sección "[Patrocinar a un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | +| `sponsor_sponsorship_payment_complete` | Se activa después de que patrocinas una cuenta y se procesa tu pago (consulta la sección "[Patrocinar a un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | +| `sponsor_sponsorship_preference_change (cambio de preferencia de patrocinio de patrocinador)` | Se activa cuando cambias si deseas recibir actualizaciones por correo electrónico de un programador patrocinado o no (consulta la sección "[Administrar tu patrocinio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)") | +| `sponsor_sponsorship_tier_change (cambiar nivel de patrocinio de patrocinador)` | Se activa cuando subes o bajas de categoría tu patrocinio (consulta "[Subir de categoría un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)") | +| `sponsored_developer_approve (aprobación de programador patrocinado)` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `sponsored_developer_create (creación de programador patrocinado)` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | | `sponsored_developer_disable` | Se activa cuando se inhabilita tu cuenta de {% data variables.product.prodname_sponsors %} -| `sponsored_developer_redraft` | Se activa cuando tu cuenta de {% data variables.product.prodname_sponsors %} se devuelve a un estado de borrador desde un estado aprobado | -| `sponsored_developer_profile_update (actualización del perfil de programador patrocinado)` | Se activa cuando editas tu perfil de desarrollador patrocinado (consulta la sección "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)") | -| `sponsored_developer_request_approval (aprobación de solicitud de programador patrocinado)` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `sponsored_developer_tier_description_update (actualización de descripción del nivel de programador patrocinado)` | Se activa cuando cambias la descripción de un nivel de patrocinio (consulta la sección "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)") | -| `sponsored_developer_update_newsletter_send (envío de boletín de actualización del programador patrocinado)` | Se activa cuando envías una actualización de correo electrónico a tus patrocinadores (consulta la sección "[Contactar a tus patrocinadores](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)") | -| `waitlist_invite_sponsored_developer (invitación a la lista de espera de programadores patrocinados)` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `waitlist_join (incorporación a la lista de espera)` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +| `sponsored_developer_redraft` | Se activa cuando tu cuenta de {% data variables.product.prodname_sponsors %} se devuelve a un estado de borrador desde un estado aprobado | +| `sponsored_developer_profile_update (actualización del perfil de programador patrocinado)` | Se activa cuando editas tu perfil de desarrollador patrocinado (consulta la sección "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)") | +| `sponsored_developer_request_approval (aprobación de solicitud de programador patrocinado)` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `sponsored_developer_tier_description_update (actualización de descripción del nivel de programador patrocinado)` | Se activa cuando cambias la descripción de un nivel de patrocinio (consulta la sección "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)") | +| `sponsored_developer_update_newsletter_send (envío de boletín de actualización del programador patrocinado)` | Se activa cuando envías una actualización de correo electrónico a tus patrocinadores (consulta la sección "[Contactar a tus patrocinadores](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)") | +| `waitlist_invite_sponsored_developer (invitación a la lista de espera de programadores patrocinados)` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `waitlist_join (incorporación a la lista de espera)` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | {% endif %} {% ifversion fpt or ghec %} diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md index b4d34a1044..85f11a5597 100644 --- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md +++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md @@ -14,7 +14,7 @@ redirect_from: - /github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation --- -Cuando un token {% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}venció o {% endif %}se revocó, ya no puede utilizarse para autenticar solicitudes de Git y de las API. No es posible restablecer un token revocado o vencido, ya seas tú o la aplicación necesitarán crear un token nuevo. +Cuando un token {% ifversion fpt or ghae or ghes > 3.2 or ghec %}venció o {% endif %}se revocó, ya no puede utilizarse para autenticar solicitudes de Git y de las API. No es posible restablecer un token revocado o vencido, ya seas tú o la aplicación necesitarán crear un token nuevo. Este artículo te explica las posibles razones por las cuales tu token de {% data variables.product.product_name %} podría revocarse o vencer. @@ -24,7 +24,7 @@ Este artículo te explica las posibles razones por las cuales tu token de {% dat {% endnote %} -{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## El token se revocó después de llegar a su fecha de vencimiento Cuando creas un token de acceso personal, te recomendamos que configures una fecha de vencimiento para este. Al alcanzar la fecha de vencimiento de tu token, este se revocará automáticamente. Para obtener más información, consulta la sección "[Crear un token de acceso personal](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)". 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 bea844a524..3b3d8f5201 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 @@ -57,7 +57,7 @@ Consulta "[Revisar tus integraciones autorizadas](/articles/reviewing-your-autho {% ifversion not ghae %} -Si restableciste la contraseña de tu cuenta y también te gustaría activar un cierre de sesión desde la app de GitHub Mobile, entonces puedes revocar tu autorización de la App de OAuth de "GitHub iOS" o "GitHub Android". Para obtener información adicional, consulta la sección "[Revisar tus integraciones autorizadas](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)". +If you have reset your account password and would also like to trigger a sign-out from the {% data variables.product.prodname_mobile %} app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. This will sign out all instances of the {% data variables.product.prodname_mobile %} app associated with your account. Para obtener información adicional, consulta la sección "[Revisar tus integraciones autorizadas](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)". {% endif %} diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md index 32f8ee0c84..035d099981 100644 --- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md +++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md @@ -22,7 +22,7 @@ shortTitle: Cambiar el método de entrega de 2FA {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security %} -3. Al lado de "SMS delivery" (Entrega de SMS), haz clic en **Edit** (Editar). ![Editar opciones de entrega de SMS](/assets/images/help/2fa/edit-sms-delivery-option.png) +3. Next to "Primary two-factor method", click **Change**. ![Edit primary delivery options](/assets/images/help/2fa/edit-primary-delivery-option.png) 4. En "Delivery options" (Opciones de entrega), haz clic en **Reconfigure two-factor authentication** (Reconfirgurar autenticación de dos factores). ![Cambiar tus opciones de entrega 2FA](/assets/images/help/2fa/2fa-switching-methods.png) 5. Decide si deseas configurar la autenticación de dos factores mediante una app móvil TOTP o un mensaje de texto. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)". - Para configurar la autenticación de dos factores mediante una app móvil TOTP, haz clic en **Set up using an app** (Configurar mediante una app). 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 bb20a1b738..99430e1ffb 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 @@ -48,7 +48,7 @@ Los jobs que se ejecutan en Windows y macOS y que se hospedan en {% data variabl El almacenamiento que utilza un repositorio es el total del almacenamiento utilizado por los artefactos de {% data variables.product.prodname_actions %} y por {% data variables.product.prodname_registry %}. Tu costo de almacenamiento es el uso total para todos los repositorios que pertenezcan a tu cuenta. Para obtener más información sobre los costos de {% data variables.product.prodname_registry %}, consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)". - Si tu uso de cuenta sobrepasa estos límites y habías configurado un límite de gastos mayor a $0 USD, pagarás $0.25 USD por GB de almacenamiento por mes y por minuto de uso dependiendo en el sistema operativo que utilice el ejecutor hospedado en {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} redondea hacia arriba los minutos que utiliza cada job. + If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} redondea hacia arriba los minutos que utiliza cada job. {% note %} diff --git a/translations/es-ES/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/es-ES/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md index 0bd1827b1a..d24e5e5ff1 100644 --- a/translations/es-ES/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md +++ b/translations/es-ES/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md @@ -50,9 +50,9 @@ Todos los datos de transferencia saliente, cuando se desencadenan mediante {% da El uso de almacenamiento se comparte con los artefactos de compilación que produce {% data variables.product.prodname_actions %} para los repositorios que pertenecen a tu cuenta. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)". -{% data variables.product.prodname_dotcom %} cobra el uso a la cuenta a la que pertenece el repositorio en donde se publica el paquete. Si tu uso de cuenta sobrepasa estos límites y has configurado un límite de gastos mayor a $0 USD, pagarás $0.25 USD por GB de almacenamiento y $0.50 USD por GB de transferencia de datos. +{% data variables.product.prodname_dotcom %} cobra el uso a la cuenta a la que pertenece el repositorio en donde se publica el paquete. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and $0.50 USD per GB of data transfer. -Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %}, permite los gastos ilimitados, utiliza 150GB de almacenamiento, y tiene 50GB de transferencia de datos durante un mes, ésta tendrá un excedente de 148GB en el almacenamiento y de 40GB en transferencia de datos para ese mes. El excedente de almacenamiento costaría $0.25 USD por GB, o $37 USD. El excedente para transferencia de datos costaría $0.50 USD por GB, o $20 USD. +Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %}, permite los gastos ilimitados, utiliza 150GB de almacenamiento, y tiene 50GB de transferencia de datos durante un mes, ésta tendrá un excedente de 148GB en el almacenamiento y de 40GB en transferencia de datos para ese mes. The storage overage would cost $0.008 USD per GB per day or $37 USD. El excedente para transferencia de datos costaría $0.50 USD por GB, o $20 USD. {% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %} diff --git a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md index 0f327fa0ca..3004a0980f 100644 --- a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md +++ b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md @@ -57,7 +57,7 @@ Una persona podría completar las tareas porque tiene todos los roles, pero podr **Tips**: - Si bien no se requiere, recomendamos que el propietario de la organización envíe una invitación a la misma dirección de correo electrónico que se utiliza para el Nombre Primario de Usuario (UPN) del suscriptor. Cuando la dirección de correo electrónico de {% data variables.product.product_location %} coincide con el UPN del suscriptor, puedes asegurar que otra empresa no reclame la licencia del suscriptor. - - Si el suscriptor acepta la invitación a la organización con una cuenta personal existente en {% data variables.product.product_location %}, recomendamos que este agregue la dirección de correo electrónico que utiliza para {% data variables.product.prodname_vs %} a su cuenta personal de {% data variables.product.product_location %}. Para obtener más información, consula la sección "[Agregar una dirección de correo electrónico a tu cuenta de {% data variables.product.prodname_dotcom %}](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)". + - Si el suscriptor acepta la invitación a la organización con una cuenta personal existente en {% data variables.product.product_location %}, recomendamos que este agregue la dirección de correo electrónico que utiliza para {% data variables.product.prodname_vs %} a su cuenta personal de {% data variables.product.product_location %}. Para obtener más información, consula la sección "[Agregar una dirección de correo electrónico a tu cuenta de {% data variables.product.prodname_dotcom %}](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)". - Si el propietario de la organización debe invitar a una gran cantidad de suscriptores, puedes llevar el proceso más rápidamente con un script. Para obtener más información, consulta el [script de ejemplo de PowerShell](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) en el repositorio `github/platform-samples`. {% endtip %} diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md index cccde8bdec..a462055e5a 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md @@ -73,7 +73,7 @@ By default, the {% data variables.product.prodname_codeql_workflow %} uses the ` If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Additionally, when an `on:push` scan returns results that can be mapped to an open pull request, these alerts will automatically appear on the pull request in the same places as other pull request alerts. The alerts are identified by comparing the existing analysis of the head of the branch to the analysis for the target branch. For more information on {% data variables.product.prodname_code_scanning %} alerts in pull requests, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." {% endif %} @@ -85,7 +85,7 @@ For more information about the `pull_request` event, see "[Events that trigger w If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." {% endif %} diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index 7649b34387..990c6e03c7 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -155,9 +155,9 @@ The names of the {% data variables.product.prodname_code_scanning %} analysis ch ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png) -When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. +When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. -{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png) The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request. @@ -167,13 +167,13 @@ For example, in the screenshot above, {% data variables.product.prodname_code_sc ![Missing analysis for commit message](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png) {% endif %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ### Reasons for the "Analysis not found" message {% else %} ### Reasons for the "Missing analysis" message {% endif %} -After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. +After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include: diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index 0facaadb22..66507b8e68 100644 --- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -28,7 +28,7 @@ topics: ## About {% data variables.product.prodname_code_scanning %} results on pull requests In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} In repositories where {% data variables.product.prodname_code_scanning %} is configured to scan each time code is pushed, {% data variables.product.prodname_code_scanning %} will also map the results to any open pull requests and add the alerts as annotations in the same places as other pull request checks. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." {% endif %} @@ -42,7 +42,7 @@ There are many options for configuring {% data variables.product.prodname_code_s For all configurations of {% data variables.product.prodname_code_scanning %}, the check that contains the results of {% data variables.product.prodname_code_scanning %} is: **{% data variables.product.prodname_code_scanning_capc %} results**. The results for each analysis tool used are shown separately. Any new alerts caused by changes in the pull request are shown as annotations. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)." +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)." ![{% data variables.product.prodname_code_scanning_capc %} results check on a pull request](/assets/images/help/repository/code-scanning-results-check.png) {% endif %} diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index 2225d13a1d..5619e484dc 100644 --- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -10,7 +10,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md index 336fdb6182..c45c8cb9a1 100644 --- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md +++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md @@ -5,7 +5,7 @@ shortTitle: Configure Dependabot alerts versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -38,7 +38,7 @@ You can enable or disable {% data variables.product.prodname_dependabot_alerts % {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %} -3. Under "Code security and analysis", to the right of {% data variables.product.prodname_dependabot_alerts %}, click **Disable all** or **Enable all**. ![Screenshot of "Configure security and analysis" features with "Enable all" or "Disable all" buttons emphasized](/assets/images/help/dependabot/dependabot-alerts-disable-or-enable-all.png) +3. Debajo de "Análisis y seguridad del código", a la derecha de las {% data variables.product.prodname_dependabot_alerts %}, haz clic en **Inhabilitar todas** o **Habilitar todas**. ![Screenshot of "Configure security and analysis" features with "Enable all" or "Disable all" buttons emphasized](/assets/images/help/dependabot/dependabot-alerts-disable-or-enable-all.png) 4. Optionally, enable {% data variables.product.prodname_dependabot_alerts %} by default for new repositories that you create. ![Screenshot of "Enable Dependabot alerts" with "Enable by default for new private repositories" checkbox emphasized](/assets/images/help/dependabot/dependabot-alerts-enable-by-default.png) 5. Click **Disable {% data variables.product.prodname_dependabot_alerts %}** or **Enable {% data variables.product.prodname_dependabot_alerts %}** to disable or enable {% data variables.product.prodname_dependabot_alerts %} for all the repositories you own. ![Screenshot of "Enable Dependabot alerts" with "Enable Dependabot alerts" button emphasized](/assets/images/help/dependabot/dependabot-alerts-enable-dependabot-alerts.png) @@ -51,7 +51,7 @@ When you enable {% data variables.product.prodname_dependabot_alerts %} for exis 3. Under "Code security and analysis", to the right of {% data variables.product.prodname_dependabot_alerts %}, enable or disable {% data variables.product.prodname_dependabot_alerts %} by default for new repositories that you create. ![Screenshot of "Configure security and analysis" with "Enable for all new private repositories" check emphasized](/assets/images/help/dependabot/dependabot-alerts-enable-for-all-new-repositories.png) {% else %} -{% data variables.product.prodname_dependabot_alerts %} for your repositories can be enabled or disabled by your enterprise owner. For more information, see "[Enabling Dependabot for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +{% data variables.product.prodname_dependabot_alerts %} for your repositories can be enabled or disabled by your enterprise owner. Para obtener más información, consulta la sección "[Habilitar al Dependabot para tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". {% endif %} diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md index d7a1e74b78..21377b5720 100644 --- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md +++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -31,7 +31,7 @@ Cuando el {% data variables.product.prodname_dependabot %} detecta las dependenc {% ifversion fpt or ghec %}Si eres un propietario de organización, puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_alerts %} para todos los repositorios en tu organización con un clic. También puedes configurar si se habilitará o inhabilitará la detección de dependencias vulnerables para los repositorios recién creados. Para obtener más información, consulta la sección "[Administrar la configuración de análisis y seguridad para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)". {% endif %} -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} Predeterminadamente, si el propietario de tu empresa configuró las notificaciones por correo electrónico en ella, recibirás las {% data variables.product.prodname_dependabot_alerts %} por este medio. Los propietarios de empresas también pueden habilitar las {% data variables.product.prodname_dependabot_alerts %} sin notificaciones. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_dependabot %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/index.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/index.md index 9117598069..7ee4f2b8fb 100644 --- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/index.md +++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/index.md @@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md index c5f632c3e2..b7e6e81dc7 100644 --- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md +++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md @@ -11,7 +11,7 @@ shortTitle: View Dependabot alerts versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -55,7 +55,7 @@ For supported languages, {% data variables.product.prodname_dependabot %} automa {% note %} -**Note:** During the beta release, this feature is available only for new Python advisories created *after* April 14, 2022, and for a subset of historical Python advisories. GitHub is working to backfill data across additional historical Python advisories, which are added on a rolling basis. Vulnerable calls are highlighted only on the {% data variables.product.prodname_dependabot_alerts %} pages. +**Note:** During the beta release, this feature is available only for new Python advisories created *after* April 14, 2022, and for a subset of historical Python advisories. {% data variables.product.prodname_dotcom %} is working to backfill data across additional historical Python advisories, which are added on a rolling basis. Vulnerable calls are highlighted only on the {% data variables.product.prodname_dependabot_alerts %} pages. {% endnote %} @@ -65,7 +65,7 @@ You can filter the view to show only alerts where {% data variables.product.prod For alerts where vulnerable calls are detected, the alert details page shows additional information: -- A code block showing where the function is used or, where there are multiple calls, the first call to the function. +- One or more code blocks showing where the function is used. - An annotation listing the function itself, with a link to the line where the function is called. ![Screenshot showing the alert details page for an alert with a "Vulnerable call" label](/assets/images/help/repository/review-calls-to-vulnerable-functions.png) @@ -106,7 +106,7 @@ For supported languages, {% data variables.product.prodname_dependabot %} detect ### Fixing vulnerable dependencies -1. View the details for an alert. For more information, see "[Viewing vulnerable dependencies](#viewing-vulnerable-dependencies)" (above). +1. Ver los detalles de una alerta. Para obtener más información, consulta la sección "[Ver las dependencias vulnerables](#viewing-vulnerable-dependencies)" (anteriormente). {% ifversion fpt or ghec or ghes > 3.2 %} 1. If you have {% data variables.product.prodname_dependabot_security_updates %} enabled, there may be a link to a pull request that will fix the dependency. Alternatively, you can click **Create {% data variables.product.prodname_dependabot %} security update** at the top of the alert details page to create a pull request. ![Crea un botón de actualización de seguridad del {% data variables.product.prodname_dependabot %}](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png) 1. Optionally, if you do not use {% data variables.product.prodname_dependabot_security_updates %}, you can use the information on the page to decide which version of the dependency to upgrade to and create a pull request to update the dependency to a secure version. diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/translations/es-ES/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md index a4a8a05086..8cd835f8ba 100644 --- a/translations/es-ES/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md +++ b/translations/es-ES/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md @@ -63,7 +63,7 @@ Si no se habilitan las actualizaciones de seguridad para tu repositorio y no sab Puedes habilitar o inhabilitar las {% data variables.product.prodname_dependabot_security_updates %} para un repositorio individual (ver a continuación). -You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your personal account or organization. Para obtener más información, consulta la sección "[Administrar los ajustes de seguridad y análisis de tu cuenta personal](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" o "[Administrar los ajustes de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". +You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your personal account or organization. For more information, see "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." Las {% data variables.product.prodname_dependabot_security_updates %} requieren de configuraciones de repositorio específicas. Para obtener más información, consulta "[Repositorios soportados](#supported-repositories)". diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md index b505b983bc..ee757626eb 100644 --- a/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md +++ b/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md @@ -30,7 +30,7 @@ shortTitle: Actualizaciones de versión del dependabot El {% data variables.product.prodname_dependabot %} hace el esfuerzo de mantener tus dependencias. Puedes utilizarlo para garantizar que tu repositorio se mantenga automáticamente con los últimos lanzamientos de los paquetes y aplicaciones de los que depende. -You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_configuration file into your repository. Este archivo de configuración especifica la ubicación del manifiesto o de otros archivos de definición de paquetes almacenados en tu repositorio. El {% data variables.product.prodname_dependabot %} utiliza esta información para revisar los paquetes y las aplicaciones desactualizadas. El {% data variables.product.prodname_dependabot %} determina si hay una versión nueva de una dependencia al buscar el versionamiento semántico ([semver](https://semver.org/)) de la dependencia para decidir si debería actualizarla a esa versión. Para ciertos administradores de paquetes, {% data variables.product.prodname_dependabot_version_updates %} también es compatible con su delegación a proveedores. Las dependencias delegadas (o almacenadas en caché) son aquellas que se registran en un directorio específico en un repositorio en vez de que se referencien en un manifiesto. Las dependencias delegadas a proveedores están disponibles desde el momento de su creación, incluso si los servidores de paquetes no se encuentran disponibles. Las {% data variables.product.prodname_dependabot_version_updates %} pueden configurarse para verificar las dependencias delegadas a proveedores para las nuevas versiones y también pueden actualizarse de ser necesario. +You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_ configuration file into your repository. Este archivo de configuración especifica la ubicación del manifiesto o de otros archivos de definición de paquetes almacenados en tu repositorio. El {% data variables.product.prodname_dependabot %} utiliza esta información para revisar los paquetes y las aplicaciones desactualizadas. El {% data variables.product.prodname_dependabot %} determina si hay una versión nueva de una dependencia al buscar el versionamiento semántico ([semver](https://semver.org/)) de la dependencia para decidir si debería actualizarla a esa versión. Para ciertos administradores de paquetes, {% data variables.product.prodname_dependabot_version_updates %} también es compatible con su delegación a proveedores. Las dependencias delegadas (o almacenadas en caché) son aquellas que se registran en un directorio específico en un repositorio en vez de que se referencien en un manifiesto. Las dependencias delegadas a proveedores están disponibles desde el momento de su creación, incluso si los servidores de paquetes no se encuentran disponibles. Las {% data variables.product.prodname_dependabot_version_updates %} pueden configurarse para verificar las dependencias delegadas a proveedores para las nuevas versiones y también pueden actualizarse de ser necesario. Cuando el {% data variables.product.prodname_dependabot %} identifica una dependencia desactualizada, levanta una solicitud de extracción para actualizar el manifiesto a su última versión de la dependencia. Lara las dependencias delegadas a proveedores, el {% data variables.product.prodname_dependabot %} levanta una solicitud de cambios para reemplazar la dependencia desactualizada directamente con la versión nueva. Verificas que tu prueba pase, revisas el registro de cambios y notas de lanzamiento que se incluyan en el resumen de la solicitud de extracción y, posteriormente, lo fusionas. Para obtener más información, consulta la sección "[Configurar las actualizaciones de versión del {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)". diff --git a/translations/es-ES/content/code-security/dependabot/index.md b/translations/es-ES/content/code-security/dependabot/index.md index cb1f4984f9..2cfeef9d87 100644 --- a/translations/es-ES/content/code-security/dependabot/index.md +++ b/translations/es-ES/content/code-security/dependabot/index.md @@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/translations/es-ES/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/es-ES/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index ad0caeadd5..9cb2e51ff7 100644 --- a/translations/es-ES/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/es-ES/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -36,7 +36,7 @@ topics: * {% data variables.product.prodname_dependabot %} escanea cualquier subida a la rama predeterminada que contenga un archivo de manifiesto. Cuando se agrega un registro de vulnerabilidad nuevo, este escanea todos los repositorios existentes y genera una alerta para cada repositorio vulnerable. Las {% data variables.product.prodname_dependabot_alerts %} se agregan a nivel del repositorio, en vez de crear una alerta por cada vulnerabilidad. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". * {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} se activa cuando recibes una alerta sobre una dependencia vulnerable en tu repositorio. Cuando sea posible, el {% data variables.product.prodname_dependabot %} creará una solicitud de cambios en tu repositorio para actualizar la dependencia vulnerable a la versión segura mínima posible que se requiere para evitar la vulnerabilidad. Para obtener más información, consulta las secciones "[Acerca de las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" y "[Solucionar problemas en los errores del {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)". - {% endif %}El {% data variables.product.prodname_dependabot %} no escanea los repositorios para encontrar dependencias vulnerables en horarios específicos, sino cuando algo cambia. Por ejemplo, se activará un escaneo cuando se agregue una dependencia nueva ({% data variables.product.prodname_dotcom %} verifica esto en cada subida) o cuando se agrega una vulnerabilidad a la base de datos de las asesorías {% ifversion ghes or ghae-issue-4864 %} y se sincroniza con {% data variables.product.product_location %}{% endif %}. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)". + {% endif %}El {% data variables.product.prodname_dependabot %} no escanea los repositorios para encontrar dependencias vulnerables en horarios específicos, sino cuando algo cambia. Por ejemplo, se activará un escaneo cuando se agregue una dependencia nueva ({% data variables.product.prodname_dotcom %} verifica esto en cada subida) o cuando se agrega una vulnerabilidad a la base de datos de las asesorías {% ifversion ghes or ghae %} y se sincroniza con {% data variables.product.product_location %}{% endif %}. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)". ## Do {% data variables.product.prodname_dependabot_alerts %} only relate to vulnerable dependencies in manifests and lockfiles? 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 21c6e0e3f7..c32115569b 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 @@ -20,7 +20,7 @@ topics: The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Available for all repositories {% endif %} ### Security policy @@ -41,7 +41,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% endif %} -{% ifversion ghes < 3.3 or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae %} ### {% data variables.product.prodname_dependabot_alerts %} {% data reusables.dependabot.dependabot-alerts-beta %} @@ -55,7 +55,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ### Dependency graph The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository. @@ -100,13 +100,13 @@ Available only with a license for {% data variables.product.prodname_GH_advanced Automatically detect tokens or credentials that have been checked into a repository. You can view alerts for any secrets that {% data variables.product.company_short %} finds in your code, so that you know which tokens or credentials to treat as compromised. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ### Dependency review 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 or ghae-issue-4554 %} +{% ifversion ghec or ghes > 3.1 or ghae %} ### Security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams {% ifversion ghec %} 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 ebb6dbe2c8..dd6785e84c 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 @@ -33,7 +33,7 @@ You can create a default security policy that will display in any of your organi {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph {% 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. @@ -51,7 +51,7 @@ You can create a default security policy that will display in any of your organi For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Managing dependency review @@ -138,7 +138,7 @@ 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 fpt or ghes > 3.1 or ghec or ghae-issue-4554 %}{% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae-issue-4554 %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %} +{% ifversion fpt or ghes > 3.1 or ghec or ghae %}{% ifversion ghes > 3.1 or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %} {% ifversion ghec %} diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md index 6ee9dc430b..8b9288bdea 100644 --- a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md +++ b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md @@ -44,7 +44,7 @@ From the main page of your repository, click **{% octicon "gear" aria-label="The For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)." -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing the dependency graph {% ifversion fpt or ghec %} @@ -61,7 +61,7 @@ For more information, see "[Exploring the dependencies of a repository](/code-se {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} {% data variables.product.prodname_dependabot_alerts %} are generated when {% data variables.product.prodname_dotcom %} identifies a dependency in the dependency graph with a vulnerability. {% ifversion fpt or ghec %}You can enable {% data variables.product.prodname_dependabot_alerts %} for any repository.{% endif %} @@ -75,11 +75,11 @@ For more information, see "[Exploring the dependencies of a repository](/code-se {% data reusables.dependabot.dependabot-alerts-beta %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[Managing security and analysis settings for your personal account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account){% endif %}." +For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account){% endif %}." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Managing dependency review Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." diff --git a/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md index 255a48389b..26d4e5a31c 100644 --- a/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md @@ -1,13 +1,13 @@ --- title: Acerca del resumen de seguridad intro: 'Puedes ver, filtrar y clasificar las alertas de seguridad para los repositorios que pertenezcan a tu organización o equipo en un solo lugar: la página de Resumen de Seguridad.' -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' redirect_from: - /code-security/security-overview/exploring-security-alerts versions: fpt: '*' - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' type: how_to @@ -22,7 +22,7 @@ topics: shortTitle: Acerca del resumen de seguridad --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} @@ -69,7 +69,7 @@ A nivel organizacional, el resumen de seguridad muestra seguridad agregada y esp {% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} ### Acerca del resumen de seguridad a nivel empresarial -En el nivel empresarial, el resumen de seguridad muestra información de seguridad agregada y específica del repositorio para tu empresa. Puedes ver los repositorios que pertenecen a tu empresa, los cuales tengan alertas de seguridad, o ver todas las alertas del {% data variables.product.prodname_secret_scanning %} de toda tu empresa. +En el nivel empresarial, el resumen de seguridad muestra información de seguridad agregada y específica del repositorio para tu empresa. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise. Los propietarios de organizaciones y administradores de seguridad para las organizaciones de tu empresa también tienen acceso limitado al resumen de seguridad a nivel empresarial. Solo pueden ver los repositorios y alertas de las organizaciones a las cuales tienen acceso completo. diff --git a/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index 138eb640d7..6cc4383862 100644 --- a/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -1,10 +1,10 @@ --- title: Filtrar alertas en el resumen de seguridad intro: Utiliza filtros para ver categorías específicas de las alertas -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' versions: - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' type: how_to @@ -17,7 +17,7 @@ topics: shortTitle: Filtrar alertas --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} diff --git a/translations/es-ES/content/code-security/security-overview/index.md b/translations/es-ES/content/code-security/security-overview/index.md index de81942b93..ba0527588d 100644 --- a/translations/es-ES/content/code-security/security-overview/index.md +++ b/translations/es-ES/content/code-security/security-overview/index.md @@ -5,7 +5,7 @@ intro: 'Visualiza, clasifica y filtra las alertas de seguridad desde cualquier p product: '{% data reusables.gated-features.security-center %}' versions: fpt: '*' - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' topics: diff --git a/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md index 1ad544e466..61747fb733 100644 --- a/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md +++ b/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md @@ -1,7 +1,7 @@ --- title: Ver el resumen de seguridad intro: Navegar a las diversas vistas disponibles en el resumen de seguridad -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' versions: ghae: issue-5503 @@ -17,7 +17,7 @@ topics: shortTitle: Ver el resumen de seguridad --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} @@ -28,7 +28,8 @@ shortTitle: Ver el resumen de seguridad 1. Para ver la información agregada sobre los tipos de alerta, haz clic en **Mostrar más**. ![Botón de mostrar más](/assets/images/help/organizations/security-overview-show-more-button.png) {% data reusables.organizations.filter-security-overview %} {% if security-overview-views %} -1. Como alternativa y opción, utiliza la barra lateral a la izquierda para filtrar información por característica de seguridad. En cada página, puedes utilizar filtros que sean específicos para cada característica para refinar tu búsqueda. ![Captura de pantalla de la página específica del escaneo de código](/assets/images/help/organizations/security-overview-code-scanning-alerts.png) +{% data reusables.organizations.security-overview-feature-specific-page %} + ![Captura de pantalla de la página específica del escaneo de código](/assets/images/help/organizations/security-overview-code-scanning-alerts.png) ## Visualizar las alertas en toda tu organización @@ -42,6 +43,9 @@ shortTitle: Ver el resumen de seguridad {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} 1. In the left sidebar, click {% octicon "shield" aria-label="The shield icon" %} **Code Security**. +{% if security-overview-feature-specific-alert-page %} +{% data reusables.organizations.security-overview-feature-specific-page %} +{% endif %} {% endif %} ## Visualizar las alertas para un repositorio diff --git a/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md b/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md index 0f0f6c11cf..0f4080325a 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md +++ b/translations/es-ES/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md @@ -19,6 +19,8 @@ topics: At its core, end-to-end software supply chain security is about making sure the code you distribute hasn't been tampered with. Previously, attackers focused on targeting dependencies you use, for example libraries and frameworks. Attackers have now expanded their focus to include targeting user accounts and build processes, and so those systems must be defended as well. +For information about features in {% data variables.product.prodname_dotcom %} that can help you secure dependencies, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." + ## About these guides This series of guides explains how to think about securing your end-to-end supply chain: personal account, code, and build processes. Each guide explains the risk to that area, and introduces the {% data variables.product.product_name %} features that can help you address that risk. @@ -29,7 +31,7 @@ Everyone's needs are different, so each guide starts with the highest impact cha - "[Mejores prácticas para asegurar el código en tu cadena de suministros](/code-security/supply-chain-security/end-to-end-supply-chain/securing-code)" -- "[Best practices for securing your build system](/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds)" +- "[Mejores prácticas para asegurar tu sistema de compilación](/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds)" ## Leer más diff --git a/translations/es-ES/content/code-security/supply-chain-security/index.md b/translations/es-ES/content/code-security/supply-chain-security/index.md index 25c7cbfb69..4b4bd19f35 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/index.md +++ b/translations/es-ES/content/code-security/supply-chain-security/index.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md index 98a9baa2ee..3a74065bb6 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md @@ -6,7 +6,7 @@ shortTitle: Dependency review versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -37,6 +37,8 @@ For more information about configuring dependency review, see "[Configuring depe Dependency review supports the same languages and package management ecosystems as the dependency graph. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)." +For more information on supply chain features available on {% data variables.product.product_name %}, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." + {% ifversion ghec or ghes %} ## Enabling dependency review diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md index f1911cf350..88722216e5 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -54,6 +54,10 @@ Other supply chain features on {% data variables.product.prodname_dotcom %} rely El {% data variables.product.prodname_dependabot %} hace referencias de los datos de las dependencias que proporciona la gráfica de dependencias con la lista de las vulnerabilidades publicadas en la {% data variables.product.prodname_advisory_database %}, escanea tus dependencias y genera {% data variables.product.prodname_dependabot_alerts %} cuando se detecta una vulnerabilidad potencial. {% endif %} +{% ifversion fpt or ghec or ghes %} +For best practice guides on end-to-end supply chain security including the protection of personal accounts, code, and build processes, see "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)." +{% endif %} + ## Feature overview ### What is the dependency graph @@ -74,7 +78,7 @@ Dependency review helps reviewers and contributors understand dependency changes - Dependency review tells you which dependencies were added, removed, or updated, in a pull request. You can use the release dates, popularity of dependencies, and vulnerability information to help you decide whether to accept the change. - You can see the dependency review for a pull request by showing the rich diff on the **Files Changed** tab. -For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." +Para obtener más información sobre la revisión de dependencias, consulta la sección "[Acerca de la revisión de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)". {% endif %} @@ -128,7 +132,7 @@ Para obtener más información sobre las {% data variables.product.prodname_depe Public repositories: - **Dependency graph**—enabled by default and cannot be disabled. - **Dependency review**—enabled by default and cannot be disabled. -- **{% data variables.product.prodname_dependabot_alerts %}**—no se habilita predeterminadamente. {% data variables.product.prodname_dotcom %} detects vulnerable dependencies and displays information in 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 %}. You can also enable or disable Dependabot alerts for all repositories owned by your user account or organization. Para obtener más información, consulta la sección "[Administrar los ajustes de seguridad y análisis para tu cuenta de usuario](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account)" o "[Administrar lis ajustes de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)". +- **{% data variables.product.prodname_dependabot_alerts %}**—no se habilita predeterminadamente. {% data variables.product.prodname_dotcom %} detects vulnerable dependencies and displays information in 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 %}. También puedes habilitar o inhabilitar las alertas del Dependabot para todos los repositorios que pertenezcan a tu cuenta de usuario u organización. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." Private repositories: - **Dependency graph**—not enabled by default. The feature can be enabled by repository administrators. Para obtener más información, consulta la sección "[Explorar las dependencias de un repositorio](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)". @@ -137,16 +141,16 @@ Private repositories: {% elsif ghec %} - **Dependency review**—available in private repositories owned by organizations provided you have a license for {% data variables.product.prodname_GH_advanced_security %} and the dependency graph enabled. Para obtener más información, consulta las secciones "[Acerca de la {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" y "[Explorar las dependencias de un repositorio](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" {% endif %} -- **{% data variables.product.prodname_dependabot_alerts %}**—no se habilita predeterminadamente. Los propietarios de los repositorios privados o las personas con acceso administrativo puede habilitar las {% data variables.product.prodname_dependabot_alerts %} si habilitan la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} para sus repositorios. También puedes habilitar o inhabilitar las alertas del Dependabot para todos los repositorios que pertenezcan a tu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar los ajustes de seguridad y análisis para tu cuenta de usuario](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account)" o "[Administrar lis ajustes de seguridad y análisis para tu organización](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)". +- **{% data variables.product.prodname_dependabot_alerts %}**—no se habilita predeterminadamente. Los propietarios de los repositorios privados o las personas con acceso administrativo puede habilitar las {% data variables.product.prodname_dependabot_alerts %} si habilitan la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} para sus repositorios. También puedes habilitar o inhabilitar las alertas del Dependabot para todos los repositorios que pertenezcan a tu cuenta de usuario u organización. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." Any repository type: -- **{% data variables.product.prodname_dependabot_security_updates %}**—no se habilita predeterminadamente. Puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)." -- **{% data variables.product.prodname_dependabot_version_updates %}**—no se habilita predeterminadamente. Las personas con permisos de escritura en un repositorio pueden habilitar las {% data variables.product.prodname_dependabot_version_updates %}. For information about enabling version updates, see "[Configuring {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)." +- **{% data variables.product.prodname_dependabot_security_updates %}**—no se habilita predeterminadamente. Puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. Para obtener más información sobre cómo habilitar las actualizaciones de seguridad, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)". +- **{% data variables.product.prodname_dependabot_version_updates %}**—no se habilita predeterminadamente. Las personas con permisos de escritura en un repositorio pueden habilitar las {% data variables.product.prodname_dependabot_version_updates %}. Para obtener más información sobre cómo habilitar las actualizaciones de versión, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)". {% endif %} {% ifversion ghes or ghae %} - **Dependency graph** and **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Both features are configured at an enterprise level by the enterprise owner. Para obtener más información, consulta la sección {% ifversion ghes %}"[Habilitar la gráfica de dependencias para tu empresa](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" y {% endif %}"[Habilitar el {% data variables.product.prodname_dependabot %} para tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". -- **Dependency review**—available when dependency graph is enabled for {% data variables.product.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." +- **Dependency review**—available when dependency graph is enabled for {% data variables.product.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. Para obtener más información, consulta la sección "[Acerca de la {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)". {% endif %} {% ifversion ghes > 3.2 %} - **{% data variables.product.prodname_dependabot_security_updates %}**—no se habilita predeterminadamente. Puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. Para obtener más información sobre cómo habilitar las actualizaciones de seguridad, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)". 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 409595d281..f0b9ba9358 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 @@ -7,7 +7,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -44,6 +44,8 @@ The dependency graph includes all the dependencies of a repository that are deta The dependency graph identifies indirect dependencies{% ifversion fpt or ghec %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. +For more information on how {% data variables.product.product_name %} helps you understand the dependencies in your environment, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." + {% ifversion fpt or ghec %} ## Dependents included diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md index 625e4271c2..aaeb125e06 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md @@ -5,7 +5,7 @@ shortTitle: Configure dependency review versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -35,7 +35,7 @@ La revisión de dependencias se incluye en {% data variables.product.product_nam {% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %} 1. If "{% data variables.product.prodname_GH_advanced_security %}" is not enabled, click **Enable** next to the feature. ![Screenshot of GitHub Advanced Security feature with "Enable" button emphasized](/assets/images/help/security/enable-ghas-private-repo.png) -{% elsif ghes or ghae %} +{% elsif ghes %} La revisión de dependencias se encuentra disponible cuando se habilita la gráfica de dependencias de {% data variables.product.product_location %} y cuando se habilita la {% data variables.product.prodname_advanced_security %} para la organización o el repositorio. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_GH_advanced_security %} en tu empresa](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)". ### Checking if the dependency graph is enabled diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md index 383ac86645..cc60198fb1 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md @@ -6,7 +6,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -25,7 +25,7 @@ Para obtener más información, consulta la sección "[Acerca de la gráfica de {% ifversion fpt or ghec %} ## About configuring the dependency graph {% endif %} {% ifversion fpt or ghec %}Para generar una gráfica de dependencias, {% data variables.product.product_name %} necesita acceso de solo lectura a los archivos de manifiesto y de bloqueo de un repositorio. La gráfica de dependencias se genera automáticamente para todos los repositorios públicos y puedes elegir habilitarla para los privados. For more information on viewing the dependency graph, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} -{% ifversion ghes or ghae %} ## Enabling the dependency graph +{% ifversion ghes %} ## Enabling the dependency graph {% data reusables.dependabot.ghes-ghae-enabling-dependency-graph %}{% endif %}{% ifversion fpt or ghec %} ### Habilitar e inhabilitar la gráfica de dependencias para un repositorio privado @@ -38,5 +38,5 @@ Cuando la gráfica de dependencias se habilita por primera vez, cualquier manifi ## Leer más {% ifversion ghec %}- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %} -- "[Ver las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Visualizar las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Solucionar problemas en la detección de dependencias vulnerables](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)" diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index a857d0a12b..9a41314832 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -12,7 +12,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md index 1710ee55da..20737355d4 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md @@ -3,7 +3,7 @@ title: Understanding your software supply chain versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependency graph diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md index f4e8203720..e3373aaa0b 100644 --- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md +++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md @@ -5,7 +5,7 @@ shortTitle: Troubleshoot dependency graph versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md index 970f2f23f9..ecfe150b87 100644 --- a/translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md +++ b/translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md @@ -42,7 +42,7 @@ Si bien esta opción no te configura un ambiente de desarrollo, te permitirá ha ## Opción 4: Utiliza los contenedores remotos y Docker para crear un ambiente contenido local -Si tu repositorio tiene un `devcontainer.json`, considera utilizar la [extensión de contenedores remotos](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) en Visual Studio Code para crear y adjuntarlo a un contenedor de desarrollo logal para tu repositorio. El tiempo de configuración para esta opción variará dependiendo de tus especificaciones locales y de la complejidad de tu configuración de contenedor dev. +Si tu repositorio tiene un `devontainer.json`, considera utilizar la [extensión de contenedores remotos](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) en {% data variables.product.prodname_vscode %} para crear y adjuntar un contenedor de desarrollo local para tu repositorio. El tiempo de configuración para esta opción variará dependiendo de tus especificaciones locales y de la complejidad de tu configuración de contenedor dev. {% note %} diff --git a/translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md index 3befa2d4ac..a3f28fe184 100644 --- a/translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md +++ b/translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md @@ -34,7 +34,7 @@ Cada codespace tiene su propia red virtual aislada. Utilizamos cortafuegos para ### Autenticación -Puedes conectarte a un codespace utilizando un buscador web o desde Visual Studio Code. Si te conectas desde Visual Studio Code, se te pedirá autenticarte con {% data variables.product.product_name %}. +You can connect to a codespace using a web browser or from {% data variables.product.prodname_vscode %}. If you connect from {% data variables.product.prodname_vscode_shortname %}, you are prompted to authenticate with {% data variables.product.product_name %}. Cada vez que se cree o reinicie un codespace, se le asignará un token de {% data variables.product.company_short %} nuevo con un periodo de vencimiento automático. Este periodo te permite trabajar en el codespace sin necesitar volver a autenticarte durante un día de trabajo habitual, pero reduce la oportunidad de que dejes la conexión abierta cuando dejas de utilizar el codespace. @@ -109,4 +109,4 @@ Ciertas características de desarrollo pueden agregar riesgos a tu ambiente pote #### Utilizar extensiones -Cualquier extensión adicional de {% data variables.product.prodname_vscode %} que hayas instalado puede introducir más riesgos potencialmente. Para ayudar a mitigar este riesgo, asegúrate de que solo instales extensiones confiables y de que siempre se mantengan actualizadas. +Cualquier extensión adicional de {% data variables.product.prodname_vscode_shortname %} que hayas instalado puede introducir más riesgos potencialmente. Para ayudar a mitigar este riesgo, asegúrate de que solo instales extensiones confiables y de que siempre se mantengan actualizadas. diff --git a/translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md index 84c96ff8a0..ec782fa8ab 100644 --- a/translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md +++ b/translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md @@ -17,7 +17,7 @@ redirect_from: ## Uso de {% data variables.product.prodname_copilot %} -[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), un programador de par de IA, puede utilizarse en cualquier codespace. Para comenzar a utilizar el {% data variables.product.prodname_copilot_short %} en {% data variables.product.prodname_codespaces %} instala la [extensión de {% data variables.product.prodname_copilot_short %} desde el mercado de {% data variables.product.prodname_vscode %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). +[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), un programador de par de IA, puede utilizarse en cualquier codespace. To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). Para incluir al {% data variables.product.prodname_copilot_short %} u otras extensiones en tus codespaces, habilita la sincronización de ajustes. Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)". Adicionalmente, para incluir al {% data variables.product.prodname_copilot_short %} en algún proyecto específico para todos los usuarios, puedes especificar `GitHub.copilot` como una extensión en tu archivo de `devcontainer.json`. For information about configuring a `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)." diff --git a/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md index 0411830ce2..4f4daa048e 100644 --- a/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md +++ b/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md @@ -15,13 +15,13 @@ redirect_from: - /codespaces/codespaces-reference/using-the-command-palette-in-codespaces --- -## Acerca de la Paleta de Comandos de {% data variables.product.prodname_vscode %} +## Acerca de {% data variables.product.prodname_vscode_command_palette %} -La paleta de comandos es una de las características focales de {% data variables.product.prodname_vscode %} y está disponible para que la utilices en Codespaces. La {% data variables.product.prodname_vscode_command_palette %} te permite acceder a muchos comandos para {% data variables.product.prodname_codespaces %} y {% data variables.product.prodname_vscode %}. Para obtener más información sobre cómo utilizar la {% data variables.product.prodname_vscode_command_palette %}, consulta la sección "[Interfaz de usuario](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" en la documentación de Visual Studio Code. +La paleta de comandos es una de las características focales de {% data variables.product.prodname_vscode %} y está disponible para que la utilices en Codespaces. La {% data variables.product.prodname_vscode_command_palette %} te permite acceder a muchos comandos para {% data variables.product.prodname_codespaces %} y {% data variables.product.prodname_vscode_shortname %}. For more information on using the {% data variables.product.prodname_vscode_command_palette_shortname %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the {% data variables.product.prodname_vscode_shortname %} documentation. -## Acceder a la {% data variables.product.prodname_vscode_command_palette %} +## Acceder a la {% data variables.product.prodname_vscode_command_palette_shortname %} -Puedes acceder a la {% data variables.product.prodname_vscode_command_palette %} de varias formas. +Puedes acceder a la {% data variables.product.prodname_vscode_command_palette_shortname %} de varias formas. - Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux). @@ -33,7 +33,7 @@ Puedes acceder a la {% data variables.product.prodname_vscode_command_palette %} ## Comandos para los {% data variables.product.prodname_github_codespaces %} -Para ver todos los comandos relacionados con {% data variables.product.prodname_github_codespaces %}, [accede a la {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette) y luego comienza a teclear "Codespaces". +Para ver todos los comandos relacionados con {% data variables.product.prodname_github_codespaces %}, [accede a la {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette) y luego comienza a teclear "Codespaces". ![Una lista de todos los comandos que se relacionan con los codespaces](/assets/images/help/codespaces/codespaces-command-palette.png) @@ -41,13 +41,13 @@ Para ver todos los comandos relacionados con {% data variables.product.prodname_ Si agregas un secreto nuevo o cambias el tipo de máquina, tendrás que detener y reiniciar el codespace para que aplique tus cambios. -Para suspender o detener el contenedor de tu codespace [accede a la {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette) y luego comienza a teclear "stop". Selecciona **Codespaces: Detener el codespace actual**. +Para suspender o detener el contenedor de tu codespace [accede a la {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette) y luego comienza a teclear "stop". Selecciona **Codespaces: Detener el codespace actual**. ![Comando para detner un codespace](/assets/images/help/codespaces/codespaces-stop.png) ### Agregar un contenedor de dev desde una plantilla -Para agregar un contenedor dev a una plantilla, [accede a la {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette) y luego comienza a teclear "dev container". Selecciona **Codespaces: Agregar archivos de configuración del contenedor de desarrollo...** +Para agregar un contenedor dev a una plantilla, [accede a la {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette) y luego comienza a teclear "dev container". Selecciona **Codespaces: Agregar archivos de configuración del contenedor de desarrollo...** ![Comando para agregar un contenedor de dev](/assets/images/help/codespaces/add-prebuilt-container-command.png) @@ -55,14 +55,14 @@ Para agregar un contenedor dev a una plantilla, [accede a la {% data variables.p Si agregas un contenedor de dev o si editas cualquiera de los archivos de configuración (`devcontainer.json` y `Dockerfile`), tendrás que reconstruir tu codespace para que este aplique tus cambios. -Para recompilar tu contenedor, [accede a la {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette) y luego comienza a teclear "recompilar". Selecciona **Codespaces: Reconstruir contenedor**. +Para recompilar tu contenedor, [accede a la {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette) y luego comienza a teclear "recompilar". Selecciona **Codespaces: Reconstruir contenedor**. ![Comando para reconstruir un codespace](/assets/images/help/codespaces/codespaces-rebuild.png) ### Bitácoras de los codespaces -Puedes utilizar la {% data variables.product.prodname_vscode_command_palette %} para acceder a las bitácoras de creación de codespaces o puedes utilizarla para exportar todas las bitácoras. +Puedes utilizar la {% data variables.product.prodname_vscode_command_palette_shortname %} para acceder a las bitácoras de creación de codespaces o puedes utilizarla para exportar todas las bitácoras. -Para recuperar las bitácoras para Codespaces, [accede a la {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette) y luego comienza a teclear "log". Selecciona **Codespaces: Exportar bitácoras** para exportar todas las bitácoras relacionadas con los codespaces o selecciona **Codespaces: Ver las bitácoras de creación** para ver las bitácoras relacionadas con la configuración. +Para recuperar las bitácoras para Codespaces, [accede a la {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette) y luego comienza a teclear "log". Selecciona **Codespaces: Exportar bitácoras** para exportar todas las bitácoras relacionadas con los codespaces o selecciona **Codespaces: Ver las bitácoras de creación** para ver las bitácoras relacionadas con la configuración. ![Comando para acceder a las bitácoras](/assets/images/help/codespaces/codespaces-logs.png) diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 59b5feb5ad..835fe5912a 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -35,7 +35,7 @@ For more information on what happens when you create a codespace, see "[Deep Div For more information on the lifecycle of a codespace, see "[Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)." -If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the Visual Studio Code documentation. +If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.codespaces.use-visual-studio-features %} diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md index a985c3a36c..ff505fbe49 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md @@ -33,7 +33,7 @@ shortTitle: Develop in a codespace 4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal. 5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more. -For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation. +For more information on using {% data variables.product.prodname_vscode_shortname %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.codespaces.connect-to-codespace-from-vscode %} @@ -54,7 +54,7 @@ For more information on using {% data variables.product.prodname_vscode %}, see ### Using the {% data variables.product.prodname_vscode_command_palette %} -The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)." +The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette_shortname %} in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)." ## Navigating to an existing codespace diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md index 59eb5ed129..3b81563de2 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md @@ -20,17 +20,17 @@ shortTitle: Visual Studio Code ## About {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %} -You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. To use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}, you need to install the {% data variables.product.prodname_github_codespaces %} extension. For more information on setting up Codespaces in {% data variables.product.prodname_vscode %}, see "[Prerequisites](#prerequisites)." +You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. To use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode_shortname %}, you need to install the {% data variables.product.prodname_github_codespaces %} extension. For more information on setting up Codespaces in {% data variables.product.prodname_vscode_shortname %}, see "[Prerequisites](#prerequisites)." -By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." +By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode_shortname %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." -If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." +If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode_shortname %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." ## Prerequisites -To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. +To develop in a codespace directly in {% data variables.product.prodname_vscode_shortname %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode_shortname %} October 2020 Release 1.51 or later. -Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode %} documentation. +Use the {% data variables.product.prodname_vscode_marketplace %} to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% mac %} @@ -40,8 +40,8 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. -1. Sign in to {% data variables.product.product_name %} to approve the extension. +2. To authorize {% data variables.product.prodname_vscode_shortname %} to access your account on {% data variables.product.product_name %}, click **Allow**. +3. Sign in to {% data variables.product.product_name %} to approve the extension. {% endmac %} @@ -56,28 +56,28 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. +1. To authorize {% data variables.product.prodname_vscode_shortname %} to access your account on {% data variables.product.product_name %}, click **Allow**. 1. Sign in to {% data variables.product.product_name %} to approve the extension. {% endwindows %} -## Creating a codespace in {% data variables.product.prodname_vscode %} +## Creating a codespace in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.creating-a-codespace-in-vscode %} -## Opening a codespace in {% data variables.product.prodname_vscode %} +## Opening a codespace in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 1. Under "Codespaces", click the codespace you want to develop in. 1. Click the Connect to Codespace icon. - ![The Connect to Codespace icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) + ![The Connect to Codespace icon in {% data variables.product.prodname_vscode_shortname %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) -## Changing the machine type in {% data variables.product.prodname_vscode %} +## Changing the machine type in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.codespaces-machine-types %} You can change the machine type of your codespace at any time. -1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`). +1. In {% data variables.product.prodname_vscode_shortname %}, open the Command Palette (`shift command P` / `shift control P`). 1. Search for and select "Codespaces: Change Machine Type." ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png) @@ -100,13 +100,13 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts. -## Deleting a codespace in {% data variables.product.prodname_vscode %} +## Deleting a codespace in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.deleting-a-codespace-in-vscode %} -## Switching to the Insiders build of {% data variables.product.prodname_vscode %} +## Switching to the Insiders build of {% data variables.product.prodname_vscode_shortname %} -You can use the [Insiders Build of Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_codespaces %}. +You can use the [Insiders Build of {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_codespaces %}. 1. In bottom left of your {% data variables.product.prodname_codespaces %} window, select **{% octicon "gear" aria-label="The settings icon" %} Settings**. 2. From the list, select "Switch to Insiders Version". diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md index 089a99a913..68efad7449 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md @@ -24,6 +24,7 @@ You can work with {% data variables.product.prodname_codespaces %} in the {% da - [Delete a codespace](#delete-a-codespace) - [SSH into a codespace](#ssh-into-a-codespace) - [Open a codespace in {% data variables.product.prodname_vscode %}](#open-a-codespace-in-visual-studio-code) +- [Open a codespace in JupyterLab](#open-a-codespace-in-jupyterlab) - [Copying a file to/from a codespace](#copy-a-file-tofrom-a-codespace) - [Modify ports in a codespace](#modify-ports-in-a-codespace) - [Access codespace logs](#access-codespace-logs) @@ -113,6 +114,12 @@ gh codespace code -c codespace-name For more information, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code)." +### Open a codespace in JupyterLab + +```shell +gh codespace jupyter -c codespace-name +``` + ### Copy a file to/from a codespace ```shell diff --git a/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md index 3d090f0bd8..05f97e8e7f 100644 --- a/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ b/translations/es-ES/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md @@ -19,7 +19,7 @@ shortTitle: Control origen Puedes llevar a cabo todas las acciones de Git que necesites directamente dentro de tu codespace. Por ejemplo, puedes recuperar cambios del repositorio remoto, cambiar de rama, crear una rama nueva, confirmar y subir cambios y crear solicitudes de cambios. Puedes utilizar la terminal integrada dentro de tu codespace para ingresar comandos de Git o puedes hacer clic en los iconos u opciones de menú para completar las tareas más comunes de Git. Esta guía te explica cómo utilizar la interface de usuario gráfica para el control de código fuente. -El control de fuentes en {% data variables.product.prodname_github_codespaces %} utiliza el mismo flujo de trabajo que {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la sección de la documentación de {% data variables.product.prodname_vscode %} "[Utilizar el control de versiones en VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)". +El control de fuentes en {% data variables.product.prodname_github_codespaces %} utiliza el mismo flujo de trabajo que {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la documentación de {% data variables.product.prodname_vscode_shortname %} en la sección "[Utilizar el control de versiones en {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)". Un flujo de trabajo típico para actualizar un archivo utilizando {% data variables.product.prodname_github_codespaces %} sería: diff --git a/translations/es-ES/content/codespaces/getting-started/deep-dive.md b/translations/es-ES/content/codespaces/getting-started/deep-dive.md index b35a0dd68a..47f78fb947 100644 --- a/translations/es-ES/content/codespaces/getting-started/deep-dive.md +++ b/translations/es-ES/content/codespaces/getting-started/deep-dive.md @@ -46,13 +46,13 @@ Since your repository is cloned onto the host VM before the container is created ### Step 3: Connecting to the codespace -When your container has been created and any other initialization has run, you'll be connected to your codespace. You can connect to it through the web or via [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed. +When your container has been created and any other initialization has run, you'll be connected to your codespace. You can connect to it through the web or via [{% data variables.product.prodname_vscode_shortname %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed. ### Step 4: Post-creation setup Once you are connected to your codespace, your automated setup may continue to build based on the configuration you specified in your `devcontainer.json` file. You may see `postCreateCommand` and `postAttachCommand` run. -If you want to use Git hooks in your codespace, set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the Visual Studio Code documentation. +If you want to use Git hooks in your codespace, set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. If you have a public dotfiles repository for {% data variables.product.prodname_codespaces %}, you can enable it for use with new codespaces. When enabled, your dotfiles will be cloned to the container and the install script will be invoked. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)." @@ -67,7 +67,7 @@ As you develop in your codespace, it will save any changes to your files every f {% note %} -**Note:** Changes in a codespace in {% data variables.product.prodname_vscode %} are not saved automatically, unless you have enabled [Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). +**Note:** Changes in a codespace in {% data variables.product.prodname_vscode_shortname %} are not saved automatically, unless you have enabled [Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). {% endnote %} ### Closing or stopping your codespace @@ -93,7 +93,7 @@ Running your application when you first land in your codespace can make for a fa ## Committing and pushing your changes -Git is available by default in your codespace and so you can rely on your existing Git workflow. You can work with Git in your codespace either via the Terminal or by using [Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" +Git is available by default in your codespace and so you can rely on your existing Git workflow. You can work with Git in your codespace either via the Terminal or by using [{% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" ![Running git status in Codespaces Terminal](/assets/images/help/codespaces/git-status.png) @@ -107,9 +107,9 @@ You can create a codespace from any branch, commit, or pull request in your proj ## Personalizing your codespace with extensions -Using {% data variables.product.prodname_vscode %} in your codespace gives you access to the {% data variables.product.prodname_vscode %} Marketplace so that you can add any extensions you need. For information on how extensions run in {% data variables.product.prodname_codespaces %}, see [Supporting Remote Development and GitHub Codespaces](https://code.visualstudio.com/api/advanced-topics/remote-extensions) in the {% data variables.product.prodname_vscode %} docs. +Using {% data variables.product.prodname_vscode_shortname %} in your codespace gives you access to the {% data variables.product.prodname_vscode_marketplace %} so that you can add any extensions you need. For information on how extensions run in {% data variables.product.prodname_codespaces %}, see [Supporting Remote Development and GitHub Codespaces](https://code.visualstudio.com/api/advanced-topics/remote-extensions) in the {% data variables.product.prodname_vscode_shortname %} docs. -If you already use {% data variables.product.prodname_vscode %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to automatically sync extensions, settings, themes, and keyboard shortcuts between your local instance and any {% data variables.product.prodname_codespaces %} you create. +If you already use {% data variables.product.prodname_vscode_shortname %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to automatically sync extensions, settings, themes, and keyboard shortcuts between your local instance and any {% data variables.product.prodname_codespaces %} you create. ## Further reading diff --git a/translations/es-ES/content/codespaces/getting-started/quickstart.md b/translations/es-ES/content/codespaces/getting-started/quickstart.md index 34c97a07b0..d6564071cc 100644 --- a/translations/es-ES/content/codespaces/getting-started/quickstart.md +++ b/translations/es-ES/content/codespaces/getting-started/quickstart.md @@ -72,7 +72,7 @@ Ahora que hiciste algunos cambios, puedes utilizar la terminal integrada o la vi ## Personalizar con una extensión -Dentro de un codespace, tienes acceso al Visual Studio Code Marketplace. Para este ejemplo, instalarás una extensión que altera el tema, pero puedes instalar cualquier extensión que sea útil para tu flujo de trabajo. +Within a codespace, you have access to the {% data variables.product.prodname_vscode_marketplace %}. Para este ejemplo, instalarás una extensión que altera el tema, pero puedes instalar cualquier extensión que sea útil para tu flujo de trabajo. 1. En la barra lateral, haz clic en el icono de extensiones. @@ -84,7 +84,7 @@ Dentro de un codespace, tienes acceso al Visual Studio Code Marketplace. Para es ![Seleccionar el tema de fairyfloss](/assets/images/help/codespaces/fairyfloss.png) -4. Los cambios que hagas en la configuración de tu editor en el codespace actual, tales como el tema y las uniones de teclado, se sincronizarán automáticamente a través de [la Syncronización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync) en cualquier otro codespace que abras y en cualquier instancia de Visual Studio Code que se firmen en tu cuenta de GitHub. +4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to any other codespaces you open and any instances of {% data variables.product.prodname_vscode %} that are signed into your GitHub account. ## Siguientes pasos diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md index 086ebf1156..15a5b95df1 100644 --- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md +++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md @@ -41,7 +41,7 @@ Puedes limitar la elección de tipos de máquina que se encuentra disponible par ## Borrar los codespaces sin utilizar -Tus usuarios pueden borrar sus codespaces en https://github.com/codespaces y desde dentro de Visual Studio Code. Para reducir el tamaño de un codespace, los usuarios pueden borrar archivos manualmente en la terminal o desde Visual Studio Code. +Your users can delete their codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, users can manually delete files using the terminal or from within {% data variables.product.prodname_vscode_shortname %}. {% note %} diff --git a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md index aa79016944..5f54837d95 100644 --- a/translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md +++ b/translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md @@ -1,8 +1,8 @@ --- -title: Administrar el acceso a otros repositorios dentro de tu codespace +title: Managing access to other repositories within your codespace allowTitleToDifferFromFilename: true -shortTitle: Acceso a los repositorios -intro: 'Puedes administrar los repositorios a los cuales pueden acceder los {% data variables.product.prodname_codespaces %}.' +shortTitle: Repository access +intro: 'You can manage the repositories that {% data variables.product.prodname_codespaces %} can access.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -14,24 +14,24 @@ redirect_from: - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces --- -## Resumen +## Overview -Predeterminadamente, a tu codespace se le asigna un token con alcance del repositorio del cual se creó. Para obtener más información, consulta la sección "[Seguridad en {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/security-in-codespaces#authentication)". Si tu proyecto necesita permisos adicionales para otros repositorios, puedes configurar esto en el archivo `devcontainer.json` y asegurarte de que otros colaboradores tengan el conjunto de permisos correcto. +By default, your codespace is assigned a token scoped to the repository from which it was created. For more information, see "[Security in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/security-in-codespaces#authentication)." If your project needs additional permissions for other repositories, you can configure this in the `devcontainer.json` file and ensure other collaborators have the right set of permissions. -Cuando los permisos se listan en el archivo `devcontainer.json`, se te pedirá revisar y autorizar los permisos adicionales como parte de la creación de codespaces para dicho repositorio. Una vez que autorizas los permisos listados, {% data variables.product.prodname_github_codespaces %} recordará tu elección y no te pedirá autorización amenos de que cambien los permisos en el archivo `devcontainer.json`. +When permissions are listed in the `devcontainer.json` file, you will be prompted to review and authorize the additional permissions as part of codespace creation for that repository. Once you've authorized the listed permissions, {% data variables.product.prodname_github_codespaces %} will remember your choice and will not prompt you for authorization unless the permissions in the `devcontainer.json` file change. -## Prerrequisitos +## Prerequisites -Para crear codespaces con permisos personalizados definidos, debes utilizar uno de los siguientes: -* La IU web de {% data variables.product.prodname_dotcom %} -* [{% data variables.product.prodname_dotcom %} CLI](https://github.com/cli/cli/releases/latest) 2.5.2 o posterior -* [{% data variables.product.prodname_github_codespaces %} extensión de Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 o posterior +To create codespaces with custom permissions defined, you must use one of the following: +* The {% data variables.product.prodname_dotcom %} web UI +* [{% data variables.product.prodname_dotcom %} CLI](https://github.com/cli/cli/releases/latest) 2.5.2 or later +* [{% data variables.product.prodname_github_codespaces %} {% data variables.product.prodname_vscode %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 or later -## Configurar los permisos adicionales de los repositorios +## Setting additional repository permissions -1. Puedes configurar los permisos de repositorio para {% data variables.product.prodname_github_codespaces %} en el archivo `devcontainer.json`. Si tu repositorio no contiene ya un archivo `devcontainer.json`, agrégalo ahora. Para obtener màs informaciòn, "[Agrega un contenedor dev a tu proyecto](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)". +1. You configure repository permissions for {% data variables.product.prodname_github_codespaces %} in the `devcontainer.json` file. If your repository does not already contain a `devcontainer.json` file, add one now. For more information, "[Add a dev container to your project](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)." -1. Edita el archivo `devcontainer.json` agregando el nombre de repositorio y los permisos necesarios al objeto `repositories`: +1. Edit the `devcontainer.json` file, adding the repository name and permissions needed to the `repositories` object: ```json{:copy} { @@ -51,25 +51,25 @@ Para crear codespaces con permisos personalizados definidos, debes utilizar uno {% note %} - **Nota:** Solo puedes referenciar los repositorios que pertenecen a la misma cuenta personal o de organización que el repositorio en el que estás trabajando actualmente. + **Note:** You can only reference repositories that belong to the same personal account or organization as the repository you are currently working in. {% endnote %} - Puedes otorgar tantos o tan pocos de los permisos siguientes como quieras para cada repositorio listado: - * `actions` - lectura / escritura - * `checks` - lectura / escritura - * `contents` - lectura / escritura - * `deployments` - lectura / escritura - * `discussions` - lectura / escritura - * `issues` - lectura / escritura + You can grant as many or as few of the following permissions for each repository listed: + * `actions` - read / write + * `checks` - read / write + * `contents` - read / write + * `deployments` - read / write + * `discussions` - read / write + * `issues` - read / write * `packages` - read - * `pages` - lectura / escritura - * `pull_requests` - lectura / escritura - * `repository_projects` - lectura / escritura - * `statuses` - lectura / escritura - * `workflows` - escritura + * `pages` - read / write + * `pull_requests` - read / write + * `repository_projects` - read / write + * `statuses` - read / write + * `workflows` - write - Para configurar un permiso para todos los repositorios de una organización, utiliza el comodín `*` seguido de tu nombre de organización en el objeto `repositories`. + To set a permission for all repositories in an organization, use the `*` wildcard following your organization name in the `repositories` object. ```json { @@ -103,36 +103,36 @@ Para crear codespaces con permisos personalizados definidos, debes utilizar uno } ``` -## Autorizar los permisos solicitados +## Authorizing requested permissions -Si se definen permisos de repositorio adicionales en el archivo `devcontainer.json`, se te pedirá revisar y, opcionalmente, autorizar los permisos cuando crees un codespace para este repositorio. Cuando autorizas permisos para un repositorio, {% data variables.product.prodname_github_codespaces %} no volverá a enviar mensajes a menos de que el conjunto de permisos solicitados haya cambiado para el repositorio. +If additional repository permissions are defined in the `devcontainer.json` file, you will be prompted to review and optionally authorize the permissions when you create a codespace for this repository. When you authorize permissions for a repository, {% data variables.product.prodname_github_codespaces %} will not re-prompt you unless the set of requested permissions has changed for the repository. -![La página de permisos solicitados](/assets/images/help/codespaces/codespaces-accept-permissions.png) +![The requested permissions page](/assets/images/help/codespaces/codespaces-accept-permissions.png) -Solo deberías autorizar los permisos para los repositorios que conoces y en los cuales confías. Si no confías en el conjunto de permisos solicitados, haz clic en **Continuar sin autorizar** para crear el codespace con el conjunto de permisos base. El rechazar permisos adicionales podría impactar la funcionalidad de tu proyecto dentro del codespace, ya que este codespace solo tendrá acceso al repositorio desde el cuál se creó. +You should only authorize permissions for repositories you know and trust. If you don't trust the set of requested permissions, click **Continue without authorizing** to create the codespace with the base set of permissions. Rejecting additional permissions may impact the functionality of your project within the codespace as the codespace will only have access to the repository from which it was created. -Solo puedes autorizar los permisos que tu cuenta personal ya posea. Si un codespace solicita permisos para los repositorios a los cuales no tienes acceso actualmente, contacta a un propietario o administrador del repositorio para obtener suficiente acceso y luego intenta crear un codespace nuevamente. +You can only authorize permissions that your personal account already possesses. If a codespace requests permissions for repositories that you don't currently have access to, contact an owner or admin of the repository to obtain sufficient access and then try to create a codespace again. -## Acceso y seguridad +## Access and security {% warning %} -**Aviso de obsolesencia**: El acceso y ajuste de seguridad, en la sección de {% data variables.product.prodname_codespaces %} de los ajustes de tu cuenta personal, ahora es obsoleto. Para habilitar un acceso expandido a otros repositorios, agrega los permisos solicitados a tu definición de contenedor dev para tu codespace, tal como se describe anteriormente. +**Deprecation note**: The access and security setting, in the {% data variables.product.prodname_codespaces %} section of your personal account settings, is now deprecated. To enable expanded access to other repositories, add the requested permissions to your dev container definition for your codespace, as described above. {% endwarning %} -Cuando habilitas el acceso y la seguridad para un repositorio que le pertenece a tu cuenta personal, cualquier codespace que se cree para dicho repositorio tendrá permisos de lectura para todos los otros repositorios que te pertenezcan. Si quieres restringir los repositorios a los que puede acceder un codespace, puedes limitarlos a ya sea el repositorio para el cual se abrió el codespace o a repositorios específicos. Solo debes habilitar el acceso y la seguridad para los repositorios en los cuales confíes. +When you enable access and security for a repository owned by your personal account, any codespaces that are created for that repository will have read permissions to all other repositories you own. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository the codespace was opened for or specific repositories. You should only enable access and security for repositories you trust. {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.codespaces-tab %} -1. Debajo de "Acceso y seguridad", selecciona el ajuste que quieras para tu cuenta personal. +1. Under "Access and security", select the setting you want for your personal account. - ![Botones radiales para adminsitrar los repositorios confiables](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) + ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png) -1. Si eliges "Repositorios seleccionados", selecciona el menú desplegable y luego da clic en un repositorio para permitir que los codespaces de éste accedan al resto de los repositorios que te pertenecen. Repite esto para todos los repositorios cuyos codespaces quieras que accedan al resto de tus repositorios. +1. If you chose "Selected repositories", select the drop-down menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own. - ![Menú desplegable de "Repositorios seleccionados"](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) + !["Selected repositories" drop-down menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png) -## Leer más +## Further reading -- "[Administrar el acceso a los repositorios para los codespaces de tu organización](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)" +- "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)" diff --git a/translations/es-ES/content/codespaces/overview.md b/translations/es-ES/content/codespaces/overview.md index 5dd8184961..88e16eb473 100644 --- a/translations/es-ES/content/codespaces/overview.md +++ b/translations/es-ES/content/codespaces/overview.md @@ -34,7 +34,7 @@ To customize the runtimes and tools in your codespace, you can create one or mor If you don't add a dev container configuration, {% data variables.product.prodname_codespaces %} will clone your repository into an environment with the default codespace image that includes many tools, languages, and runtime environments. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". -You can also personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and VS Code extensions. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)". +You can also personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and {% data variables.product.prodname_vscode_shortname %} extensions. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)". ## About billing for {% data variables.product.prodname_codespaces %} diff --git a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md index 723acd7f8e..dafc1317e2 100644 --- a/translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md +++ b/translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md @@ -94,7 +94,7 @@ Prebuilds do not use any user-level secrets while building your environment, bec ## Configuring time-consuming tasks to be included in the prebuild -You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild template creation. For more information, see the Visual Studio Code documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)." +You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild template creation. For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)." `onCreateCommand` is run only once, when the prebuild template is created, whereas `updateContentCommand` is run at template creation and at subsequent template updates. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild template update. diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md index 3e1090accc..0c8afd3d1b 100644 --- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md +++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md @@ -110,7 +110,7 @@ Para utilizar un Dockerfile como parte de una configuración de contenedor dev, } ``` -Para obtener más información sobre cómo utilizar un Dockerfile en una configuración de contenedor dev, consulta la documentación de {% data variables.product.prodname_vscode %} "[Crear un contenedor de desarrollo](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)". +For more information about using a Dockerfile in a dev container configuration, see the {% data variables.product.prodname_vscode_shortname %} documentation "[Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)." ## Utilizar la configuración de contenedor dev predeterminada @@ -122,7 +122,7 @@ La configuración predeterminada es una buena opción si estás trabajando en un ## Utilizar una configuración predeterminada de contenedor dev -Puedes elegir de entre una lista de configuraciones predeterminadas para crear una configuración de contenedor dev para tu repositorio. Estas configuraciones proporcionan ajustes comunes para tipos de proyecto particulares y pueden ayudarte a iniciar rápidamente con una configuración que ya tenga las opciones de contenedor, ajustes de {% data variables.product.prodname_vscode %} y extensiones de {% data variables.product.prodname_vscode %} que deberían instalarse. +Puedes elegir de entre una lista de configuraciones predeterminadas para crear una configuración de contenedor dev para tu repositorio. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode_shortname %} settings, and {% data variables.product.prodname_vscode_shortname %} extensions that should be installed. Utilizar una configuración predefinida es una gran idea si necesitas extensibilidad adicional. También puedes comenzar con una configuración predeterminada y modificarla conforme la necesites para tu proyecto. @@ -192,9 +192,9 @@ Si existe el archivo `.devcontainer/devcontainer.json` o `.devcontainer.json`, e ### Editar el archivo devcontainer.json -Puedes agregar y editar las claves de configuración compatibles en el archivo `devcontainer.json` para especificar los aspectos del ambiente del codespace, como qué extensiones de {% data variables.product.prodname_vscode %} se instalarán. {% data reusables.codespaces.more-info-devcontainer %} +You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode_shortname %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %} -El archivo de `devcontainer.json` se escribe utilizando el formato JSONC. Esto te permite incluir comentarios dentro del archivo de configuración. For more information, see "[Editing JSON with Visual Studio Code](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode %} documentation. +El archivo de `devcontainer.json` se escribe utilizando el formato JSONC. Esto te permite incluir comentarios dentro del archivo de configuración. For more information, see "[Editing JSON with {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% note %} @@ -202,11 +202,11 @@ El archivo de `devcontainer.json` se escribe utilizando el formato JSONC. Esto t {% endnote %} -### Editor settings for Visual Studio Code +### Editor settings for {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.vscode-settings-order %} -Puedes definir la configuración predeterminada del editor para {% data variables.product.prodname_vscode %} en dos lugares. +You can define default editor settings for {% data variables.product.prodname_vscode_shortname %} in two places. * Editor settings defined in the `.vscode/settings.json` file in your repository are applied as _Workspace_-scoped settings in the codespace. * Editor settings defined in the `settings` key in the `devcontainer.json` file are applied as _Remote [Codespaces]_-scoped settings in the codespace. diff --git a/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md b/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md index 49ffb9cf91..b2e751ef1b 100644 --- a/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md +++ b/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md @@ -27,7 +27,7 @@ El {% data variables.product.prodname_serverless %} presenta una experiencia de El {% data variables.product.prodname_serverless %} se encuentra disponible gratuitamente para todos en {% data variables.product.prodname_dotcom_the_website %}. -El {% data variables.product.prodname_serverless %} proporciona muchos de los beneficios de {% data variables.product.prodname_vscode %}, tales como búsqueda, resaltado de sintaxis y vista de control de código fuente. También puedes utilizar la Sincronización de Ajustes para compartir tus propios ajustes de {% data variables.product.prodname_vscode %} con el editor. Para obtener más información, consulta la sección de "[Sincronización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync)" en la documentación de {% data variables.product.prodname_vscode %}. +El {% data variables.product.prodname_serverless %} proporciona muchos de los beneficios de {% data variables.product.prodname_vscode %}, tales como búsqueda, resaltado de sintaxis y vista de control de código fuente. También puedes utilizar la Sincronización de Ajustes para compartir tus propios ajustes de {% data variables.product.prodname_vscode_shortname %} con el editor. Para obtener más información, consulta la sección de "[Sincronización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync)" en la documentación de {% data variables.product.prodname_vscode_shortname %}. El {% data variables.product.prodname_serverless %} se ejecuta completamente en el área de pruebas de tu buscador. El editor no clona el repositorio, sino que utiliza la [extensión de repositorios de GitHub](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) para llevar a cabo la mayoría de la funcionalidad que utilizarás. Tu trabajo se guarda en el almacenamiento local de tu buscador hasta que lo confirmes. Debes confirmar tus cambios frecuentemente para asegurarte de que siempre sean accesibles. @@ -49,7 +49,7 @@ Tanto el {% data variables.product.prodname_serverless %} como los {% data varia | **Inicio** | El {% data variables.product.prodname_serverless %} se abre instantáneamente al presionar una tecla y puedes comenzar a usarlo de inmediato sin tener que esperar por configuraciones o instalaciones adicionales. | Cuando creas o reanudas un codespace, a este se le asigna una MV y el contenedor se configura con base ene l contenido de un archivo de `devcontainer.json`. Esta configuración puede tomar algunos minutos para crear el ambiente. Para obtener más información, consulta la sección "[Crear un Codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". | | **Cálculo** | No hay cálculos asociados, así que no podrás compilar y ejecutar tu código ni utilizar la terminal integrada. | Con {% data variables.product.prodname_codespaces %}, obtienes el poder de la MV dedicada en ela que ejecutas y depuras tu aplicación. | | **Acceso a la terminal** | Ninguno. | {% data variables.product.prodname_codespaces %} proporciona un conjunto común de herramientas predeterminadamente, lo que significa que puedes utilizar la terminal como lo harías en tu ambiente local. | -| **Extensiones** | Solo un subconjunto de extensiones que pueden ejecutarse en la web aparecerá en la Vista de Extensiones y podrá instalarse. Para obtener más información, consulta la sección "[Utilizar las extensiones](#using-extensions)". | Con los Codespaces, puedes utilizar más extensiones desde el Mercado de Visual Studio Code. | +| **Extensiones** | Solo un subconjunto de extensiones que pueden ejecutarse en la web aparecerá en la Vista de Extensiones y podrá instalarse. Para obtener más información, consulta la sección "[Utilizar las extensiones](#using-extensions)". | With Codespaces, you can use most extensions from the {% data variables.product.prodname_vscode_marketplace %}. | ### Seguir trabajando en {% data variables.product.prodname_codespaces %} @@ -61,9 +61,9 @@ Para seguir trabajando en un codespace, haz clic en **Seguir trabajando en…** ## Utilizar el control de código fuente -Cuando utilizas el {% data variables.product.prodname_serverless %}, todas las acciones se administran a través de la Vista de Control de Código Fuente, la cual se ubica en la barra de actividad en la parte izquierda. Para obtener más información sobre la Vista de Control de Código Fuente, consulta la sección "[Control de versiones](https://code.visualstudio.com/docs/editor/versioncontrol)" en la documentación de {% data variables.product.prodname_vscode %}. +Cuando utilizas el {% data variables.product.prodname_serverless %}, todas las acciones se administran a través de la Vista de Control de Código Fuente, la cual se ubica en la barra de actividad en la parte izquierda. Para obtener más información sobre la Vista de Control de Código Fuente, consulta la sección "[Control de versiones](https://code.visualstudio.com/docs/editor/versioncontrol)" en la documentación de {% data variables.product.prodname_vscode_shortname %}. -Ya que el editor basado en web utiliza la extensión de repositorios de GitHub para alimentar su funcionalidad, puedes cambiar de rama sin necesidad de acumular cambios. Para obtener más información, consulta la sección "[Repositorios de GitHub](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" en la documentación de {% data variables.product.prodname_vscode %}. +Ya que el editor basado en web utiliza la extensión de repositorios de GitHub para alimentar su funcionalidad, puedes cambiar de rama sin necesidad de acumular cambios. Para obtener más información, consulta la sección "[Repositorios de GitHub](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" en la documentación de {% data variables.product.prodname_vscode_shortname %}. ### Crear una rama nueva @@ -88,9 +88,9 @@ Puedes utilizar el {% data variables.product.prodname_serverless %} para trabaja ## Utilizar extensiones -El {% data variables.product.prodname_serverless %} es compatible con las extensiones de {% data variables.product.prodname_vscode %} que se hayan creado o actualizado específicamente para ejecutarse en la web. A estas extensiones se les conoce como "extensiones web". Para aprender cómo puedes crear una extensión web o actualizar la existente para que funcione en la web, consulta la sección de "[Extensiones web](https://code.visualstudio.com/api/extension-guides/web-extensions)" en la documnetación de {% data variables.product.prodname_vscode %}. +El {% data variables.product.prodname_serverless %} es compatible con las extensiones de {% data variables.product.prodname_vscode_shortname %} que se hayan creado o actualizado específicamente para ejecutarse en la web. A estas extensiones se les conoce como "extensiones web". Para aprender cómo puedes crear una extensión web o actualizar la existente para que funcione en la web, consulta la sección de "[Extensiones web](https://code.visualstudio.com/api/extension-guides/web-extensions)" en la documnetación de {% data variables.product.prodname_vscode_shortname %}. -Las extensiones que puedan ejecutarse en {% data variables.product.prodname_serverless %} aparecerán en la Vista de Extensiones y podrán instalarse. Si utilizas la sincronización de ajustes, cualquier extensión compatible también se instala automáticamente. Para obtener más información, consulta la sección de "[Sincronización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync)" en la documentación de {% data variables.product.prodname_vscode %}. +Las extensiones que puedan ejecutarse en {% data variables.product.prodname_serverless %} aparecerán en la Vista de Extensiones y podrán instalarse. Si utilizas la sincronización de ajustes, cualquier extensión compatible también se instala automáticamente. Para obtener más información, consulta la sección de "[Sincronización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync)" en la documentación de {% data variables.product.prodname_vscode_shortname %}. ## Solución de problemas @@ -104,5 +104,5 @@ Si tienes problemas para abrir el {% data variables.product.prodname_serverless ### Limitaciones conocidas - El {% data variables.product.prodname_serverless %} es actualmente compatible en Chrome (y en varios otros buscadores basados en Chromium), Edge, Firefox y Safari. Te recomendamos que utilices las últimas versiones de estos buscadores. -- Es posible que algunos enlaces de teclas no funcionen, dependiendo del buscador que estás utilizando. Estas limitaciones de enlaces de teclas se documentan en la sección de "[limitaciones conocidas y adaptaciones](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" de la documentación de {% data variables.product.prodname_vscode %}. +- Es posible que algunos enlaces de teclas no funcionen, dependiendo del buscador que estás utilizando. Estas limitaciones de enlaces de teclas se documentan en la sección de "[limitaciones conocidas y adaptaciones](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" de la documentación de {% data variables.product.prodname_vscode_shortname %}. - `.` podría no funcionar para abrir el {% data variables.product.prodname_serverless %} de acuerdo con tu diseño de teclado local. En dado caso, puedes abrir cualquier repositorio de {% data variables.product.prodname_dotcom %} en el {% data variables.product.prodname_serverless %} si cambias la URL de `github.com` a `github.dev`. diff --git a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md index 9303b5572f..48a3fa23cb 100644 --- a/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md +++ b/translations/es-ES/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -22,11 +22,11 @@ When you create a codespace, you can choose the type of the virtual machine you ![A list of available machine types](/assets/images/help/codespaces/choose-custom-machine-type.png) -If you have your {% data variables.product.prodname_codespaces %} editor preference set to "Visual Studio Code for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used. +If you have your {% data variables.product.prodname_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used. ![The 'prebuilt codespace found' message](/assets/images/help/codespaces/prebuilt-codespace-found.png) -Similarly, if your editor preference is "Visual Studio Code" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for Codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)." +Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for Codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)." After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal: diff --git a/translations/es-ES/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md b/translations/es-ES/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md index 349bff5e32..c0079afa59 100644 --- a/translations/es-ES/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md +++ b/translations/es-ES/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md @@ -44,7 +44,7 @@ Las wikis son parte de los repositorios Gift, de manera que puedes hacer cambios ### Clonar wikis en tu computadora -Cada wiki brinda una manera sencilla de clonar sus contenidos en tu computadora. Once you've created an initial page on {% data variables.product.product_name %}, you can clone the repository to your computer with the provided URL: +Cada wiki brinda una manera sencilla de clonar sus contenidos en tu computadora. Una vez que creaste una página inicial en {% data variables.product.product_name %}, puedes clonar el repositorio a tu computadora con la URL que se proporcionó: ```shell $ git clone https://github.com/YOUR_USERNAME/YOUR_REPOSITORY.wiki.git diff --git a/translations/es-ES/content/communities/moderating-comments-and-conversations/index.md b/translations/es-ES/content/communities/moderating-comments-and-conversations/index.md index a956c9c113..98a8939023 100644 --- a/translations/es-ES/content/communities/moderating-comments-and-conversations/index.md +++ b/translations/es-ES/content/communities/moderating-comments-and-conversations/index.md @@ -16,7 +16,7 @@ children: - /managing-disruptive-comments - /locking-conversations - /limiting-interactions-in-your-repository - - /limiting-interactions-for-your-user-account + - /limiting-interactions-for-your-personal-account - /limiting-interactions-in-your-organization - /tracking-changes-in-a-comment - /managing-how-contributors-report-abuse-in-your-organizations-repository diff --git a/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md b/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md similarity index 93% rename from translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md rename to translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md index 03266611d3..3cd11ad755 100644 --- a/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md +++ b/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md @@ -1,5 +1,5 @@ --- -title: Limitar las interacciones para tu cuenta de usuario +title: Limitar las interacciones para tu cuenta personal intro: Puedes requerir temporalmente un periodo de actividad limitada para usuarios específicos en todos los repositorios públicos que pertenezcan a tu cuenta personal. versions: fpt: '*' @@ -7,6 +7,7 @@ versions: permissions: Anyone can limit interactions for their own personal account. redirect_from: - /github/building-a-strong-community/limiting-interactions-for-your-user-account + - /communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account topics: - Community shortTitle: Limitar las interacciones en tu cuenta diff --git a/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md index 99628d850b..06f5548efc 100644 --- a/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md +++ b/translations/es-ES/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md @@ -22,7 +22,7 @@ shortTitle: Limitar las interacciones en un repositorio {% data reusables.community.types-of-interaction-limits %} -También puedes habilitar las limitaciones de las actividades en todos los repositorios que le pertenezcan a tu cuenta personal o a una organización. Si se habilita un límite a lo largo de la organización o del usuario, no podrás limitar la actividad para los repositorios individuales que pertenezcan a la cuenta. Para obtener más información, consulta las secciones "[Limitar las interacciones para tu cuenta personal](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account)" y "[Limitar las interacciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)". +También puedes habilitar las limitaciones de las actividades en todos los repositorios que le pertenezcan a tu cuenta personal o a una organización. Si se habilita un límite a lo largo de la organización o del usuario, no podrás limitar la actividad para los repositorios individuales que pertenezcan a la cuenta. Para obtener más información, consulta las secciones "[Limitar las interacciones para tu cuenta personal](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account)" y "[Limitar las interacciones en tu organización](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)". ## Limitar las interacciones en tu repositorio diff --git a/translations/es-ES/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md b/translations/es-ES/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md index 679c791e51..4e6271442e 100644 --- a/translations/es-ES/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md +++ b/translations/es-ES/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md @@ -47,13 +47,13 @@ Cualquiera con acceso de escritura a un repositorio puede editar comentarios sob Es adecuado editar un comentario y eliminar el contenido que no haga ninguna colaboración con la conversación y viole el código de conducta de tu comunidad{% ifversion fpt or ghec %} o los [Lineamientos comunitarios](/free-pro-team@latest/github/site-policy/github-community-guidelines) de GitHub{% endif %}. -Sometimes it may make sense to clearly indicate edits and their justification. +Algunas veces podría ser coherente indicar claramente las ediciones y su justificación. -That said, anyone with read access to a repository can view a comment's edit history. El menú desplegable **editado** en la parte superior del comentario contiene un historial de las ediciones y muestra el usuario y el registro de horario de cada edición. +Dicho esto, cualquiera con acceso de lectura a un repositorio puede ver el historial de edición de un comentario. El menú desplegable **editado** en la parte superior del comentario contiene un historial de las ediciones y muestra el usuario y el registro de horario de cada edición. ![Comentario con nota adicional que el contenido fue redactado](/assets/images/help/repository/content-redacted-comment.png) -## Redacting sensitive information +## Redactar la información sensible Los autores de los comentarios y cualquiera con acceso de escritura a un repositorio puede también eliminar información sensible de un historial de edición de los comentarios. Para obtener más información, consulta "[Rastrear los cambios en un comentario](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)." @@ -81,7 +81,7 @@ Eliminar un comentario crea un evento cronológico que es visible para todos aqu {% endnote %} -### Steps to delete a comment +### Pasos para borrar un comentario 1. Navega hasta el comentario que deseas eliminar. 2. En la esquina superior derecha del comentario, haz clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, después haz clic en **Delete (Eliminar)**. ![El ícono de kebab horizontal y el menú de moderación de comentario que muestra las opciones Editar, Ocultar, Eliminar e Informar](/assets/images/help/repository/comment-menu.png) diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md index 006cfee9f2..eadd7e515b 100644 --- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md +++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md @@ -36,9 +36,7 @@ Al usar el creador de plantillas, puedes especificar un título y una descripci Con los formatos de propuesta, puedes crear plantillas que tengan campos de formatos web utilizando el modelado de formatos de {% data variables.product.prodname_dotcom %}. Cuando un contribuyente abre una propuesta utilizando un formato de propuesta, las entradas de este formato se convierten en un comentario de propuesta con lenguaje de marcado estándar. Puedes especificar varios tipos diferentes de entradas y configurarlas como se requieran para ayudar a que los contribuyentes abran las propuestas accionables en tu repositorio. Para obtener más información, consulta las secciones "[Configurar plantillas de propuestas en tu repositorio](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)" y "[Sintaxis para emitir formatos](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)". {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} {% data reusables.repositories.issue-template-config %} Para obtener más información, consulta "[Configurar plantillas de propuestas para tu repositorio](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser)". -{% endif %} Las plantillas de propuestas se almacenan en la rama por defecto del repositorio, en un directorio oculto `.github/ISSUE_TEMPLATE`. Si creas una plantilla en otra rama, no estará disponible para que la usen los colaboradores. Los nombres de archivo de las plantillas de propuestas no distinguen entre mayúsculas y minúsculas y necesitan tener una extensión *.md*.{% ifversion fpt or ghec %}Las plantillas de propuestas que se crearon con formatos de propuesta necesitan una extensión *.yml*.{% endif %}{% data reusables.repositories.valid-community-issues %} diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md index 066cfdc38d..7620665f59 100644 --- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md +++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md @@ -21,12 +21,8 @@ shortTitle: Configure {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} - ## Creating issue templates -{% endif %} - {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 3. In the "Features" section, under "Issues," click **Set up templates**. @@ -71,7 +67,6 @@ Here is the rendered version of the issue form. {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} ## Configuring the template chooser {% data reusables.repositories.issue-template-config %} @@ -110,7 +105,6 @@ Your configuration file will customize the template chooser when the file is mer {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -{% endif %} ## Further reading diff --git a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md index b906d334c1..30fd34714b 100644 --- a/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md +++ b/translations/es-ES/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md @@ -17,7 +17,7 @@ shortTitle: Configurar el editor predeterminado - [Atom](https://atom.io/) - [MacVim](https://macvim-dev.github.io/macvim/) -- [Visual Studio Code](https://code.visualstudio.com/) +- [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) - [Visual Studio Codium](https://vscodium.com/) - [Sublime Text](https://www.sublimetext.com/) - [BBEdit](http://www.barebones.com/products/bbedit/) @@ -44,7 +44,7 @@ shortTitle: Configurar el editor predeterminado {% windows %} - [Atom](https://atom.io/) -- [Visual Studio Code](https://code.visualstudio.com/) +- [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) - [Visual Studio Codium](https://vscodium.com/) - [Sublime Text](https://www.sublimetext.com/) - [ColdFusion Builder](https://www.adobe.com/products/coldfusion-builder.html) diff --git a/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md index 6c088afd31..e08db5adf3 100644 --- a/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md +++ b/translations/es-ES/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md @@ -89,7 +89,7 @@ Puedes seleccionar los permisos en una secuencia de consulta utilizando los nomb | [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Otorga acceso a la [API de Contenidos](/rest/reference/repos#contents). Puede ser uno de entre `none`, `read`, o `write`. | | [`starring`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Otorga acceso a la [API de marcar con estrella](/rest/reference/activity#starring). Puede ser uno de entre `none`, `read`, o `write`. | | [`estados`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Otorga acceso a la [API de Estados](/rest/reference/commits#commit-statuses). Puede ser uno de entre `none`, `read`, o `write`. | -| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Otorga acceso a la [API de debates de equipo](/rest/reference/teams#discussions) y a la [API de comentarios en debates de equipo](/rest/reference/teams#discussion-comments). Puede ser uno de entre `none`, `read`, o `write`.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Otorga acceso a la [API de debates de equipo](/rest/reference/teams#discussions) y a la [API de comentarios en debates de equipo](/rest/reference/teams#discussion-comments). Puede ser uno de entre `none`, `read`, o `write`.{% ifversion fpt or ghes or ghae or ghec %} | `vulnerability_alerts` | Otorga acceso para recibir {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables en un repositorio. Consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" para aprender más. Puede ser uno de entre: `none` o `read`.{% endif %} | `observando` | Otorga acceso a la lista y cambia los repositorios a los que un usuario está suscrito. Puede ser uno de entre `none`, `read`, o `write`. | diff --git a/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index e7ef5122e6..a9c09dd0ff 100644 --- a/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/es-ES/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -239,8 +239,8 @@ Mientras que la mayoría de tu interacción con la API deberá darse utilizando * [Listar los despliegues](/rest/reference/deployments#list-deployments) * [Crear un despliegue](/rest/reference/deployments#create-a-deployment) -* [Obtener un despliegue](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %} -* [Borrar un despliegue](/rest/reference/deployments#delete-a-deployment){% endif %} +* [Obtén un despliegue](/rest/reference/deployments#get-a-deployment) +* [Borra un despliegue](/rest/reference/deployments#delete-a-deployment) #### Eventos @@ -422,14 +422,12 @@ Mientras que la mayoría de tu interacción con la API deberá darse utilizando * [Eliminar el requerir los ganchos de pre-recepción para una organización](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} #### Poyectos de Equipo de una Organización * [Listar los proyectos de equipo](/rest/reference/teams#list-team-projects) * [Verificar los permisos del equipo para un proyecto](/rest/reference/teams#check-team-permissions-for-a-project) * [Agregar o actualizar los permisos de un proyecto de equipo](/rest/reference/teams#add-or-update-team-project-permissions) * [Eliminar a un proyecto de un equipo](/rest/reference/teams#remove-a-project-from-a-team) -{% endif %} #### Repositorios de Equipo de la Organización @@ -575,7 +573,7 @@ Mientras que la mayoría de tu interacción con la API deberá darse utilizando #### Reacciones -{% ifversion fpt or ghes or ghae or ghec %}*[Borrar una reacción](/rest/reference/reactions#delete-a-reaction-legacy){% else %}*[Borrar una reacción](/rest/reference/reactions#delete-a-reaction){% endif %} +* [Borra una reacción](/rest/reference/reactions) * [Listar las reacciones a un comentario de una confirmación](/rest/reference/reactions#list-reactions-for-a-commit-comment) * [Crear una reacción para el comentario de una confirmación](/rest/reference/reactions#create-reaction-for-a-commit-comment) * [Listar las reacciones de un informe de problemas](/rest/reference/reactions#list-reactions-for-an-issue) @@ -587,13 +585,13 @@ Mientras que la mayoría de tu interacción con la API deberá darse utilizando * [Listar las reacciones para un comentario de debate de equipo](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) * [Crear una reacción para un comentario de debate de equipo](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) * [Listar las reaciones a un debate de equipo](/rest/reference/reactions#list-reactions-for-a-team-discussion) -* [Crear una reacción para un debate de equipo](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %} +* [Crear una reacción para un debate de equipo](/rest/reference/reactions#create-reaction-for-a-team-discussion) * [Borrar la reacción a un comentario de una confirmación](/rest/reference/reactions#delete-a-commit-comment-reaction) * [Borrar la reacción a un comentario](/rest/reference/reactions#delete-an-issue-reaction) * [Borrar la reacción a un comentario de una confirmación](/rest/reference/reactions#delete-an-issue-comment-reaction) * [Borrar la reacción a un comentario de una solicitud de extracción](/rest/reference/reactions#delete-a-pull-request-comment-reaction) * [Borrar la reacción a un debate de equipo](/rest/reference/reactions#delete-team-discussion-reaction) -* [Borrar la reacción a un comentario de un debate de equipo](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} +* [Borrar una reacción a un comentario en un debate de equipo](/rest/reference/reactions#delete-team-discussion-comment-reaction) #### Repositorios @@ -707,11 +705,9 @@ Mientras que la mayoría de tu interacción con la API deberá darse utilizando * [Obtener el README de un repositorio](/rest/reference/repos#get-a-repository-readme) * [Obtener la licencia para un repositorio](/rest/reference/licenses#get-the-license-for-a-repository) -{% ifversion fpt or ghes or ghae or ghec %} #### Envíos de Evento de un Repositorio * [Crear un evento de envío de un repositorio](/rest/reference/repos#create-a-repository-dispatch-event) -{% endif %} #### Ganchos de Repositorio 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 8784a0f106..37384594fc 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 @@ -333,7 +333,7 @@ Para crear este vínculo, necesitarás el `client_id` de tus Apps de Oauth, el c * "[Solución de problemas para errores de solicitud de autorización](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" * "[Solución de problemas para errores de solicitud de tokens de acceso para Apps de OAuth](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" -* "[Errores del flujo de dispostivos](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +* "[Errores del flujo de dispostivos](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} * "[Vencimiento y revocación de token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} ## Leer más diff --git a/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md index 7e11b59e60..45a3ba13af 100644 --- a/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md +++ b/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md @@ -85,7 +85,7 @@ Considera estas ideas cuando utilices tokens de acceso personal: * Puedes realizar solicitudes cURL de una sola ocasión. * Puedes ejecutar scripts personales. * No configures un script para que lo utilice todo tu equipo o compañía. -* No configures una cuenta personal para que actúe como un usuario bot.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %} +* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} * Sí debes establecer un vencimiento para tus tokens de acceso personal para que te ayuden a mantener tu información segura.{% endif %} ## Determinar qué integración debes crear diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md b/translations/es-ES/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md index 2a31833042..53b6f12b04 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md +++ b/translations/es-ES/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md @@ -89,4 +89,4 @@ Tus implementaciones de lenguaje y de servidor pueden diferir de esta muestra de * **No se recomienda** utilizar un simple operador de `==`. Un método como el de [`secure_compare`][secure_compare] lleva a cabo una secuencia de comparación de "tiempo constante" que ayuda a mitigar algunos ataques de temporalidad en contra de las operaciones de igualdad habituales. -[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare +[secure_compare]: https://rubydoc.info/github/rack/rack/main/Rack/Utils:secure_compare diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 82c5d0766b..d7411f9b56 100644 --- a/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -353,10 +353,10 @@ Los eventos de webhook se desencadenan basándose en la especificidad del domini ### Objeto de carga útil del webhook -| Clave | Tipo | Descripción | -| ------------ | ------------------------------------------- | -------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} -| `Acción` | `secuencia` | La acción realizada. Puede ser `created`.{% endif %} -| `deployment` | `objeto` | El [despliegue](/rest/reference/deployments#list-deployments). | +| Clave | Tipo | Descripción | +| ------------ | ----------- | -------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción realizada. Puede ser `created`. | +| `deployment` | `objeto` | El [despliegue](/rest/reference/deployments#list-deployments). | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -378,14 +378,14 @@ Los eventos de webhook se desencadenan basándose en la especificidad del domini ### Objeto de carga útil del webhook -| Clave | Tipo | Descripción | -| ---------------------------------- | ------------------------------------------- | ----------------------------------------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} -| `Acción` | `secuencia` | La acción realizada. Puede ser `created`.{% endif %} -| `deployment_status` | `objeto` | El [estado del despliegue](/rest/reference/deployments#list-deployment-statuses). | -| `deployment_status["state"]` | `secuencia` | El estado nuevo. Puede ser `pending`, `success`, `failure`, o `error`. | -| `deployment_status["target_url"]` | `secuencia` | El enlace opcional agregado al estado. | -| `deployment_status["description"]` | `secuencia` | La descripción opcional legible para las personas que se agrega al estado. | -| `deployment` | `objeto` | El [despliegue](/rest/reference/deployments#list-deployments) con el que se asocia este estado. | +| Clave | Tipo | Descripción | +| ---------------------------------- | ----------- | ----------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción realizada. Puede ser `created`. | +| `deployment_status` | `objeto` | El [estado del despliegue](/rest/reference/deployments#list-deployment-statuses). | +| `deployment_status["state"]` | `secuencia` | El nuevo estado. Puede ser `pending`, `success`, `failure`, o `error`. | +| `deployment_status["target_url"]` | `secuencia` | El enlace opcional agregado al estado. | +| `deployment_status["description"]` | `secuencia` | La descripción opcional legible para las personas que se agrega al estado. | +| `deployment` | `objeto` | El [despliegue](/rest/reference/deployments#list-deployments) con el que se asocia este estado. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1154,7 +1154,6 @@ Las entregas para los eventos `review_requested` y `review_request_removed` tend {{ webhookPayloadsForCurrentVersion.release.published }} -{% ifversion fpt or ghes or ghae or ghec %} ## repository_dispatch Este evento ocurre cuando una {% data variables.product.prodname_github_app %} envía una solicitud de `POST` a la terminal "[Crear un evento de envío de repositorio](/rest/reference/repos#create-a-repository-dispatch-event)". @@ -1166,7 +1165,6 @@ Este evento ocurre cuando una {% data variables.product.prodname_github_app %} e ### Ejemplo de carga útil del webhook {{ webhookPayloadsForCurrentVersion.repository_dispatch }} -{% endif %} ## repositorio @@ -1370,7 +1368,7 @@ Solo puedes crear un webhook de patrocinio en {% data variables.product.prodname | ------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `id` | `número` | El identificador único del estado. | | `sha` | `secuencia` | El SHA de la confirmación. | -| `state` | `secuencia` | El estado nuevo. Puede ser `pending`, `success`, `failure`, o `error`. | +| `state` | `secuencia` | El nuevo estado. Puede ser `pending`, `success`, `failure`, o `error`. | | `descripción` | `secuencia` | La descripción opcional legible para las personas que se agrega al estado. | | `url_destino` | `secuencia` | El enlace opcional agregado al estado. | | `branches` | `arreglo` | Un conjunto de objetos de la rama que contiene el SHA del estado. Cada rama contiene el SHA proporcionado, pero éste puede ser o no el encabezado de la rama. El conjunto incluye un máximo de 10 ramas. | @@ -1490,7 +1488,7 @@ Este evento ocurre cuando alguien activa una ejecución de flujo de trabajo en G {{ webhookPayloadsForCurrentVersion.workflow_dispatch }} {% endif %} -{% ifversion fpt or ghes > 3.2 or ghec or ghae-issue-4462 %} +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## workflow_job diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md index f524164282..43d3f27020 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md @@ -1,39 +1,39 @@ --- title: Acerca de utilizar visual Studio Code con GitHub Classroom shortTitle: Aceca de utilizar Visual Studio Code -intro: 'Puedes configurar a Visual Studio Code como el editor preferido para las tareas en {% data variables.product.prodname_classroom %}.' +intro: 'You can configure {% data variables.product.prodname_vscode %} as the preferred editor for assignments in {% data variables.product.prodname_classroom %}.' versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/about-using-vs-code-with-github-classroom --- -## Acerca de Visual Studio Code +## Acerca de {% data variables.product.prodname_vscode %} -Visual Studio Code es un editor de código fuente ligero pero podereos, el cual se ejecuta en tu máquina de escritorio y está disponible para Windows, macOS y Linux. Con la [Extensión de GitHub Classroom para Visual Studio Code](https://aka.ms/classroom-vscode-ext), los alumnos pueden buscar, editar, emitir, colaborar y probar sus Tareas de las Aulas fácilmente. Para obtener más información sobre los IDe y {% data variables.product.prodname_classroom %}, consulta la sección "[Integrar {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". +{% data variables.product.prodname_vscode %} is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. With the [GitHub Classroom extension for {% data variables.product.prodname_vscode_shortname %}](https://aka.ms/classroom-vscode-ext), students can easily browse, edit, submit, collaborate, and test their Classroom Assignments. Para obtener más información sobre los IDe y {% data variables.product.prodname_classroom %}, consulta la sección "[Integrar {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". ### El editor predilecto de tus alumnos -La integración de GitHub Classroom con Visual Studio Code proporciona a los alumnos un paquete de extensiones que contiene: +The GitHub Classroom integration with {% data variables.product.prodname_vscode_shortname %} provides students with an extension pack which contains: 1. [La Extensión de GitHub Classroom](https://aka.ms/classroom-vscode-ext) con abstracciones personalizadas que hacen más fácil que los alumnos naveguen en el inicio. 2. [La Extgensión de Visual Studio Live Share](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare-pack) que se integra en una vista de alumnos para dar acceso fácil a los ayudantes para enseñar y a los compañeros de clase para ayudar y colaborar. 3. [La Extensión de GitHub Pull Request](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) que permite a los alumnos ver la retroalimentación de sus instructores dentro del editor. -### Cómo lanzar una tarea en Visual Sudio Code -Cuando creas una tarea, Visual Studio Code puede agregarse como el editor preferido para ella. Para obtener más detalles, consulta la sección "[Integrar a {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". +### How to launch the assignment in {% data variables.product.prodname_vscode_shortname %} +When creating an assignment, {% data variables.product.prodname_vscode_shortname %} can be added as the preferred editor for an assignment. Para obtener más detalles, consulta la sección "[Integrar a {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". -Esto incluirá una insignia de "Abrir en Visual Studio Code" en todos los repositorios de los alumnos. Esta insignia maneja la instalación de Visual Studio Code, el paquete de extensiones del Aula, y el abrir hacia la tarea activa con un clic. +This will include an "Open in {% data variables.product.prodname_vscode_shortname %}" badge in all student repositories. This badge handles installing {% data variables.product.prodname_vscode_shortname %}, the Classroom extension pack, and opening to the active assignment with one click. {% note %} -**Nota:** El alumno debe tener instalado Git en su computadora para subir código desde Visual Studio Code hacia su repositorio. Esto no se instala automáticamente cuando haces clic en el botón de **Abrir en Visual Studio Code**. El alumno puede descargar Git desde [aquí](https://git-scm.com/downloads). +**Note:** The student must have Git installed on their computer to push code from {% data variables.product.prodname_vscode_shortname %} to their repository. This is not automatically installed when clicking the **Open in {% data variables.product.prodname_vscode_shortname %}** button. El alumno puede descargar Git desde [aquí](https://git-scm.com/downloads). {% endnote %} ### Cómo utilizar el paquete de extensión de GitHub Classroom La extensión de GitHub Classroom tiene dos componentes principales: la vista de 'Aulas' y la vista de 'Tarea Activa'. -Cuando un alumno lanza la extensión por primera vez, automáticamente navegan a la pestaña del Explorador en Visual Studio Code, en donde pueden entrar a la vista de "Tarea Activa" junto con la vista de diagrama de árbol de los archivos en el repositorio. +When the student launches the extension for the first time, they are automatically navigated to the Explorer tab in {% data variables.product.prodname_vscode_shortname %}, where they can see the "Active Assignment" view alongside the tree-view of files in the repository. ![Vista de Tarea Activa de GitHub Classroom](/assets/images/help/classroom/vs-code-active-assignment.png) diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md index 278f590c14..731d2acbb9 100644 --- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md +++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md @@ -25,7 +25,7 @@ Después de que un alumno acepta una tarea con un IDE, el archivo README en su r |:--------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | {% data variables.product.prodname_github_codespaces %} | "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)" | | Microsoft MakeCode Arcade | "[Acerca de utilizar MakeCode Arcade con {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | -| Visual Studio Code | La [extensión de {% data variables.product.prodname_classroom %}](http://aka.ms/classroom-vscode-ext) en el Mercado de Visual Studio | +| {% data variables.product.prodname_vscode %} | La [extensión de {% data variables.product.prodname_classroom %}](http://aka.ms/classroom-vscode-ext) en el Mercado de Visual Studio | Sabemos que las integraciones con IDE en la nube son importantes para tu aula y estamos trabajando para traerte más opciones. 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 682303fd67..89646e219b 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 @@ -14,7 +14,7 @@ shortTitle: Extensiones & integraciones ## Herramientas del editor -Puedes conectarte a los repositorios de {% data variables.product.product_name %} dentro de las herramientas de edición de terceros tales como Atom, Unity y Visual Studio. +You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and {% data variables.product.prodname_vs %}. ### {% data variables.product.product_name %} para Atom @@ -24,13 +24,13 @@ Con el {% data variables.product.product_name %} para la extensión de Atom, pue Con el {% data variables.product.product_name %} para la extensión del editor de Unity, puedes desarrollar en Unity, la plataforma de código abierto de desarrollo de juegos, y ver tu trabajo en {% data variables.product.product_name %}. Para obtener más información, consulta el [sitio](https://unity.github.com/) oficial de la extensión del editor de Unity o la [documentación](https://github.com/github-for-unity/Unity/tree/master/docs). -### {% data variables.product.product_name %} para Visual Studio +### {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} -Con el {% data variables.product.product_name %} para la extensión de Visual Studio, puedes trabajar en los repositorios {% data variables.product.product_name %} sin salir de Visual Studio. Para obtener más información, consulta el [sitio](https://visualstudio.github.com/) oficial de la extensión de Visual Studio o la [documentación](https://github.com/github/VisualStudio/tree/master/docs). +With the {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} extension, you can work in {% data variables.product.product_name %} repositories without leaving {% data variables.product.prodname_vs %}. For more information, see the official {% data variables.product.prodname_vs %} extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs). -### {% data variables.product.prodname_dotcom %} para Visual Studio Code +### {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} -Con el {% data variables.product.prodname_dotcom %} para la extensión de Visual Studio Code, puedes revisar y administrar solicitudes de extracción {% data variables.product.product_name %} en Visual Studio Code. Para obtener más información, consulta el [sitio](https://vscode.github.com/) oficial de la extensión de Visual Studio Code o la [documentación](https://github.com/Microsoft/vscode-pull-request-github). +With the {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} extension, you can review and manage {% data variables.product.product_name %} pull requests in {% data variables.product.prodname_vscode_shortname %}. For more information, see the official {% data variables.product.prodname_vscode_shortname %} extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github). ## Herramientas de gestión de proyectos diff --git a/translations/es-ES/content/get-started/exploring-projects-on-github/following-organizations.md b/translations/es-ES/content/get-started/exploring-projects-on-github/following-organizations.md index 612ee9879e..8680ef9ce7 100644 --- a/translations/es-ES/content/get-started/exploring-projects-on-github/following-organizations.md +++ b/translations/es-ES/content/get-started/exploring-projects-on-github/following-organizations.md @@ -15,7 +15,7 @@ topics: ## Aceca de los seguidores en {% data variables.product.product_name %} -When you follow organizations, you'll see their public activity on your personal dashboard. Para obtener más información, consulta "[Acerca de tu tablero personal](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)". +When you follow organizations, you'll see their public activity on your personal dashboard. Para obtener más información, consulta "[Acerca de tu tablero personal](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)". You can unfollow an organization if you do not wish to see their {% ifversion fpt or ghec %}public{% endif %} activity on {% data variables.product.product_name %}. diff --git a/translations/es-ES/content/get-started/exploring-projects-on-github/following-people.md b/translations/es-ES/content/get-started/exploring-projects-on-github/following-people.md index f03bfd32e4..04590120b9 100644 --- a/translations/es-ES/content/get-started/exploring-projects-on-github/following-people.md +++ b/translations/es-ES/content/get-started/exploring-projects-on-github/following-people.md @@ -17,7 +17,7 @@ topics: ## Aceca de los seguidores en {% data variables.product.product_name %} -Cuando sigues a las personas, verás su actividad pública en tu tablero personal.{% ifversion fpt or ghec %} Si alguien que sigues marca un repositorio como favorito, {% data variables.product.product_name %} podría recomendártelo.{% endif %} Para obtener más información, consulta la sección "[Acerca de tu tablero personal](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)". +Cuando sigues a las personas, verás su actividad pública en tu tablero personal.{% ifversion fpt or ghec %} Si alguien a quien sigues marca un repositorio público como favorito, {% data variables.product.product_name %} podría recomendártelo.{% endif %} Para obtener más información, consulta la sección "[Acerca de tu tablero personal](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)". Puedes dejar de seguir a alguien si no quieres ver su actividad pública en {% data variables.product.product_name %}. diff --git a/translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md b/translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md index e067a7b838..1ead23db4d 100644 --- a/translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md +++ b/translations/es-ES/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md @@ -26,7 +26,7 @@ Puedes buscar, clasificar y filtrar tus repositorios y temas marcados con estrel Marcar con estrellas tus repositorios y temas favoritos te facilitará encontrarlos posteriormente. Puedes ver todos los repositorios y temas que has marcado con estrellas visitando tu {% data variables.explore.your_stars_page %}. {% ifversion fpt or ghec %} -Puedes seleccionar los repositorios y temas como favoritos para descubrir proyectos similares en {% data variables.product.product_name %}. Cuando marcas los repositorios o temas con una estrella, {% data variables.product.product_name %} podría recomendarte contenido relacionado en tu tablero personal. Para obtener más información, consulta las secciones "[Encontrar formas de contribuir con el código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)" y "[Acerca de tu tablero personal](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)". +Puedes seleccionar los repositorios y temas como favoritos para descubrir proyectos similares en {% data variables.product.product_name %}. Cuando marcas los repositorios o temas con una estrella, {% data variables.product.product_name %} podría recomendarte contenido relacionado en tu tablero personal. Para obtener más información, consulta las secciones "[Encontrar formas de contribuir con el código abierto en {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)" y "[Acerca de tu tablero personal](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)". {% endif %} Marcar un repositorio con estrella también muestra reconocimiento al mantenedor del repositorio por su trabajo. Muchas de las clasificaciones de los repositorios de {% data variables.product.prodname_dotcom %} dependen de la cantidad de estrellas que tiene un repositorio. Además, [Explore](https://github.com/explore) muestra repositorios populares en base a la cantidad de estrellas que tienen. diff --git a/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md index 2b3d28a26d..601486e0bd 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/about-remote-repositories.md @@ -81,14 +81,10 @@ Cuando ejecutas `git clone`, `git fetch`, `git pull`, o `git push` en un reposit {% endtip %} -{% ifversion fpt or ghes or ghae or ghec %} - ## Clonar con {% data variables.product.prodname_cli %} También puedes instalar {% data variables.product.prodname_cli %} para utilizar flujos de trabajo de {% data variables.product.product_name %} en tu terminal. Para obtener más información, consulta la sección "[Acerca de {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)". -{% endif %} - {% ifversion not ghae %} ## Clonar con Subversion diff --git a/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md index fa52fb36cd..36199b32ee 100644 --- a/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md +++ b/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md @@ -28,9 +28,9 @@ shortTitle: Editores de texto asociados $ git config --global core.editor "atom --wait" ``` -## Utilizar Visual Studio Code como tu editor +## Using {% data variables.product.prodname_vscode %} as your editor -1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code. +1. Omstañar [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de {% data variables.product.prodname_vscode_shortname %}. {% data reusables.command_line.open_the_multi_os_terminal %} 3. Escribe este comando: ```shell @@ -68,9 +68,9 @@ shortTitle: Editores de texto asociados $ git config --global core.editor "atom --wait" ``` -## Utilizar Visual Studio Code como tu editor +## Using {% data variables.product.prodname_vscode %} as your editor -1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code. +1. Omstañar [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de {% data variables.product.prodname_vscode_shortname %}. {% data reusables.command_line.open_the_multi_os_terminal %} 3. Escribe este comando: ```shell @@ -107,9 +107,9 @@ shortTitle: Editores de texto asociados $ git config --global core.editor "atom --wait" ``` -## Utilizar Visual Studio Code como tu editor +## Using {% data variables.product.prodname_vscode %} as your editor -1. Instala [ Visual Studio Code](https://code.visualstudio.com/) (VS Code). Para obtener más información, consulta la sección "[Configurar Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de VS Code. +1. Omstañar [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de {% data variables.product.prodname_vscode_shortname %}. {% data reusables.command_line.open_the_multi_os_terminal %} 3. Escribe este comando: ```shell 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 ff51878ad2..177c1499bd 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 @@ -31,7 +31,7 @@ Una licencia de {% data variables.product.prodname_GH_advanced_security %} propo - **{% data variables.product.prodname_secret_scanning_caps %}** - Detecta secretos, por ejemplo claves y tokens, que se han verificado en el repositorio.{% if secret-scanning-push-protection %} Si se habilita la protección de subida, también detecta secretos cuando se suben a tu repositorio. Para obtener más información, consulta las secciones "[Acerca del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)" y "[Proteger las subidas con el {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)".{% else %} Para obtener más información, consulta la sección "[Acerca del {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)".{% endif %} -{% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4864 %} +{% ifversion fpt or ghes > 3.1 or ghec or ghae %} - **Revisión de dependencias** - Muestra todo el impacto de los cambios a las dependencias y vee los detalles de las versiones vulnerables antes de que fusiones una solicitud de cambios. Para obtener más información, consulta la sección "[Acerca de la revisión de dependencias](/code-security/supply-chain-security/about-dependency-review)". {% endif %} diff --git a/translations/es-ES/content/get-started/learning-about-github/about-versions-of-github-docs.md b/translations/es-ES/content/get-started/learning-about-github/about-versions-of-github-docs.md index 1020ac88a8..ed08269468 100644 --- a/translations/es-ES/content/get-started/learning-about-github/about-versions-of-github-docs.md +++ b/translations/es-ES/content/get-started/learning-about-github/about-versions-of-github-docs.md @@ -37,7 +37,7 @@ En una ventana amplia del buscador, no hay texto que siga al logo de {% data var En {% data variables.product.prodname_dotcom_the_website %}, cada cuenta tiene su propio plan. Cada cuenta personal tiene un plan asociado que proporciona acceso a ciertas características y cada organización tiene un plan asociado diferente. Si tu cuenta personal es miembro de una organización de {% data variables.product.prodname_dotcom_the_website %}, puedes tener acceso a características diferentes cuando utilizas recursos que le pertenezcan a esa organización y cuando utilizas los que le pertenecen a tu cuenta personal. Para obtener más información, consulta la sección "[Tipos de cuentas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)". -Si no sabes si una organización utiliza {% data variables.product.prodname_ghe_cloud %}, pregúntale a un propietario de organización. Para obtener más información, consulta la sección "[Ver los roles de las personas en una organización](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)". +Si no sabes si una organización utiliza {% data variables.product.prodname_ghe_cloud %}, pregúntale a un propietario de organización. Para obtener más información, consulta la sección "[Ver los roles de las personas en una organización](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)". ### {% data variables.product.prodname_ghe_server %} diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md index 9ff3a4ee8e..a3f04f886d 100644 --- a/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -75,7 +75,7 @@ Para obtener más información sobre cómo autenticarte en {% data variables.pro | ---------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Navega a {% data variables.product.prodname_dotcom_the_website %} | Si no necesitas trabajar con archivos localmente, {% data variables.product.product_name %} te permite completar la mayoría de las acciones relacionadas con Git en el buscador, desde crear y bifurcar repositorios hasta editar archivos y abrir solicitudes de cambios. | Este método es útil si quieres tener una interfaz virtual y necesitas realizar cambios rápidos y simples que no requieran que trabajes localmente. | | {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} se extiende y simplifica tu flujo de trabajo {% data variables.product.prodname_dotcom_the_website %}, usando una interfaz visual en lugar de comandos de texto en la línea de comandos. Para obtener más información sobre cómo iniciar con {% data variables.product.prodname_desktop %}, consulta la sección "[Iniciar con {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)". | Este método es le mejor si necesitas o quieres trabajar con archivos localmente, pero prefieres utilizar una interfaz visual para utilizar Git e interactuar con {% data variables.product.product_name %}. | -| IDE o editor de texto | Puedes configurar un editor de texto predeterminado, como [Atom](https://atom.io/) o [Visual Studio Code](https://code.visualstudio.com/) para abrir y editar tus archivos con Git, utilizar extensiones y ver la estructura del proyecto. Para obtener más información, consulta la sección "[Asociar los editores de texto con Git](/github/using-git/associating-text-editors-with-git)". | Es conveniente si estás trabajando con archivos y proyectos más complejos y quieres todo en un solo lugar, ya que los editores o IDE a menudo te permiten acceder directamente a la línea de comandos en el editor. | +| IDE o editor de texto | You can set a default text editor, like [Atom](https://atom.io/) or [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. Para obtener más información, consulta la sección "[Asociar los editores de texto con Git](/github/using-git/associating-text-editors-with-git)". | Es conveniente si estás trabajando con archivos y proyectos más complejos y quieres todo en un solo lugar, ya que los editores o IDE a menudo te permiten acceder directamente a la línea de comandos en el editor. | | Línea de comandos, con o sin {% data variables.product.prodname_cli %} | Para la mayoría de los controles granulares y personalización de cómo utilizas Git e interactúas con {% data variables.product.product_name %}, puedes utilizar la línea de comandos. Para obtener más información sobre cómo utilizar los comandos de Git, consulta la sección "[Hoja de comandos de Git](/github/getting-started-with-github/quickstart/git-cheatsheet)".

El {% data variables.product.prodname_cli %} es una herramienta de línea de comandos por separado que puedes instalar, la cual agrega solicitudes de cambio, propuestas, {% data variables.product.prodname_actions %} y otras características de {% data variables.product.prodname_dotcom %} a tu terminal para que puedas hacer todo tu trabajo desde un solo lugar. Para obtener más información, consulta la sección "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)". | Esto es lo más conveniente si ya estás trabajando desde la línea de comandos, lo cual te permite evitar cambiar de contexto o si estás más cómodo utilizando la línea de comandos. | | API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} | {% data variables.product.prodname_dotcom %} Tiene una API de REST y una de GraphQL que puedes utilizar para interactuar con {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Comenzar con la API](/github/extending-github/getting-started-with-the-api)". | La API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} tendrá la mayor utilidad si quisieras automatizar tareas comunes, respaldar tus datos o crear integraciones que se extiendan a {% data variables.product.prodname_dotcom %}. | ### 4. Escribir en {% data variables.product.product_name %} diff --git a/translations/es-ES/content/get-started/quickstart/communicating-on-github.md b/translations/es-ES/content/get-started/quickstart/communicating-on-github.md index bedb65241c..30cfaa7b24 100644 --- a/translations/es-ES/content/get-started/quickstart/communicating-on-github.md +++ b/translations/es-ES/content/get-started/quickstart/communicating-on-github.md @@ -117,7 +117,6 @@ Este ejemplo muestra la publicación de bienvenida de {% data variables.product. El mantenedor de la comunidad inició un debate para recibir a la comunidad y para pedir a los miembros que se presentaran a sí mismos. Esta publicación fomenta un ambiente acogedor para los visitantes y contribuyentes. Esta publicación también aclara que al equipo le complace ayudar a los contribuyentes del repositorio. {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} ### Casos de debates de equipo - Tengo una pregunta que no se relaciona necesariamente con los archivos específicos del repositorio. @@ -140,8 +139,6 @@ Un miembro del equipo `octocat` publicó un debate de equipo que les informaba s - Hay una publicación del blog que describe cómo los equipos utilizan {% data variables.product.prodname_actions %} para producir sus documentos. - Los materiales sobre el "All Hands" de abril está ahora disponible para que lo vean todos los miembros del equipo. -{% endif %} - ## Pasos siguientes Estos ejemplos te muestran cómo decidir cuál es la mejor herramienta para tus conversaciones en {% data variables.product.product_name %}. Pero esto es solo el inicio; puedes hacer mucho más para confeccionar estas herramientas de acuerdo con tus necesidades. diff --git a/translations/es-ES/content/get-started/using-github/github-command-palette.md b/translations/es-ES/content/get-started/using-github/github-command-palette.md index 293ae6772c..751f81b7a9 100644 --- a/translations/es-ES/content/get-started/using-github/github-command-palette.md +++ b/translations/es-ES/content/get-started/using-github/github-command-palette.md @@ -153,7 +153,7 @@ These commands are available from all scopes. |`New organization`|Create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." | |`New project`|Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)." | |`New repository`|Create a new repository from scratch. For more information, see "[Creating a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository)." | -|`Switch theme to `|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." | +|`Switch theme to `|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)." | ### Organization commands diff --git a/translations/es-ES/content/get-started/using-github/github-mobile.md b/translations/es-ES/content/get-started/using-github/github-mobile.md index f621bf2f48..8a7e665d07 100644 --- a/translations/es-ES/content/get-started/using-github/github-mobile.md +++ b/translations/es-ES/content/get-started/using-github/github-mobile.md @@ -25,10 +25,13 @@ Con {% data variables.product.prodname_mobile %} puedes: - Leer, revisar y colaborar en informes de problemas y solicitudes de extracción - Buscar, navegar e interactuar con usuarios, repositorios y organizaciones - Recibir notificaciones para subir información cuando alguien menciona tu nombre de usuario -{% ifversion fpt or ghec %}- Asegura tu cuenta de GitHub.com con la autenticación bifactorial{% endif %} +{% ifversion fpt or ghec %}- Asegura tu cuenta de GitHub.com con la autenticación bifactorial +- Verify your sign in attempts on unrecognized devices{% endif %} Para obtener más información sobre las notificaciones de {% data variables.product.prodname_mobile %}, consulta "[Configurando notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)." +{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)." {% endif %} + ## Instalar {% data variables.product.prodname_mobile %} Para instalar {% data variables.product.prodname_mobile %} para Android o iOS, consulta la sección [{% data variables.product.prodname_mobile %}](https://github.com/mobile). @@ -45,7 +48,7 @@ You can be simultaneously signed into mobile with one personal account on {% dat Debes instalar {% data variables.product.prodname_mobile %} 1.4 o posterior en tu dispositivo para utilizar {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}. -Para utilizar {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} debe estar en su versión 3.0 o posterior, y tu propietario de empresa debe habilitar la compatibilidad con la versión móvil en tu empresa. Para obtener más información, consulta las secciones {% ifversion ghes %}"[Notas de lanzamiento](/enterprise-server/admin/release-notes)" y {% endif %}"[Administrar {% data variables.product.prodname_mobile %} para tu empresa]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" en la documentación de {% data variables.product.prodname_ghe_server %}.{% else %}".{% endif %} +Para utilizar {% data variables.product.prodname_mobile %} con {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} debe estar en su versión 3.0 o posterior, y tu propietario de empresa debe habilitar la compatibilidad con la versión móvil en tu empresa. For more information, see {% ifversion ghes %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %} During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a personal account on {% data variables.product.prodname_dotcom_the_website %}. @@ -73,9 +76,9 @@ Si configuras el idioma en tu dispositivo para que sea uno de los compatibles, { {% data variables.product.prodname_mobile %} habilita automáticamente los Enlaces Universales para iOS. Cuando tocas en cualquier enlace de {% data variables.product.product_name %}, la URL destino se abrirá en {% data variables.product.prodname_mobile %} en vez de en Safari. Para obtener más información, consulta la sección[Enlaces Universales](https://developer.apple.com/ios/universal-links/) en el sitio para Desarrolladores de Apple. -Para inhabilitar los Enlaces Universales, presiona sostenidamente cualquier enlace de {% data variables.product.product_name %} y luego toca en **Abrir**. Cada vez que toques en un enlace de {% data variables.product.product_name %} posteriormente, la URL destino se abrirá en Safari en vez de en {% data variables.product.prodname_mobile %}. +To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Every time you tap a {% data variables.product.product_name %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}. -Para volver a habilitar los Enlaces Universales, sostén cualquier enlace de {% data variables.product.product_name %} y luego toca en **Abrir en {% data variables.product.prodname_dotcom %}**. +To re-enable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**. ## Compartir retroalimentación diff --git a/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md b/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md index 619f8d7304..cac7bd986d 100644 --- a/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md +++ b/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md @@ -19,7 +19,7 @@ versions: Typing ? on {% data variables.product.prodname_dotcom %} brings up a dialog box that lists the keyboard shortcuts available for that page. You can use these keyboard shortcuts to perform actions across the site without using your mouse to navigate. {% if keyboard-shortcut-accessibility-setting %} -You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see "[Managing accessibility settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings)."{% endif %} +You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see "[Managing accessibility settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings)."{% endif %} Below is a list of some of the available keyboard shortcuts. {% if command-palette %} @@ -30,7 +30,7 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a | Keyboard shortcut | Description |-----------|------------ |S or / | Focus the search bar. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)." -|G N | Go to your notifications. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}." +|G N | Go to your notifications. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)." |Esc | When focused on a user, issue, or pull request hovercard, closes the hovercard and refocuses on the element the hovercard is in {% if command-palette %}|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 %} @@ -101,7 +101,6 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |Command+G (Mac) or
Ctrl+G (Windows/Linux) | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." |{% endif %} |R | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." | - ## Issue and pull request lists | Keyboard shortcut | Description @@ -137,8 +136,8 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |J | Move selection down in the list |K | Move selection up in the list |Command+Shift+Enter | Add a single comment on a pull request diff | -|Alt and click | 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. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|{% endif %} +|Alt and click | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down Alt and clicking **Show outdated** or **Hide outdated**.| +|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. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."| ## Project boards @@ -195,7 +194,6 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr ## Notifications -{% ifversion fpt or ghes or ghae or ghec %} | Keyboard shortcut | Description |-----------|------------ |E | Mark as done @@ -203,13 +201,6 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr |Shift+I| Mark as read |Shift+M | Unsubscribe -{% else %} - -| Keyboard shortcut | Description -|-----------|------------ -|E or I or Y | Mark as read -|Shift+M | Mute thread -{% endif %} ## Network graph diff --git a/translations/es-ES/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/es-ES/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md index 4d29d77bc7..9c3207b9e9 100644 --- a/translations/es-ES/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ b/translations/es-ES/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md @@ -61,7 +61,6 @@ Git admite la asignación de archivos GeoJSON. Estas asignaciones se muestran co Sigue estos pasos para crear un gist. -{% ifversion fpt or ghes or ghae or ghec %} {% note %} También puedes crear un gist si utilizas el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh gist create`](https://cli.github.com/manual/gh_gist_create)" en el {% data variables.product.prodname_cli %}. @@ -69,7 +68,6 @@ También puedes crear un gist si utilizas el {% data variables.product.prodname_ Como alternativa, puedes arrastrar y soltar un archivo de texto desde tu escritorio directamente en el editor. {% endnote %} -{% endif %} 1. Inicia sesión en {% data variables.product.product_name %}. 2. Dirígete a tu {% data variables.gists.gist_homepage %}. diff --git a/translations/es-ES/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/es-ES/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index 160711e297..6ca2cf3bf8 100644 --- a/translations/es-ES/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/es-ES/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -29,18 +29,19 @@ When you use two or more headings, GitHub automatically generates a table of con ![Screenshot highlighting the table of contents icon](/assets/images/help/repository/headings_toc.png) - ## Estilo de texto -Puedes indicar énfasis con texto en negritas, itálicas o tachadas en los campos de comentario y archivos `.md`. +You can indicate emphasis with bold, italic, strikethrough, subscript, or superscript text in comment fields and `.md` files. -| Estilo | Sintaxis | Atajo del teclado | Ejemplo | Resultado | -| ---------------------------- | ------------------ | ------------------------------------------------------------------------------------- | ----------------------------------------------- | --------------------------------------------- | -| Negrita | `** **` o `__ __` | Command+B (Mac) or Ctrl+B (Windows/Linux) | `**Este texto está en negrita**` | **Este texto está en negrita** | -| Cursiva | `* *` o `_ _`      | Command+I (Mac) or Ctrl+I (Windows/Linux) | `*Este texto está en cursiva*` | *Este texto está en cursiva* | -| Tachado | `~~ ~~` | | `~~Este texto está equivocado~~` | ~~Este texto está equivocado~~ | -| Cursiva en negrita y anidada | `** **` y `_ _` | | `**Este texto es _extremadamente_ importante**` | **Este texto es _extremadamente_ importante** | -| Todo en negrita y cursiva | `*** ***` | | `***Todo este texto es importante***` | ***Todo este texto es importante*** | +| Estilo | Sintaxis | Atajo del teclado | Ejemplo | Resultado | +| ---------------------------- | -------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------- | --------------------------------------------- | +| Negrita | `** **` o `__ __` | Command+B (Mac) or Ctrl+B (Windows/Linux) | `**Este texto está en negrita**` | **Este texto está en negrita** | +| Cursiva | `* *` o `_ _`      | Command+I (Mac) or Ctrl+I (Windows/Linux) | `*Este texto está en cursiva*` | *Este texto está en cursiva* | +| Tachado | `~~ ~~` | | `~~Este texto está equivocado~~` | ~~Este texto está equivocado~~ | +| Cursiva en negrita y anidada | `** **` y `_ _` | | `**Este texto es _extremadamente_ importante**` | **Este texto es _extremadamente_ importante** | +| Todo en negrita y cursiva | `*** ***` | | `***Todo este texto es importante***` | ***Todo este texto es importante*** | +| Subscript | ` ` | | `This is a subscript text` | This is a subscript text | +| Superscript | ` ` | | `This is a superscript text` | This is a superscript text | ## Cita de texto @@ -235,7 +236,7 @@ Para obtener más información, consulta "[Acerca de las listas de tareas](/arti ## Mencionar personas y equipos -Puedes mencionar a una persona o [equipo](/articles/setting-up-teams/) en {% data variables.product.product_name %} al escribir @ más el nombre de usuario o el nombre del equipo. Esto activará una notificación y llamará su atención hacia la conversación. Las personas también recibirán una notificación si editas un comentario para mencionar su nombre de usuario o el nombre del equipo. Para obtener más información acerca de las notificaciones, consulta la sección {% ifversion fpt or ghes or ghae or ghec %}"[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Acerca de las notificaciones](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}". +Puedes mencionar a una persona o [equipo](/articles/setting-up-teams/) en {% data variables.product.product_name %} al escribir @ más el nombre de usuario o el nombre del equipo. Esto activará una notificación y llamará su atención hacia la conversación. Las personas también recibirán una notificación si editas un comentario para mencionar su nombre de usuario o el nombre del equipo. For more information about notifications, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)." {% note %} @@ -296,7 +297,7 @@ Para encontrar una lista completa de emojis y códigos disponibles, consulta el Puedes crear un nuevo párrafo al dejar una línea en blanco entre las líneas de texto. -{% ifversion fpt or ghae-issue-5180 or ghes > 3.2 or ghec %} +{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## Notas al pie Puedes agregar notas al pie para tu contenido si utilizas esta sintaxis de corchetes: diff --git a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/index.md b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/index.md index 3d41daf3c3..419aab2a1c 100644 --- a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/index.md +++ b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/index.md @@ -14,6 +14,7 @@ children: - /organizing-information-with-collapsed-sections - /creating-and-highlighting-code-blocks - /creating-diagrams + - /writing-mathematical-expressions - /autolinked-references-and-urls - /attaching-files - /creating-a-permanent-link-to-a-code-snippet diff --git a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md index 1d26e12b29..80441f6560 100644 --- a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md +++ b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md @@ -15,7 +15,7 @@ topics: ## Vincular una solicitud de cambios a una propuesta -Para enlazar una solicitud de cambios a una propuesta para{% ifversion fpt or ghes or ghae or ghec %} mostrar que una solución se encuentra en progreso y para{% endif %} cerrar la propuesta automáticamente cuando alguien fusiona la solicitud de cambios, teclea alguna de las siguientes palabras clave seguida de una referencia a la propuesta. Por ejemplo, `Closes #10` o `Fixes octo-org/octo-repo#100`. +To link a pull request to an issue to show that a fix is in progress and to automatically close the issue when someone merges the pull request, type one of the following keywords followed by a reference to the issue. Por ejemplo, `Closes #10` o `Fixes octo-org/octo-repo#100`. * close * closes diff --git a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md new file mode 100644 index 0000000000..2323c26988 --- /dev/null +++ b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md @@ -0,0 +1,59 @@ +--- +title: Writing mathematical expressions +intro: 'Use Markdown to display mathematical expressions on {% data variables.product.company_short %}.' +versions: + feature: math +shortTitle: Mathematical expressions +--- + +To enable clear communication of mathematical expressions, {% data variables.product.product_name %} supports LaTeX formatted math within Markdown. For more information, see [LaTeX/Mathematics](http://en.wikibooks.org/wiki/LaTeX/Mathematics) in Wikibooks. + +{% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide). + +## Writing inline expressions + +To include a math expression inline with your text, delimit the expression with a dollar symbol `$`. + +``` +This sentence uses `$` delimiters to show math inline: $\sqrt{3x-1}+(1+x)^2$ +``` + +![Inline math markdown rendering](/assets/images/help/writing/inline-math-markdown-rendering.png) + +## Writing expressions as blocks + +To add a math expression as a block, start a new line and delimit the expression with two dollar symbols `$$`. + +``` +**The Cauchy-Schwarz Inequality** + +$$\left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right)$$ +``` + +![Math expression as a block rendering](/assets/images/help/writing/math-expression-as-a-block-rendering.png) + +## Writing dollar signs in line with and within mathematical expressions + +To display a dollar sign as a character in the same line as a mathematical expression, you need to escape the non-delimiter `$` to ensure the line renders correctly. + + - Within a math expression, add a `\` symbol before the explicit `$`. + + ``` + This expression uses `\$` to display a dollar sign: $\sqrt{\$4}$ + ``` + + ![Dollar sign within math expression](/assets/images/help/writing/dollar-sign-within-math-expression.png) + + - Outside a math expression, but on the same line, use span tags around the explicit `$`. + + ``` + To split $100 in half, we calculate $100/2$ + ``` + + ![Dollar sign inline math expression](/assets/images/help/writing/dollar-sign-inline-math-expression.png) + +## Leer más + +* [The MathJax website](http://mathjax.org) +* [Introducción a la escritura y el formato en GitHub](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github) +* [GitHub Flavored Markdown Spec](https://github.github.com/gfm/) diff --git a/translations/es-ES/content/github/copilot/about-github-copilot-telemetry.md b/translations/es-ES/content/github/copilot/about-github-copilot-telemetry.md index 57df9b34a6..7cf6f8d5a7 100644 --- a/translations/es-ES/content/github/copilot/about-github-copilot-telemetry.md +++ b/translations/es-ES/content/github/copilot/about-github-copilot-telemetry.md @@ -9,7 +9,7 @@ versions: ## Qué datos se recolectan -Los datos que se recolectan se describen en los "[Términos de telemetría del {% data variables.product.prodname_copilot %}](/github/copilot/github-copilot-telemetry-terms)". Adicionalmente, la extensión/aditamento del {% data variables.product.prodname_copilot %} recopila la actividad de el Ambiente de Desarrollo Integrado (IDE) del usuario, ligado con una marca de tiempo y los metadatos que recopila el paquete de telemetría de extensión/aditamento. Cuando se utiliza con Visual Studio Code, IntelliJ, NeoVM u otros IDE, el {% data variables.product.prodname_copilot %} recopila los metadatos estándar que proporcionan dichos IDE. +Los datos que se recolectan se describen en los "[Términos de telemetría del {% data variables.product.prodname_copilot %}](/github/copilot/github-copilot-telemetry-terms)". Adicionalmente, la extensión/aditamento del {% data variables.product.prodname_copilot %} recopila la actividad de el Ambiente de Desarrollo Integrado (IDE) del usuario, ligado con una marca de tiempo y los metadatos que recopila el paquete de telemetría de extensión/aditamento. Cuando se utiliza con {% data variables.product.prodname_vscode %}, IntelliJ, NeoVIM o con otro IDE, {% data variables.product.prodname_copilot %} recopila los metadatos estándar que proporcionan dichos IDE. ## Cómo {% data variables.product.company_short %} utiliza los datos diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md index 31fd567c1e..76fb5aeb94 100644 --- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md +++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md @@ -30,8 +30,8 @@ También puedes usar la barra de búsqueda "Filtrar tarjetas" en la parte superi - Filtrar por comprobación de estado usando `status:pending`, `status:success` o `status:failure` - Filtrar tarjetas por tipo usando `type:issue`, `type:pr` o `type:note` - Filtrar tarjetas por estado y tipo usando `is:open`, `is:closed` o `is:merged` y `is:issue`, `is:pr` o `is:note` -- Filtrar tarjetas por informes de problemas que se enlazan con alguna solicitud de extracción mediante una referencia de cierre utilizando `linked:pr`{% ifversion fpt or ghes or ghae or ghec %} -- Filtrar tarjetas por repositorio en un tablero de proyecto de toda la organización utilizando `repo:ORGANIZATION/REPOSITORY`{% endif %} +- Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr` +- Filtrar tarjetas por repositorio en un tablero de proyecto de toda la organización usando `repo:ORGANIZATION/REPOSITORY` 1. Dirígete al tablero de proyecto que contenga las tarjetas que desees filtrar. 2. Sobre las columnas de las tarjetas del proyecto, haz clic en la barra de búsqueda "Filtrar tarjetas" y escribe la consulta de búsqueda para filtrar las tarjetas. ![Barra de búsqueda Filtrar tarjetas](/assets/images/help/projects/filter-card-search-bar.png) diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md index 00691e74a8..aa93f1927e 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/about-issues.md @@ -22,7 +22,7 @@ topics: Las propuestas te permiten rastrear tu trabajo en {% data variables.product.company_short %}, donde sucede el desarrollo. Cuando mencionas una propuesta en otra propuesta o solicitud de cambios, la línea de tiempo de la propuesta refleja la referencia cruzada para que puedas rastrear el trabajo relacionado. Para indicar que el trabajo está en curso, puedes enlazar una propeusta a una solicitud de cambios. Cuando la solicitud de cambios se fusiona, la propuesta enlazada se cierra automáticamente. -For more information on keywords, see "[Linking a pull request to an issue](issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)." +Para obtener más información sobre las palabras clave, consulta la sección "[enlazar una solicitud de cambios a una propuesta](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)". ## Crea propuestas rápidamente @@ -36,7 +36,7 @@ Para obtener más información sobre los proyectos, consulta las secciones {% if ## Mantente actualizado -Para mantenerte actualizado sobre la mayoría de los comentarios recientes de una propuesta, puedes suscribirte a ella para recibir notificaciones sobre las confirmaciones más recientes. Para encontrar rápidamente los enlaces a los informes de problemas recientemente actualizados a los cuales te has suscrito, visita tu tablero. Para obtener más información, consulta la sección {% ifversion fpt or ghes or ghae or ghec %}"[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Acerca de las notificaciónes](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}" y "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". +Para mantenerte actualizado sobre la mayoría de los comentarios recientes de una propuesta, puedes suscribirte a ella para recibir notificaciones sobre las confirmaciones más recientes. Para encontrar rápidamente los enlaces a los informes de problemas recientemente actualizados a los cuales te has suscrito, visita tu tablero. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" y "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)". ## Administración de comunidad diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md index c3185a5523..c9460f71f9 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md @@ -19,7 +19,9 @@ shortTitle: Asignar propuestas & solicitudes de cambio ## Acerca de los asignatarios de las propuestas y solicitudes de cambios -Puedes asignar hasta 10 personas a cada propuesta o solicitud de cambios, incluyéndote a ti mismo, a cualquiera que haya comentado en la propuesta o solicitud de cambios, a cualquiera con permisos de escritura en el repositorio y a los miembros de la organización con permisos de lectura en el repositorio. Para obtener más información, consulta "[Permisos de acceso en {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)". +Puedes asignar a varias personas a cada propuesta o solicitud de cambios, incluyendo a ti mismo, a cualquiera que haya comentado en la propuesta o solicitud de cambios, a cualquiera con permisos de escritura en el repositorio y a los miembros de la organización con permisos de lectura en dicho repositorio. Para obtener más información, consulta "[Permisos de acceso en {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)". + +Se puede tener hasta 10 personas asignadas en las propuestas y solicitudes de cambio en los repositorios públicos y en los privados de una cuenta de pago. Los repositorios privados en el plan gratuito se limitan a una persona por propuesta o solicitud de cambios. ## Asignar una propuesta o solicitud de cambios individual diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index cf85394183..5c162949b5 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -178,11 +178,9 @@ With issue and pull request search terms, you can: {% endtip %} {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} For issues, you can also use search to: - Filter for issues that are linked to a pull request by a closing reference: `linked:pr` -{% endif %} For pull requests, you can also use search to: - Filter [draft](/articles/about-pull-requests#draft-pull-requests) pull requests: `is:draft` @@ -193,8 +191,8 @@ For pull requests, you can also use search to: - Filter pull requests by [reviewer](/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 %} -- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %} -- Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue`{% endif %} +- Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/atom` +- Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue` ## Sorting issues and pull requests @@ -217,7 +215,6 @@ You can sort any filtered view by: To clear your sort selection, click **Sort** > **Newest**. - ## Sharing filters When you filter or sort issues and pull requests, your browser's URL is automatically updated to match the new view. diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md index 2f4e2d02b8..479c147c68 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md @@ -26,7 +26,7 @@ shortTitle: Link PR to issue ## About linked issues and pull requests -You can link an issue to a pull request {% ifversion fpt or ghes or ghae or ghec %}manually or {% endif %}using a supported keyword in the pull request description. +You can link an issue to a pull request manually or using a supported keyword in the pull request description. When you link a pull request to the issue the pull request addresses, collaborators can see that someone is working on the issue. @@ -56,11 +56,10 @@ Issue in the same repository | *KEYWORD* #*ISSUE-NUMBER* | `Closes #10` Issue in a different repository | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100` Multiple issues | Use full syntax for each issue | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` -{% ifversion fpt or ghes or ghae or ghec %}Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword.{% endif %} +Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword. You can also use closing keywords in a commit message. The issue will be closed when you merge the commit into the default branch, but the pull request that contains the commit will not be listed as a linked pull request. -{% ifversion fpt or ghes or ghae or ghec %} ## Manually linking a pull request to an issue Anyone with write permissions to a repository can manually link a pull request to an issue. @@ -78,7 +77,6 @@ You can manually link up to ten issues to each pull request. The issue and pull {% endif %} 5. Click the issue you want to link to the pull request. ![Drop down to link issue](/assets/images/help/pull_requests/link-issue-drop-down.png) -{% endif %} ## Further reading diff --git a/translations/es-ES/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md b/translations/es-ES/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md index 0fb7b586fe..bedd78a4d8 100644 --- a/translations/es-ES/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md +++ b/translations/es-ES/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md @@ -25,4 +25,4 @@ Tus tableros de propuestas y solicitudes de extracción están disponibles en la ## Leer más -- {% ifversion fpt or ghes or ghae or ghec %}"[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}"[Listar los repositorios que estás observando](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}" +- "[Ver tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching)" diff --git a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/creating-a-project.md index 0f9ced276f..eddf698cb9 100644 --- a/translations/es-ES/content/issues/trying-out-the-new-projects-experience/creating-a-project.md +++ b/translations/es-ES/content/issues/trying-out-the-new-projects-experience/creating-a-project.md @@ -163,7 +163,7 @@ Los campos personalizados pueden ser de texto, número, fecha, selección simple 6. Si especificaste **Selección simple** como el tipo, ingresa las opciones. 7. Si especificaste **Iteración** como el tipo, ingresa la fecha de inicio de la primera iteración y la duración de la misma. Se crearán tres iteraciones automáticamente y podrás agregar iteraciones adicionales en la página de ajustes del proyecto. -You can also edit your custom fields. +También puedes editar tus campos personalizados. {% data reusables.projects.project-settings %} 1. Debajo de **Campos**, selecciona aquél que quieras editar. diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md index 58a9b63236..6ab2e4d91a 100644 --- a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md +++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -35,7 +35,7 @@ En la barra lateral izquierda de tu tablero, puedes acceder a los principales re En la sección "All activity" (Toda la actividad) de tus noticias, puedes ver actualizaciones de otros equipos y repositorios en tu organización. -La sección "All activity" (Toda la actividad) muestra toda la actividad reciente en la organización, incluida la actividad en los repositorios a los que no estás suscrito y de las personas que no sigues. Para obtener más información, consulta las secciones {% ifversion fpt or ghes or ghae or ghec %}"[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Observar y dejar de observar los repositorios](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}" y "[Seguir a las personas](/articles/following-people)". +La sección "All activity" (Toda la actividad) muestra toda la actividad reciente en la organización, incluida la actividad en los repositorios a los que no estás suscrito y de las personas que no sigues. Para obtener más información, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" y "[Seguir a las personas](/articles/following-people)". Por ejemplo, las noticias de la organización muestran actualizaciones cuando alguien en la organización: - Crea una rama nueva. diff --git a/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md index c6fcbe38ea..60d0d28354 100644 --- a/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md +++ b/translations/es-ES/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -32,7 +32,7 @@ Cuando alguien publica o responde a un debate público en la página de un equip {% tip %} -**Sugerencia:** Dependiendo de los parámetros de tu notificación, recibirás actualizaciones por correo electrónico, la página de notificaciones web en {% data variables.product.product_name %}, o ambas. Para obtener más información, consulta las secciones {% ifversion fpt or ghae or ghes or ghec %}"[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}[Acerca de las notificaciones por correo electrónico](/github/receiving-notifications-about-activity-on-github/about-email-notifications)" y "[Acerca de las notificaciones web](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}". +**Sugerencia:** Dependiendo de los parámetros de tu notificación, recibirás actualizaciones por correo electrónico, la página de notificaciones web en {% data variables.product.product_name %}, o ambas. Para obtener más información, consulta la sección "[Configurar las notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)". {% endtip %} @@ -40,7 +40,7 @@ Por defecto, si se menciona tu nombre de usuario en un debate del equipo, recibi Para apagar las notificaciones para los debates del equipo, puedes cancelar la suscripción a una publicación de debate específica o cambiar tus parámetros de notificación para dejar de ver o ignorar por completo los debtaes de un equipo específico. Te puedes suscribir a las notificaciones para la publicación de un debate específico incluso si dejaste de ver los debates de ese equipo. -Para obtener más información, consulta la sección {% ifversion fpt or ghae or ghes or ghec %}"[Visualizar tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Suscribirte y desuscribirte de las notificaciones](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" y "[Equipos anidados](/articles/about-teams/#nested-teams)". +Para obtener más información, consulta la sección "[Ver tus suscripciones](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)" y "[Equipos anidados](/articles/about-teams/#nested-teams)". {% ifversion fpt or ghec %} diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md index 0fb25f6b1d..90f62c3e0d 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md @@ -156,5 +156,5 @@ Puedes administrar el acceso a las características de la {% data variables.prod - "[Asegurar tu repositorio](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %} - "[Acerca del escaneo de secretos](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %} -- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae-issue-4864 %} +- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae %} - "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)"{% endif %} diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index 0953732065..79a0b10092 100644 --- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -41,7 +41,7 @@ Para buscar eventos específicos, utiliza el calificador `action` en tu consulta | [`advisory_credit`](#advisory_credit-category-actions) | Contiene todas las actividades relacionadas con darle crédito a un contribuyente por una asesoría de seguridad en la {% data variables.product.prodname_advisory_database %}. Para obtener más información, consulta la sección "[Acerca de las asesorías de seguridad de {% data variables.product.prodname_dotcom %}](/github/managing-security-vulnerabilities/about-github-security-advisories)". | | [`facturación`](#billing-category-actions) | Contiene todas las actividades relacionadas con la facturación de tu organización. | | [`business`](#business-category-actions) | Contiene actividades relacionadas con los ajustes de negocios para una empresa. | -| [`codespaces`](#codespaces-category-actions) | Contiene todas las actividades relacionadas con los codespaces de tu organización. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +| [`codespaces`](#codespaces-category-actions) | Contiene todas las actividades relacionadas con los codespaces de tu organización. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %} | [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contiene las actividades de configuración a nivel organizacional para las {% data variables.product.prodname_dependabot_alerts %} en los repositorios existentes. Para obtener más información, consulta la sección "[Acerca de{% data variables.product.prodname_dependabot_alerts %}](/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.{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %} | [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contiene las actividades de configuración a nivel organizacional para las {% data variables.product.prodname_dependabot_security_updates %} en los repositorios existentes. Para obtener más información, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". | @@ -61,8 +61,8 @@ Para buscar eventos específicos, utiliza el calificador `action` en tu consulta | [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contiene todas las actividades relacionadas con administrar la publicación de sitios de {% data variables.product.prodname_pages %} para los repositorios en la organización. Para obtener más información, consulta la sección "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". |{% endif %} | [`org`](#org-category-actions) | Contiene actividades relacionadas con la membrecía organizacional.{% ifversion ghec %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contiene todas las actividades relacionadas con la autorización de credenciales para su uso con el inicio de sesión único de SAML. {% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)". |{% endif %}{% ifversion fpt or ghes or ghae or ghec %} -| [`organization_label`](#organization_label-category-actions) | Contiene todas las actividades relacionadas con las etiquetas predeterminadas para los repositorios de tu organización.{% endif %} +| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)". |{% endif %} +| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization. | | [`oauth_application`](#oauth_application-category-actions) | Contiene todas las actividades relacionadas con las Apps de OAuth. | | [`paquetes`](#packages-category-actions) | Contiene todas las actividades relacionadas con el {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %} | [`payment_method`](#payment_method-category-actions) | Contiene todas las actividades relacionadas con la manera en que tu organización le paga a GitHub.{% endif %} @@ -76,7 +76,7 @@ Para buscar eventos específicos, utiliza el calificador `action` en tu consulta | repositorio {% ifversion fpt or ghec %}privado{% endif %}. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".{% endif %}{% ifversion ghes or ghae or ghec %} | | | [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contiene actividades a nivel de repositorio relacionadas con el escaneo de secretos. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning). |{% endif %}{% if secret-scanning-audit-log-custom-patterns %} | [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions) | Contiene actividades a nivel de repositorio relacionadas con los patrones personalizados del escaneo de secretos. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)". |{% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contiene actividades a nivel de repositorio relacionadas con los patrones personalizados del escaneo de secretos. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." |{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contiene actividades a nivel de repositorio relacionadas con los patrones personalizados del escaneo de secretos. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." |{% endif %}{% ifversion fpt or ghes or ghae or ghec %} | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contiene todas las actividades relacionadas con [las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %} | [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contiene actividades de configuración a nivel de repositorio para las {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% if custom-repository-roles %} | [`rol`](#role-category-actions) | Contiene todas las actividades relacionadas con los [roles de repositorio personalziados](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %} @@ -237,7 +237,7 @@ Un resumen de algunas de las acciones más comunes que se registran como eventos | `manage_access_and_security` | Se activa cuando un usuario actualiza [a cuáles repositorios puede acceder un codespace](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). | {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{% ifversion fpt or ghec or ghes > 3.2 or ghae %} ### Acciones de la categoría `dependabot_alerts` | Acción | Descripción | @@ -499,7 +499,6 @@ Para obtener más información, consulta la sección "[Administrar la publicaci | `delete` | Triggered when a custom pattern is removed from secret scanning in an organization. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)". | {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} ### Acciones de la categoría `organization_label` | Acción | Descripción | @@ -508,8 +507,6 @@ Para obtener más información, consulta la sección "[Administrar la publicaci | `actualización` | Se activa cuando se edita una etiqueta por defecto. | | `destroy (destruir)` | Se activa cuando se elimina una etiqueta por defecto. | -{% endif %} - ### acciones de la categoría `oauth_application` | Acción | Descripción | @@ -574,11 +571,10 @@ Para obtener más información, consulta la sección "[Administrar la publicaci | `update_required_status_checks_enforcement_level (actualizar nivel de aplicación de verificaciones de estado requeridas)` | Se activa cuando se actualiza en una rama la aplicación de verificaciones de estado requeridas. | | `update_strict_required_status_checks_policy` | Se activa cuando se cambia el requisito para que una rama se encuentre actualizada antes de la fusión. | | `rejected_ref_update (actualización de referencia rechazada)` | Se activa cuando se rechaza el intento de actualización de una rama. | -| `policy_override (anulación de política)` | Se activa cuando un administrador del repositorio invalida un requisito de protección de la rama. {% ifversion fpt or ghes or ghae or ghec %} +| `policy_override (anulación de política)` | Se activa cuando un administrador del repositorio anula el requisito de protección de una rama. | | `update_allow_force_pushes_enforcement_level` | Se activa cuando se habilitan o inhabilitan las subidas de información forzadas en una rama protegida. | | `update_allow_deletions_enforcement_level` | Se activa cuando se habilita o inhabilita el borrado de ramas en una rama protegida. | | `update_linear_history_requirement_enforcement_level` | Se activa cuando se habilita o inhabilita el historial de confirmaciones linear requerido para una rama protegida. | -{% endif %} {% ifversion fpt or ghes > 3.1 or ghae or ghec %} @@ -709,7 +705,7 @@ Para obtener más información, consulta la sección "[Administrar la publicaci | `inhabilitar` | Se activa cuando un propietario del repositorio o persona con acceso administrativo al mismo inhabilita el escaneo de secretos para un repositorio. Para obtener más información, consulta la sección "[Proteger las subidas de información con el escaneo de secretos](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". | | `habilitar` | Se activa cuando un propietario del repositorio o persona con acceso administrativo al mismo habilita el escaneo de secretos para un repositorio. | -{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% endif %}{% ifversion fpt or ghes or ghae or ghec %} ### acciones de la categoría `repository_vulnerability_alert` | Acción | Descripción | diff --git a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index 0a30561f90..b066eaede4 100644 --- a/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -152,18 +152,18 @@ Some of the features listed below are limited to organizations using {% data var In this section, you can find the access required for security features, such as {% data variables.product.prodname_advanced_security %} features. | Repository action | Read | Triage | Write | Maintain | Admin | -|:---|:---:|:---:|:---:|:---:|:---:| {% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +|:---|:---:|:---:|:---:|:---:|:---:| {% ifversion fpt or ghes or ghae or ghec %} | Receive [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | -| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %} +| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} | Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 or ghec %} +| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae or ghec %} | [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %} | [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | | [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | | [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} -| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %} +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **X** |{% endif %} [1] Repository writers and maintainers can only see alert information for their own commits. diff --git a/translations/es-ES/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md b/translations/es-ES/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md index 3e53f6b979..9ac00d4bc7 100644 --- a/translations/es-ES/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md +++ b/translations/es-ES/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md @@ -5,8 +5,6 @@ permissions: Organization owners can export member information for their organiz versions: fpt: '*' ghec: '*' - ghes: '>=3.3' - ghae: issue-5146 topics: - Organizations - Teams diff --git a/translations/es-ES/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/es-ES/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md index 8c989dfce9..8111066c71 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -26,8 +26,8 @@ shortTitle: Convert organization to user 2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner). 3. {% data variables.product.signin_link %} to the new personal account. 4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new personal account. -5. [Rename the organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) to make the current username available. -6. [Rename the user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) to the organization's name. +5. [Rename the organization](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username) to make the current username available. +6. [Rename the user](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username) to the organization's name. 7. [Delete the organization](/organizations/managing-organization-settings/deleting-an-organization-account). diff --git a/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index f249484779..112afc6286 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -103,14 +103,14 @@ Puedes configurar este comportamiento de una organización utilizando los siguie {% data reusables.actions.workflow-permissions-intro %} -Puedes configurar los permisos predeterminados para el `GITHUB_TOKEN` en la configuración de tu organización o tus repositorios. If you select a restrictive option as the default in your organization settings, the same option is selected in the settings for repositories within your organization, and the permissive option is disabled. If your organization belongs to a {% data variables.product.prodname_enterprise %} account and a more restrictive default has been selected in the enterprise settings, you won't be able to select the more permissive default in your organization settings. +Puedes configurar los permisos predeterminados para el `GITHUB_TOKEN` en la configuración de tu organización o tus repositorios. Si seleccionas una opción restrictiva como la predeterminada en los ajustes de tu organización, la misma opción se selecciona en los ajustes para los repositorios dentro de tu organización y la opción permisiva se inhabilita. Si tu organización le pertenece a una cuenta de {% data variables.product.prodname_enterprise %} y se seleccionaron opciones predeterminadas más restrictivas en los ajustes de la empresa, no podrás seleccionar el predeterminado más permisivo en tus ajustes de organización. {% data reusables.actions.workflow-permissions-modifying %} ### Configuring the default `GITHUB_TOKEN` permissions {% if allow-actions-to-approve-pr-with-ent-repo %} -By default, when you create a new organization, `GITHUB_TOKEN` only has read access for the `contents` scope. +Predeterminadamente, cuando creas una organización nueva, `GITHUB_TOKEN` solo tiene acceso de lectura para el alcance `contents`. {% endif %} {% data reusables.profile.access_profile %} @@ -127,15 +127,15 @@ By default, when you create a new organization, `GITHUB_TOKEN` only has read acc {% data reusables.actions.workflow-pr-approval-permissions-intro %} -By default, when you create a new organization, workflows are not allowed to {% if allow-actions-to-approve-pr-with-ent-repo %}create or {% endif %}approve pull requests. +Predeterminadamente, cuando creas una organización nueva, no se permite que los flujos de trabajo {% if allow-actions-to-approve-pr-with-ent-repo %}creen o {% endif %}aprueben las solicitudes de cambio. {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions-general %} -1. Under "Workflow permissions", use the **Allow GitHub Actions to {% if allow-actions-to-approve-pr-with-ent-repo %}create and {% endif %}approve pull requests** setting to configure whether `GITHUB_TOKEN` can {% if allow-actions-to-approve-pr-with-ent-repo %}create and {% endif %}approve pull requests. +1. Debajo de "Permisos de flujo de trabajo", utiliza el ajuste **Permitir que GitHub Actions {% if allow-actions-to-approve-pr-with-ent-repo %}creen y {% endif %}aprueben las solicitudes de cambios** para configurar si el `GITHUB_TOKEN` puede {% if allow-actions-to-approve-pr-with-ent-repo %}crear y {% endif %}aprobar las solicitudes de cambios. - ![Set GITHUB_TOKEN pull request approval permission for this organization](/assets/images/help/settings/actions-workflow-permissions-organization{% if allow-actions-to-approve-pr %}-with-pr-{% if allow-actions-to-approve-pr-with-ent-repo %}creation-{% endif %}approval{% endif %}.png) + ![Configurar el permiso de aprobación de solicitudes de cambio del GITHUB_TOKEN para esta organización](/assets/images/help/settings/actions-workflow-permissions-organization{% if allow-actions-to-approve-pr %}-with-pr-{% if allow-actions-to-approve-pr-with-ent-repo %}creation-{% endif %}approval{% endif %}.png) 1. Da clic en **Guardar** para aplicar la configuración. {% endif %} diff --git a/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md index faae9ba5a0..b2afa01bf1 100644 --- a/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md +++ b/translations/es-ES/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md @@ -16,13 +16,13 @@ shortTitle: Configurar la política de cambios de visibilidad permissions: Organization owners can restrict repository visibility changes for an organization. --- -You can restrict who has the ability to change the visibility of repositories in your organization, such as changing a repository from private to public. For more information about repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." +Puedes restringir quién tiene la capacidad de cambiar la visibilidad de los repositorios en tu organización, tal como cambiarlo de privado a público. Para obtener más información acerca de la visibilidad de los repositorios, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". -You can restrict the ability to change repository visibility to organization owners only, or you can allow anyone with admin access to a repository to change visibility. +Puedes restringir la capacidad de cambiar la visibilidad de los repositorios para que solo lo puedan hacer los propietarios de las organizaciones o puedes permitir que cualquier persona con permisos administrativos en dicho repositorio lo pueda hacer. {% warning %} -**Warning**: If enabled, this setting allows people with admin access to choose any visibility for an existing repository, even if you do not allow that type of repository to be created. Para obtener más información acerca de cómo restringir la visibilidad de los repositorios durante su creación, consulta la sección "[Restringir la creación de repositorios en tu organización](/articles/restricting-repository-creation-in-your-organization)". +**Advertencia**: De habilitarse, este ajuste permite que las personas con acceso administrativo elijan cualquier tipo de visibilidad en un repositorio existente, incluso si no permites que se cree ese tipo de repositorio. Para obtener más información acerca de cómo restringir la visibilidad de los repositorios durante su creación, consulta la sección "[Restringir la creación de repositorios en tu organización](/articles/restricting-repository-creation-in-your-organization)". {% endwarning %} diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md index 6a160a2236..7cf8eb37fe 100644 --- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md @@ -2,8 +2,6 @@ title: Gestionar a los administradores de seguridad en tu organización intro: Puedes otorgar a tu equipo de seguridad el menor tipo de acceso que necesiten en tu organización si asignas un equipo al rol de administrador de seguridad. versions: - fpt: '*' - ghes: '>=3.3' feature: security-managers topics: - Organizations @@ -30,7 +28,7 @@ Los miembros de un equipo que tengan el rol de administrador de seguridad solo t Puedes encontrar funcionalidades adicionales disponibles, incluyendo un resumen de seguridad de la organización, en las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} con la {% data variables.product.prodname_advanced_security %}. Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). {% endif %} -Si un equipo tiene el rol de administrador de seguridad, las personas con acceso administrativo al equipo y a un repositorio específico pueden cambiar el nivel de acceso de dicho equipo al repositorio pero no pueden eliminar el acceso. Para obtener más información, consulta las secciones "[Administrar el acceso de los equipos aun repositorio organizacional](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion ghes %}".{% else %} y "[Administrar a los equipos y personas con acceso a tu repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)".{% endif %} +Si un equipo tiene el rol de administrador de seguridad, las personas con acceso administrativo al equipo y a un repositorio específico pueden cambiar el nivel de acceso de dicho equipo al repositorio pero no pueden eliminar el acceso. 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){% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %}" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% else %}."{% endif %} ![Administrar la IU de acceso al repositorio con administradores de seguridad](/assets/images/help/organizations/repo-access-security-managers.png) diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md index 256e5a43c6..8e51209f92 100644 --- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md +++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md @@ -139,7 +139,7 @@ Some of the features listed below are limited to organizations using {% data var | Enable team synchronization (see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)") | **X** | | | | |{% endif %} | Manage pull request reviews in the organization (see "[Managing pull request reviews in your organization](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)") | **X** | | | | | -{% elsif ghes > 3.2 or ghae-issue-4999 %} +{% elsif ghes > 3.2 or ghae %} | Organization action | Owners | Members | Security managers | diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/about-teams.md b/translations/es-ES/content/organizations/organizing-members-into-teams/about-teams.md index 052dc5b6af..a48986bd53 100644 --- a/translations/es-ES/content/organizations/organizing-members-into-teams/about-teams.md +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/about-teams.md @@ -37,7 +37,7 @@ You can also use LDAP Sync to synchronize {% data variables.product.product_loca {% data reusables.organizations.types-of-team-visibility %} -You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)." +You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)." ## Team pages diff --git a/translations/es-ES/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md b/translations/es-ES/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md index 3ba1381466..529bd42969 100644 --- a/translations/es-ES/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md +++ b/translations/es-ES/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md @@ -31,11 +31,10 @@ Las personas con el rol de mantenedor de equipo pueden administrar la membrecía - [Eliminar debates de equipo](/articles/managing-disruptive-comments/#deleting-a-comment) - [Agregar a miembros de la organización al equipo](/articles/adding-organization-members-to-a-team) - [Eliminar a miembros de la organización del equipo](/articles/removing-organization-members-from-a-team) -- Eliminar el acceso del equipo a los repositorios {% ifversion fpt or ghes or ghae or ghec %} -- [Administrar una tarea de revisión de código para el equipo](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% ifversion fpt or ghec %} +- Eliminar el acceso del equipo a los repositorios +- [Administrar una tarea de revisión de código para el equipo](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% ifversion fpt or ghec %} - [Administrar los recordatorios programados para las solicitudes de extracción](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %} - ## Promover un miembro de la organización a mantenedor del equipo Antes de que puedas promover a un miembro de la organización a mantenedor de equipo, esta persona debe ser primero un miembro de dicho equipo. diff --git a/translations/es-ES/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/translations/es-ES/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md index ba3cbb0e78..b7ee60b3a5 100644 --- a/translations/es-ES/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md +++ b/translations/es-ES/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md @@ -33,12 +33,12 @@ Si conectas un repositorio a un paquete, la página de llegada de dicho paquete {% data reusables.package_registry.container-registry-ghes-beta %} {% endif %} -1. In your Dockerfile, add this line, replacing {% ifversion ghes %}`HOSTNAME`, {% endif %}`OWNER` and `REPO` with your details: +1. En tu Dockerfile, agrega esta línea reemplazando a {% ifversion ghes %}`HOSTNAME`, {% endif %}`OWNER` y `REPO` con tu información: ```shell LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPO ``` - For example, if you're the user `monalisa` and own `my-repo`, and {% data variables.product.product_location %} hostname is `github.companyname.com`, you would add this line to your Dockerfile: + Por ejemplo, si eres el usuario `monalisa` y eres el propietario de `my-repo` y el nombre del host de {% data variables.product.product_location %} es `github.companyname.com`, deberás agregar esta línea a tu Dockerfile: ```shell LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}{% data reusables.package_registry.container-registry-example-hostname %}{% endif %}/monalisa/my-repo ``` diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md index c9c3cd6c73..d6d58a197b 100644 --- a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md +++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md @@ -1,6 +1,6 @@ --- title: Trabajar con el registro de contenedores -intro: 'You can store and manage Docker and OCI images in the {% data variables.product.prodname_container_registry %}, which uses the package namespace `https://{% data reusables.package_registry.container-registry-hostname %}`.' +intro: 'Puedes almacenar y administrar imágenes de Docker y de OCI en el {% data variables.product.prodname_container_registry %}, el cual utiliza el designador de nombre de paquete `https://{% data reusables.package_registry.container-registry-hostname %}`.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images @@ -22,7 +22,7 @@ shortTitle: Registro de contenedores {% ifversion ghes > 3.4 %} {% note %} -**Note**: {% data variables.product.prodname_container_registry %} is currently in beta for {% data variables.product.product_name %} and subject to change. +**Nota:**: {% data variables.product.prodname_container_registry %} se encuentra actualmente en beta para {% data variables.product.product_name %} y está sujeto a cambios. {% endnote %} {% endif %} @@ -30,7 +30,7 @@ shortTitle: Registro de contenedores {% ifversion ghes > 3.4 %} ## Prerrequisitos -To configure and use the {% data variables.product.prodname_container_registry %} on {% data variables.product.prodname_ghe_server %}, your site administrator must first enable {% data variables.product.prodname_registry %} **and** subdomain isolation. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" and "[Enabling subdomain isolation](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)." +Para configurar y utilizar el {% data variables.product.prodname_container_registry %} en {% data variables.product.prodname_ghe_server %}, tu administrador de sitio primero debe habilitar el {% data variables.product.prodname_registry %} **y** el aislamiento de subdominios. Para obtener más información, consulta las secciones "[Iniciar con GitHub Packages para tu empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" y "[Habilitar el aislamiento de subdominios](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)". {% endif %} ## Acerca del soporte para el {% data variables.product.prodname_container_registry %} @@ -45,7 +45,7 @@ Cuando instalas o publicas una imagen de Docker, el {% data variables.product.pr {% data reusables.package_registry.authenticate_with_pat_for_container_registry %} -{% ifversion ghes %}Ensure that you replace `HOSTNAME` with {% data variables.product.product_location_enterprise %} hostname or IP address in the examples below.{% endif %} +{% ifversion ghes %}Asegúrate de reemplazar a `HOSTNAME` con el nombre de host o dirección IP de {% data variables.product.product_location_enterprise %} en los siguientes ejemplos.{% endif %} {% data reusables.package_registry.authenticate-to-container-registry-steps %} diff --git a/translations/es-ES/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/es-ES/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index cdeecd6128..b9384c4987 100644 --- a/translations/es-ES/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/translations/es-ES/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -15,7 +15,7 @@ Con control de acceso para {% data variables.product.prodname_pages %}, puedes r {% data reusables.pages.privately-publish-ghec-only %} -If your enterprise uses {% data variables.product.prodname_emus %}, access control is not available, and all {% data variables.product.prodname_pages %} sites are only accessible to other enterprise members. Para obtener más información acerca de {% data variables.product.prodname_emus %}, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)". +Si tu empresa utiliza {% data variables.product.prodname_emus %}, el control de acceso no está disponible y solo otros miembros de la empresa podrán acceder a todos los sitios de {% data variables.product.prodname_pages %}. Para obtener más información acerca de {% data variables.product.prodname_emus %}, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)". Si tu organización utiliza {% data variables.product.prodname_ghe_cloud %} sin {% data variables.product.prodname_emus %}, puedes elegir publicar tus sitios en privado o al público para cualquiera en la internet. El control de accesos se encuentra disponible para los sitios de proyecto que se publican desde un repositorio privado o interno que pertenezca a la organización. No puedes administrar el control de accesos para el sitio de una organización. Para obtener más información sobre los tipos de sitios de {% data variables.product.prodname_pages %}, consulta la sección "[Acerca de {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)". diff --git a/translations/es-ES/content/pages/index.md b/translations/es-ES/content/pages/index.md index 69e8cdb61b..4327272784 100644 --- a/translations/es-ES/content/pages/index.md +++ b/translations/es-ES/content/pages/index.md @@ -1,7 +1,34 @@ --- title: Documentación de GitHub Pages shortTitle: Páginas de GitHub -intro: 'Puedes crear un sitio web directamente desde un repositorio en {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.' +intro: 'Aprende cómo crear un sitio web directamente desde un repositorio en{% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Explora las herramientas de creación de sitios web como Jekyll y soluciona los problemas de tu sitio de {% data variables.product.prodname_pages %}.' +introLinks: + quickstart: /pages/quickstart + overview: /pages/getting-started-with-github-pages/about-github-pages +featuredLinks: + guides: + - /pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site + - /pages/getting-started-with-github-pages/creating-a-github-pages-site + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll{% endif %}' + - '{% ifversion ghec %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site{% endif %}' + - '{% ifversion fpt %}/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll{% endif %}' + popular: + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages{% endif %}' + - /pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll) + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages{% endif %}' + - '{% ifversion fpt or ghec %}/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https{% endif %}' + - '{% ifversion ghes or ghae %}/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll{% endif %}' + guideCards: + - /pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site + - /pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll + - /pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites +changelog: + label: pages +layout: product-landing redirect_from: - /categories/20/articles - /categories/95/articles diff --git a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md index 437902afcb..0048e68c58 100644 --- a/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md +++ b/translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -49,7 +49,7 @@ Las personas con permisos de escritura para un repositorio pueden agregar un tem --- --- - @import "{{ site.theme }}"; + @import "{% raw %}{{ site.theme }}{% endraw %}"; ``` 3. Agrega cualquier CSS o Sass personalizado que quieras (incluidas importaciones) inmediatamente después de la línea `@import`. diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md index cdec1046a8..f6b0db8135 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md @@ -23,13 +23,17 @@ topics: ### Merge message for a squash merge -When you squash and merge, {% data variables.product.prodname_dotcom %} generates a commit message which you can change if you want to. The message default depends on whether the pull request contains multiple commits or just one. We do not include merge commits when we count the total number of commits. +When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. The default message depends on the number of commits in the pull request, not including merge commits. Number of commits | Summary | Description | ----------------- | ------- | ----------- | One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order +{% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %} +People with admin access to a repository can configure the repository to use the title of the pull request as the default merge message for all squashed commits. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)". +{% endif %} + ### Squashing and merging a long-running branch If you plan to continue work on the [head branch](/github/getting-started-with-github/github-glossary#head-branch) of a pull request after the pull request is merged, we recommend you don't squash and merge the pull request. diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md index a260cbbe84..4f8797dc68 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md @@ -1,6 +1,6 @@ --- title: Changing the stage of a pull request -intro: 'You can mark a draft pull request as ready for review{% ifversion fpt or ghae or ghes or ghec %} or convert a pull request to a draft{% endif %}.' +intro: You can mark a draft pull request as ready for review or convert a pull request to a draft. permissions: People with write permissions to a repository and pull request authors can change the stage of a pull request. product: '{% data reusables.gated-features.draft-prs %}' redirect_from: @@ -21,21 +21,17 @@ shortTitle: Change the state {% data reusables.pull_requests.mark-ready-review %} -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Tip**: You can also mark a pull request as ready for review using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)" in the {% data variables.product.prodname_cli %} documentation. {% endtip %} -{% endif %} {% data reusables.repositories.sidebar-pr %} 2. In the "Pull requests" list, click the pull request you'd like to mark as ready for review. 3. In the merge box, click **Ready for review**. ![Ready for review button](/assets/images/help/pull_requests/ready-for-review-button.png) -{% ifversion fpt or ghae or ghes or ghec %} - ## Converting a pull request to a draft You can convert a pull request to a draft at any time. For example, if you accidentally opened a pull request instead of a draft, or if you've received feedback on your pull request that needs to be addressed, you can convert the pull request to a draft to indicate further changes are needed. No one can merge the pull request until you mark the pull request as ready for review again. People who are already subscribed to notifications for the pull request will not be unsubscribed when you convert the pull request to a draft. @@ -47,8 +43,6 @@ You can convert a pull request to a draft at any time. For example, if you accid 4. Click **Convert to draft**. ![Convert to draft confirmation](/assets/images/help/pull_requests/convert-to-draft-dialog.png) -{% endif %} - ## Further reading - "[About pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)" diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md index 4ce18de40c..19b6706e34 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md @@ -21,7 +21,7 @@ Repositories belong to a personal account (a single individual owner) or an orga To assign a reviewer to a pull request, you will need write access to the repository. For more information about repository access, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." If you have write access, you can assign anyone who has read access to the repository as a reviewer. -Organization members with write access can also assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. {% ifversion fpt or ghae or ghes or ghec %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} +Organization members with write access can also assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." {% note %} diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md index 72a631d3b9..37fff36380 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md @@ -21,7 +21,7 @@ After a pull request is opened, anyone with *read* access can review and comment {% if pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %} -Repository owners and collaborators can request a pull request review from a specific person. Organization members can also request a pull request review from a team with read access to the repository. For more information, see "[Requesting a pull request review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." {% ifversion fpt or ghae or ghes or ghec %}You can specify a subset of team members to be automatically assigned in the place of the whole team. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} +Repository owners and collaborators can request a pull request review from a specific person. Organization members can also request a pull request review from a team with read access to the repository. For more information, see "[Requesting a pull request review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)." You can specify a subset of team members to be automatically assigned in the place of the whole team. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." Reviews allow for discussion of proposed changes and help ensure that the changes meet the repository's contributing guidelines and other quality standards. You can define which individuals or teams own certain types or areas of code in a CODEOWNERS file. When a pull request modifies code that has a defined owner, that individual or team will automatically be requested as a reviewer. For more information, see "[About code owners](/articles/about-code-owners/)." diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 36ff4cc7d1..baea88ca85 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -5,7 +5,7 @@ product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md index 59d1f77e29..7d5654b4d3 100644 --- a/translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md +++ b/translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md @@ -30,10 +30,10 @@ Here's an example of a [comparison between two branches](https://github.com/octo ## Comparing tags -Comparing release tags will show you changes to your repository since the last release. {% ifversion fpt or ghae or ghes or ghec %} -For more information, see "[Comparing releases](/github/administering-a-repository/comparing-releases)."{% endif %} +Comparing release tags will show you changes to your repository since the last release. +For more information, see "[Comparing releases](/github/administering-a-repository/comparing-releases)." -{% ifversion fpt or ghae or ghes or ghec %}To compare tags, you can select a tag name from the `compare` drop-down menu at the top of the page.{% else %} Instead of typing a branch name, type the name of your tag in the `compare` drop down menu.{% endif %} +To compare tags, you can select a tag name from the `compare` drop-down menu at the top of the page. Here's an example of a [comparison between two tags](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3). diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md index 2ee7ad779e..0ec0f78905 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md @@ -27,8 +27,7 @@ shortTitle: Acerca de los métodos de fusión {% data reusables.pull_requests.default_merge_option %} -{% ifversion fpt or ghae or ghes or ghec %} -El método de fusión predeterminado crea una confirmación de fusión. Puedes impedir que cualquiera suba confirmaciones de fusión en una rama protegida imponiendo un historiar de confirmaciones linear. Para obtener más información, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-linear-history)".{% endif %} +El método de fusión predeterminado crea una confirmación de fusión. Puedes impedir que cualquiera suba confirmaciones de fusión en una rama protegida imponiendo un historiar de confirmaciones linear. Para obtener más información, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-linear-history)". ## Combinar tus confirmaciones de fusión diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md index 249403b393..a3554ebd90 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md @@ -68,11 +68,11 @@ When you create a branch rule, the branch you specify doesn't have to exist yet - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)." ![Require review from code owners](/assets/images/help/repository/PR-review-required-code-owner.png) {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5611 %} - - Optionally, to allow specific people or teams to push code to the branch without creating pull requests when they're required, select **Allow specific actors to bypass required pull requests**. Then, search for and select the people or teams who should be allowed to skip creating a pull request. - ![Allow specific actors to bypass pull request requirements checkbox](/assets/images/help/repository/PR-bypass-requirements.png) + - Optionally, to allow specific actors to push code to the branch without creating pull requests when they're required, select **Allow specified actors to bypass required pull requests**. Then, search for and select the actors who should be allowed to skip creating a pull request. + ![Allow specific actors to bypass pull request requirements checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-bypass-requirements-with-apps.png){% else %}(/assets/images/help/repository/PR-bypass-requirements.png){% endif %} {% endif %} - - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the people or teams who are allowed to dismiss pull request reviews. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." - ![Restrict who can dismiss pull request reviews checkbox](/assets/images/help/repository/PR-review-required-dismissals.png) + - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the actors who are allowed to dismiss pull request reviews. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)." + ![Restrict who can dismiss pull request reviews checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-review-required-dismissals-with-apps.png){% else %}(/assets/images/help/repository/PR-review-required-dismissals.png){% endif %} 1. Optionally, enable required status checks. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." - Select **Require status checks to pass before merging**. ![Required status checks option](/assets/images/help/repository/required-status-checks.png) @@ -115,8 +115,8 @@ When you create a branch rule, the branch you specify doesn't have to exist yet {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5624 %} Then, choose who can force push to the branch. - Select **Everyone** to allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions. - - Select **Specify who can force push** to allow only specific people or teams to force push to the branch. Then, search for and select those people or teams. - ![Screenshot of the options to specify who can force push](/assets/images/help/repository/allow-force-pushes-specify-who.png) + - Select **Specify who can force push** to allow only specific actors to force push to the branch. Then, search for and select those actors. + ![Screenshot of the options to specify who can force push]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png){% else %}(/assets/images/help/repository/allow-force-pushes-specify-who.png){% endif %} {% endif %} For more information about force pushes, see "[Allow force pushes](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)." diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md index 15b8b7fdd6..810cf322fa 100644 --- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md +++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md @@ -37,14 +37,11 @@ remote: error: Required status check "ci-build" is failing {% endnote %} -{% ifversion fpt or ghae or ghes or ghec %} - ## Conflictos entre confirmaciones de encabezado y confirmaciones de fusiones de prueba Algunas veces, los resultados de las verificaciones de estado para la confirmación de la prueba de fusión y de la confirmación principal entrarán en conflicto. Si la confirmación de fusión de prueba tiene un estado, ésta pasará. De otra manera, el estado de la confirmación principal deberá pasar antes de que puedas fusionar la rama. Para obtener más información sobre las confirmaciones de fusiones de prueba, consulta la sección "[Extracciones](/rest/reference/pulls#get-a-pull-request)". ![Ramas con conflictos en las confirmaciones de fusión](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) -{% endif %} ## Se salta el manejo pero se requieren las verificaciones diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md index ee9caffb14..d805626f9b 100644 --- a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md +++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md @@ -26,17 +26,15 @@ topics: {% endtip %} -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Tip**: También puedes crear un repositorio utilizando el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" en la documentación de {% data variables.product.prodname_cli %}. {% endtip %} -{% endif %} {% data reusables.repositories.create_new %} -2. Otra opción para crear un repositorio con la estructura del directorio y los archivos de un repositorio existente es usar el menú desplegable **Elegir una plantilla** y seleccionar un repositorio de plantillas. Verás repositorios de plantillas que te pertenecen a ti y a las organizaciones de las que eres miembro o bien repositorios de plantillas que has usado anteriormente. Para obtener más información, consulta "[Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)". ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %} -3. De manera opcional, si decides utilizar una plantilla, para incluir la estructura del directorio y los archivos de todas las ramas en la misma y no solo la rama predeterminada, selecciona **Incluir todas las ramas**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} +2. Otra opción para crear un repositorio con la estructura del directorio y los archivos de un repositorio existente es usar el menú desplegable **Elegir una plantilla** y seleccionar un repositorio de plantillas. Verás repositorios de plantillas que te pertenecen a ti y a las organizaciones de las que eres miembro o bien repositorios de plantillas que has usado anteriormente. Para obtener más información, consulta "[Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)". ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png) +3. De manera opcional, si decides utilizar una plantilla, para incluir la estructura del directorio y los archivos de todas las ramas en la misma y no solo la rama predeterminada, selecciona **Incluir todas las ramas**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png) 3. En el menú desplegable de Propietario, selecciona la cuenta en la cual quieres crear el repositorio. ![Menú desplegable Propietario](/assets/images/help/repository/create-repository-owner.png) {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %} diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md index 280aa369a1..9bdef7e4d6 100644 --- a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md +++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md @@ -18,17 +18,13 @@ shortTitle: Create from a template Anyone with read permissions to a template repository can create a repository from that template. For more information, see "[Creating a template repository](/articles/creating-a-template-repository)." -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Tip**: You can also create a repository from a template using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation. {% endtip %} -{% endif %} -{% ifversion fpt or ghae or ghes or ghec %} You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches. -{% endif %} Creating a repository from a template is similar to forking a repository, but there are important differences: - A new fork includes the entire commit history of the parent repository, while a repository created from a template starts with a single commit. @@ -44,8 +40,8 @@ For more information about forks, see "[About forks](/pull-requests/collaboratin ![Use this template button](/assets/images/help/repository/use-this-template-button.png) {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} -{% data reusables.repositories.choose-repo-visibility %}{% ifversion fpt or ghae or ghes or ghec %} +{% data reusables.repositories.choose-repo-visibility %} 6. Optionally, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**. - ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} + ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png) {% data reusables.repositories.select-marketplace-apps %} 8. Click **Create repository from template**. diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md index d10088033d..3a034388e6 100644 --- a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md +++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md @@ -1,6 +1,6 @@ --- title: Crear un repositorio desde una plantilla -intro: 'Puedes crear una plantilla a partir de un repositorio existente para que tanto tú como otras personas puedan generar nuevos repositorios con la misma estructura de {% ifversion fpt or ghae or ghes or ghec %}ramas y{% endif %}archivos en el directorio.' +intro: 'You can make an existing repository a template, so you and others can generate new repositories with the same directory structure, branches, and files.' permissions: Anyone with admin permissions to a repository can make the repository a template. redirect_from: - /articles/creating-a-template-repository @@ -24,7 +24,7 @@ shortTitle: Crear un repositorio de plantilla Para crear un repositorio de plantilla, debes crear un repositorio y luego convertirlo en una plantilla. Para obtener más información sobre la creación de repositorios, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)." -Después de que conviertes tu repositorio en una plantilla, cualquiera que tenga acceso a este podrá generar un repositorio nuevo con la misma estructura de directorios y archivos que tu rama predeterminada.{% ifversion fpt or ghae or ghes or ghec %} También pueden elegir incluir el resto de las ramas de tu repositorio. Las ramas que se crean a partir de una plantilla tienen historiales sin relación, así que no puedes crear solicitudes de cambios ni hacer fusiones entre ramas.{% endif %} Para obtener más información, consulta la sección "[Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)". +After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch. They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches. Para obtener más información, consulta "[Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)". {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md index 2603ed7d9a..e75348759f 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md @@ -31,7 +31,7 @@ Cada notificación por correo electrónico para una subida a un repositorio enum - Los archivos que fueron modificados como parte de la confirmación. - El mensaje de confirmación -Puedes filtrar las notificaciones por correo electrónico que recibes para las inserciones en un repositorio. Para obtener más información, consulta la sección {% ifversion fpt or ghae or ghes or ghec %}"[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[Acerca de los mensajes de notificación por correo electrónico](/github/receiving-notifications-about-activity-on-github/about-email-notifications)". También puedes apagar las notificaciones por correo electrónico para las cargas de información. Para obtener más información, consulta la sección "[Escoger el método de entrega para las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}". +Puedes filtrar las notificaciones por correo electrónico que recibes para las inserciones en un repositorio. Para obtener más información, consulta la sección "[Configurar notificaciones](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)". ## Habilitar las notificaciones por correo electrónico para las subidas de información en tu repositorio @@ -43,10 +43,5 @@ Puedes filtrar las notificaciones por correo electrónico que recibes para las i 7. Da clic en **Configurar notificaciones**. ![Botón de configurar notificaciones](/assets/images/help/settings/setup_notifications_settings.png) ## Leer más -{% ifversion fpt or ghae or ghes or ghec %} - "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" -{% else %} -- "[Acerca de las notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" -- "[Escoger el método de entrega para tus notificaciones](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)" -- "[Acerca de las notificaciones por correo electrónico](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" -- "[Acerca de las notificaciones web](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)"{% endif %} + diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/about-releases.md b/translations/es-ES/content/repositories/releasing-projects-on-github/about-releases.md index 29261145b4..9c9f2fd285 100644 --- a/translations/es-ES/content/repositories/releasing-projects-on-github/about-releases.md +++ b/translations/es-ES/content/repositories/releasing-projects-on-github/about-releases.md @@ -31,7 +31,7 @@ Releases are deployable software iterations you can package and make available f Releases are based on [Git tags](https://git-scm.com/book/en/Git-Basics-Tagging), which mark a specific point in your repository's history. A tag date may be different than a release date since they can be created at different times. For more information about viewing your existing tags, see "[Viewing your repository's releases and tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)." -You can receive notifications when new releases are published in a repository without receiving notifications about other updates to the repository. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching releases for a repository](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}." +You can receive notifications when new releases are published in a repository without receiving notifications about other updates to the repository. For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)." Anyone with read access to a repository can view and compare releases, but only people with write permissions to a repository can manage releases. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)." @@ -39,6 +39,10 @@ Anyone with read access to a repository can view and compare releases, but only You can manually create release notes while managing a release. Alternatively, you can automatically generate release notes from a default template, or customize your own release notes template. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)." {% endif %} +{% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7054 %} +When viewing the details for a release, the creation date for each release asset is shown next to the release asset. +{% endif %} + {% ifversion fpt or ghec %} People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository)." @@ -47,7 +51,7 @@ If a release fixes a security vulnerability, you should publish a security advis You can view the **Dependents** tab of the dependency graph to see which repositories and packages depend on code in your repository, and may therefore be affected by a new release. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." {% endif %} -You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/rest/reference/repos#releases)." +You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/rest/reference/releases)." {% ifversion fpt or ghec %} ## Storage and bandwidth quotas diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/translations/es-ES/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md index 56ff4c328b..ca3bd97746 100644 --- a/translations/es-ES/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md +++ b/translations/es-ES/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md @@ -17,13 +17,11 @@ topics: shortTitle: Visualizar lanzamientos & etiquetas --- -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Tip**: También puedes ver un lanzamientos utilizando el {% data variables.product.prodname_cli %}. Para obtener más información, consulta la sección "[`gh release view`](https://cli.github.com/manual/gh_release_view)" en la documentación de {% data variables.product.prodname_cli %}. {% endtip %} -{% endif %} ## Visualizar lanzamientos diff --git a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md index 3e35c0e7b2..432d4a4a6c 100644 --- a/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md +++ b/translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md @@ -64,7 +64,7 @@ Las bifurcaciones se detallan alfabéticamente por el nombre de usuario de la pe {% data reusables.repositories.accessing-repository-graphs %} 3. En la barra lateral izquierda, haz clic en **Forks** (Bifurcaciones). ![Pestaña Forks (Bifurcaciones)](/assets/images/help/graphs/graphs-sidebar-forks-tab.png) -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Visualizar las dependencias de un repositorio Puedes utilizar la gráfica de dependencias para explorar el código del cual depende tu repositorio. diff --git a/translations/es-ES/content/rest/enterprise-admin/audit-log.md b/translations/es-ES/content/rest/enterprise-admin/audit-log.md index f6850d0031..2891f8a3f1 100644 --- a/translations/es-ES/content/rest/enterprise-admin/audit-log.md +++ b/translations/es-ES/content/rest/enterprise-admin/audit-log.md @@ -5,6 +5,7 @@ versions: fpt: '*' ghes: '>=3.3' ghec: '*' + ghae: '*' topics: - API miniTocMaxHeadingLevel: 3 diff --git a/translations/es-ES/content/rest/guides/getting-started-with-the-checks-api.md b/translations/es-ES/content/rest/guides/getting-started-with-the-checks-api.md index 5464c09b85..e4789e8ca5 100644 --- a/translations/es-ES/content/rest/guides/getting-started-with-the-checks-api.md +++ b/translations/es-ES/content/rest/guides/getting-started-with-the-checks-api.md @@ -41,10 +41,7 @@ Una ejecución de verificación es una prueba individual que forma parte de una ![Flujo de trabajo de las ejecuciones de verificación](/assets/images/check_runs.png) -{% ifversion fpt or ghes or ghae or ghec %} -Si una ejecución de verificación permanece en un estado incompleto por más de 14 días, entonces las `conclusion` de dicha ejecución se convierten en `stale` y aparecen en -{% data variables.product.prodname_dotcom %} como quedadas con el {% octicon "issue-reopened" aria-label="The issue-reopened icon" %}. Solo {% data variables.product.prodname_dotcom %} puede marcar las ejecuciones de verificación como `stale`. Para obtener más información acerca de las conclusiones posibles para una ejecución de verificación, consulta el [parámetro de `conclusion`](/rest/reference/checks#create-a-check-run--parameters). -{% endif %} +Si una ejecución de verificación permanece en un estado incompleto por más de 14 días, entonces la `conclusion` de ésta se convierte en `stale` y aparece en {% data variables.product.prodname_dotcom %} como quedada con el {% octicon "issue-reopened" aria-label="The issue-reopened icon" %}. Solo {% data variables.product.prodname_dotcom %} puede marcar las ejecuciones de verificación como `stale`. Para obtener más información acerca de las conclusiones posibles para una ejecución de verificación, consulta el [parámetro de `conclusion`](/rest/reference/checks#create-a-check-run--parameters). Puedes crear la ejecución de verificación tan pronto como recibas el webhook de [`check_suite`](/webhooks/event-payloads/#check_suite), aún si ésta todavía no se completa. Puedes actualizar el `status` de la ejecución de verificación ya que se completa con los valores `queued`, `in_progress`, o `completed`, y puedes actualizar la `output` conforme vayan estando disponibles los detalles adicionales. Una ejecución de verificación puede contener estampas de tiempo, un enlace para encontrar más detalles en tu sitio externo, anotaciones detalladas para líneas de código específcas, e información acerca del análisis que se llevó a cabo. diff --git a/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md b/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md index 778057de81..59561271f1 100644 --- a/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/es-ES/content/rest/guides/getting-started-with-the-rest-api.md @@ -134,7 +134,7 @@ Cuando te autentiques, debes ver como tu límite de tasa sube hasta 5,000 solici Puedes [crear un**token de acceso personal**][personal token] fácilmente utilizando tu [página de configuración para tokens de acceso personal][tokens settings]: -{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} {% warning %} Para mantener tu información segura, te recomendamos ampliamente que configures un vencimiento para tus tokens de acceso personal. @@ -150,7 +150,7 @@ Para mantener tu información segura, te recomendamos ampliamente que configures ![Selección de token personal](/assets/images/help/personal_token_ghae.png) {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} Las solicitudes de la API que utilicen un token de acceso personal con vencimiento devolverán la fecha de vencimiento de dicho token a través del encabezado de `GitHub-Authentication-Token-Expiration`. Puedes utilizar el encabezado en tus scripts para proporcionar un mensaje de advertencia cuando el token esté próximo a vencer. {% endif %} diff --git a/translations/es-ES/content/rest/overview/libraries.md b/translations/es-ES/content/rest/overview/libraries.md index 8665fd2dbd..b147834fbc 100644 --- a/translations/es-ES/content/rest/overview/libraries.md +++ b/translations/es-ES/content/rest/overview/libraries.md @@ -141,9 +141,10 @@ Advertencia: Desde la segunda mitad de octubre del 2021, ya no se están manteni ### Rust -| Nombre de la librería | Repositorio | -| --------------------- | ------------------------------------------------------------- | -| **Octocrab** | [XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) | +| Nombre de la librería | Repositorio | +| --------------------- | ----------------------------------------------------------------- | +| **Octocrab** | [XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) | +| **Octocat** | [octocat-rs/octocat-rs](https://github.com/octocat-rs/octocat-rs) | ### Scala diff --git a/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md b/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md index 518a425516..5e3852220c 100644 --- a/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/es-ES/content/rest/overview/resources-in-the-rest-api.md @@ -120,7 +120,7 @@ No podrás autenticarte utilizndo tu llave y secreto de OAuth2 si estás en modo {% ifversion fpt or ghec %} -Lee [más acerca de limitar la tasa de no autenticación](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). +Lee [más acerca de limitar la tasa de no autenticación](#increasing-the-unauthenticated-rate-limit-for-oauth-apps). {% endif %} diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md index 0ae620c405..f9424b478d 100644 --- a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md +++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md @@ -87,7 +87,6 @@ Si tu consulta de búsqueda contiene espacios en blanco, tendrás que encerrarla Algunos símbolos que no son alfanuméricos, como los espacios, se quitan de las consultas de búsqueda de código que van entre comillas; por lo tanto, los resultados pueden ser imprevistos. -{% ifversion fpt or ghes or ghae or ghec %} ## Consultas con nombres de usuario Si tu consulta de búsqueda contiene un calificador que requiere un nombre de usuario, tal como `user`, `actor`, o `assignee`, puedes utilizar cualquier nombre de usuario de {% data variables.product.product_name %} para especificar una persona en concreto, o utilizar `@me`, para especificar el usuario actual. @@ -98,4 +97,3 @@ Si tu consulta de búsqueda contiene un calificador que requiere un nombre de us | `QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) coincidirá con los informes de problemas asignados a la persona que está viendo los resultados | Solo puedes utilizar `@me` con un calificador y no como un término de búsqueda, tal como `@me main.workflow`. -{% endif %} diff --git a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md index dd17c6fc17..0ab2490764 100644 --- a/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -54,15 +54,12 @@ To search issues and pull requests in all repositories owned by a certain user o {% data reusables.pull_requests.large-search-workaround %} - | Qualifier | Example | ------------- | ------------- | user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) matches issues with the word "ubuntu" from repositories owned by @defunkt. | org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) matches issues in repositories owned by the GitHub organization. | repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) matches issues from @mozilla's shumway project that were created before March 2012. - - ## Search by open or closed state You can filter issues and pull requests based on whether they're open or closed using the `state` or `is` qualifier. @@ -136,7 +133,6 @@ You can use the `involves` qualifier to find issues that in some way involve a c | involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** matches issues either @defunkt or @jlord are involved in. | | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) matches issues @mdo is involved in that do not contain the word "bootstrap" in the body. -{% ifversion fpt or ghes or ghae or ghec %} ## Search for linked issues and pull requests You can narrow your results to only include issues that are linked to a pull request by a closing reference, or pull requests that are linked to an issue that the pull request may close. @@ -145,7 +141,7 @@ You can narrow your results to only include issues that are linked to a pull req | `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) matches open issues in the `desktop/desktop` repository that are linked to a pull request by a closing reference. | | `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) matches closed pull requests in the `desktop/desktop` repository that were linked to an issue that the pull request may have closed. | | `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) matches open issues in the `desktop/desktop` repository that are not linked to a pull request by a closing reference. | -| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) matches open pull requests in the `desktop/desktop` repository that are not linked to an issue that the pull request may close. |{% endif %} +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) matches open pull requests in the `desktop/desktop` repository that are not linked to an issue that the pull request may close. | ## Search by label @@ -243,10 +239,9 @@ You can filter issues and pull requests by the number of reactions using the `re You can filter for draft pull requests. For more information, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)." | Qualifier | Example -| ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %} +| ------------- | ------------- | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) matches draft pull requests. -| `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) matches pull requests that are ready for review.{% else %} -| `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) matches draft pull requests.{% endif %} +| `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) matches pull requests that are ready for review. ## Search by pull request review status and reviewer diff --git a/translations/es-ES/content/site-policy/github-terms/github-community-guidelines.md b/translations/es-ES/content/site-policy/github-terms/github-community-guidelines.md index 763c72f859..e9ed9ed0f2 100644 --- a/translations/es-ES/content/site-policy/github-terms/github-community-guidelines.md +++ b/translations/es-ES/content/site-policy/github-terms/github-community-guidelines.md @@ -39,7 +39,7 @@ While some disagreements can be resolved with direct, respectful communication b * **Comunicar las expectativas** - Los mantenedores pueden configurar lineamientos específicos para las comunidades para ayudar a los usuarios a entender cómo interactuar con sus proyectos, por ejemplo, en el README de un repositorio, el [archivo de CONTRIBUTING](/articles/setting-guidelines-for-repository-contributors/) o en un [código de conducta dedicado](/articles/adding-a-code-of-conduct-to-your-project/). You can find additional information on building communities [here](/communities). -* **Moderar los comentarios** - Los usuarios con [privilegios de acceso de escritura](/articles/repository-permission-levels-for-an-organization/) en un repositorio pueden [editar, borrar u ocultar los comentarios de quien sea](/communities/moderating-comments-and-conversations/managing-disruptive-comments) en las confirmaciones, solicitudes de cambio y propuestas. Cualquier persona con acceso de lectura a un repositorio puede ver el historial de edición del comentario. Comment authors and people with write access to a repository can also delete sensitive information from a [comment's edit history](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment). El moderar tus proyectos puede sentirse como una tarea grande si hay mucha actividad, pero puedes [agregar colaboradores](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) para que te ayuden a administrar tu comunidad. +* **Moderar los comentarios** - Los usuarios con [privilegios de acceso de escritura](/articles/repository-permission-levels-for-an-organization/) en un repositorio pueden [editar, borrar u ocultar los comentarios de quien sea](/communities/moderating-comments-and-conversations/managing-disruptive-comments) en las confirmaciones, solicitudes de cambio y propuestas. Cualquier persona con acceso de lectura a un repositorio puede ver el historial de edición del comentario. Comment authors and people with write access to a repository can also delete sensitive information from a [comment's edit history](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment). El moderar tus proyectos puede sentirse como una tarea grande si hay mucha actividad, pero puedes [agregar colaboradores](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) para que te ayuden a administrar tu comunidad. * **Bloquear conversaciones** - Si un debate en una propuesta, solicitud de cambios o confirmación se sale de control o de tema o viola el código de conducta de tu proyecto o las políticas de GitHub, los colaboradores y el resto de las personas con acceso de descritura pueden [bloquearlo](/articles/locking-conversations/) temporal o permanentemente en la conversación. diff --git a/translations/es-ES/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md b/translations/es-ES/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md index 5285c7bb6e..750e9be1d0 100644 --- a/translations/es-ES/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md +++ b/translations/es-ES/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md @@ -16,8 +16,8 @@ El uso de los GitHub Codespaces está sujeto a la [Declaración de Privacidad de La actividad en github.dev está sujeta a los [Términos de las Vistas Previas Beta de GitHub](/github/site-policy/github-terms-of-service#j-beta-previews) -## Utilizar Visual Studio Code +## Uso de {% data variables.product.prodname_vscode %} -GitHub Codespaces y github.dev permiten el uso de Visual Studio Code en el buscador web. Cuando utilizas Visual Studio Code en el navegador web, se habilita algo de recopilación de telemetría predeterminadamente y se [explica a detalle en el sitio web de Visual Studio Code](https://code.visualstudio.com/docs/getstarted/telemetry). Los usuarios pueden decidir no participar en la telemetría siguiendo la ruta Archivo > Preferencias > Ajustes, debajo del menú superior izquierdo. +GitHub Codespaces and github.dev allow for use of {% data variables.product.prodname_vscode %} in the web browser. When using {% data variables.product.prodname_vscode_shortname %} in the web browser, some telemetry collection is enabled by default and is [explained in detail on the {% data variables.product.prodname_vscode_shortname %} website](https://code.visualstudio.com/docs/getstarted/telemetry). Los usuarios pueden decidir no participar en la telemetría siguiendo la ruta Archivo > Preferencias > Ajustes, debajo del menú superior izquierdo. -Si un usuario elige no participar en la captura de telemetría en Visual Studio Code mientras está en un codespace de acuerdo con lo estipulado, esto sincronizará la preferencia de inhabilitar la telemetría en todas las sesiones web futuras dentro de GitHub Codespaces y github.dev. +If a user chooses to opt out of telemetry capture in {% data variables.product.prodname_vscode_shortname %} while inside of a codespace as outlined, this will sync the disable telemetry preference across all future web sessions in GitHub Codespaces and github.dev. diff --git a/translations/es-ES/content/site-policy/privacy-policies/github-privacy-statement.md b/translations/es-ES/content/site-policy/privacy-policies/github-privacy-statement.md index 9f4bd24aa8..82e023e01d 100644 --- a/translations/es-ES/content/site-policy/privacy-policies/github-privacy-statement.md +++ b/translations/es-ES/content/site-policy/privacy-policies/github-privacy-statement.md @@ -65,7 +65,7 @@ Necesitamos cierta información básica al momento de creación de la cuenta. Cu #### Información de Pago Si te registras para una Cuenta paga, envías fondos a través del Programa de patrocinadores de GitHub o compras una aplicación en el Mercado GitHub, recopilamos tu nombre completo y la información de la tarjeta de crédito o la información de PayPal. Ten en cuenta que GitHub no procesa ni almacena tu información de tarjeta de crédito o información de PayPal, pero sí lo hace nuestro procesador de pago subcontratado. -Si detallas y vendes una aplicación en el [Mercado GitHub](https://github.com/marketplace), te solicitamos la información de tu banco. Si recabas fondos a través del [Programa de Patrocinadores de GitHub](https://github.com/sponsors), necesitamos algo de [información adicional](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-bank-information) mediante el proceso de registro para que participes y recibas los fondos a través de estos servicios y para propósitos de cumplimiento. +Si detallas y vendes una aplicación en el [Mercado GitHub](https://github.com/marketplace), te solicitamos la información de tu banco. If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes. #### Información de perfil Puedes decidir proporcionarnos más información para tu Perfil de cuenta, como tu nombre completo, un avatar que puede incluir una fotografía, tu biografía, tu ubicación, tu empresa y una URL a un sitio web de terceros. Esta información puede incluir Información personal del usuario. Ten en cuenta que tu información de perfil puede ser visible para otros Usuarios de nuestro Servicio. diff --git a/translations/es-ES/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/translations/es-ES/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md index a404521a79..424952d129 100644 --- a/translations/es-ES/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md +++ b/translations/es-ES/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md @@ -19,7 +19,7 @@ topics: {% data reusables.sponsors.no-fees %} Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)". -{% data reusables.sponsors.you-can-be-a-sponsored-developer %} Para obtener más información, consulta las secciones "[Acerca de {% data variables.product.prodname_sponsors %} para los contribuyentes de código libre](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" y "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)". +{% data reusables.sponsors.you-can-be-a-sponsored-developer %} Para obtener más información, consulta las secciones "[Acerca de {% data variables.product.prodname_sponsors %} para los contribuyentes de código abierto](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" y "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)". {% data reusables.sponsors.you-can-be-a-sponsored-organization %}Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)". diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md index 29a7742ca7..2149f942e2 100644 --- a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md +++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md @@ -16,7 +16,7 @@ shortTitle: Contribuyentes de código abierto ## Unirte a {% data variables.product.prodname_sponsors %} -{% data reusables.sponsors.you-can-be-a-sponsored-developer %}Para obtener más información, consulta [Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)". +{% data reusables.sponsors.you-can-be-a-sponsored-developer %}Para obtener más información, consulta [Configurar {% data variables.product.prodname_sponsors %} para tu cuenta de personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)". {% data reusables.sponsors.you-can-be-a-sponsored-organization %}Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)". @@ -28,7 +28,7 @@ Puedes configurar una meta para tus patrocinios. Para obtener más información, ## Niveles de patrocinio -{% data reusables.sponsors.tier-details %} Para obtener más información, consulta las secciones "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal"](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)", "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization) y "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)". +{% data reusables.sponsors.tier-details %} Para obtener más información, consulta las secciones "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)", "[Configurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)" y "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)". Es mejor mantener una gama de opciones de patrocinio diferentes, incluyendo niveles mensuales y de una sola ocasión, para hacer más fácil que cualquiera apiye tu trabajo. Particularmente, los pagos de una sola ocasión le permiten a la spersonas recompensarte por tu esfuerzo sin preocuparse de que sus finanzas apoyen un programa de pagos constantes. diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md index 06f351dfb1..303f2808bc 100644 --- a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md +++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md @@ -11,7 +11,7 @@ versions: ghec: '*' children: - /about-github-sponsors-for-open-source-contributors - - /setting-up-github-sponsors-for-your-user-account + - /setting-up-github-sponsors-for-your-personal-account - /setting-up-github-sponsors-for-your-organization - /editing-your-profile-details-for-github-sponsors - /managing-your-sponsorship-goal diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md index e930acde6f..e300d389a9 100644 --- a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -23,7 +23,7 @@ shortTitle: Configuración para una organización Después de recibir una invitación para que tu organización se una a {% data variables.product.prodname_sponsors %} puedes completar los pasos a continuación para que se convierta en una organización patrocinada. -Para unirte a {% data variables.product.prodname_sponsors %} como un colaborador individual independiente a una organización, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)". +Para unirte a {% data variables.product.prodname_sponsors %} como un colaborador individual independiente a una organización, consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)". {% data reusables.sponsors.navigate-to-github-sponsors %} {% data reusables.sponsors.view-eligible-accounts %} diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md similarity index 96% rename from translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md rename to translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md index b9d924b9f9..e664d27b9b 100644 --- a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md @@ -1,10 +1,11 @@ --- -title: Configurar a los Patrocinadores de GitHub para tu cuenta de usuario +title: Setting up GitHub Sponsors for your personal account intro: 'Puedes convertirte en un desarrollador patrocinado si te unes a {% data variables.product.prodname_sponsors %}, completas tu perfil de desarrollador patrocinado, creas niveles de patrocinio, emites tu información fiscal y bancaria y habilitas la autenticación bifactorial para tu cuenta en {% data variables.product.product_location %}.' redirect_from: - /articles/becoming-a-sponsored-developer - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account + - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account versions: fpt: '*' ghec: '*' diff --git a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md index 4cd423d20c..6b4dacd7f4 100644 --- a/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md +++ b/translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md @@ -28,7 +28,7 @@ Si eres un contribuyente en los Estados Unidos, debes emitir un formato ["W-9](h Los formatos de impuestos W-8 BEN y W-8 BEN-E ayudan a que {% data variables.product.prodname_dotcom %} determine al propietario beneficiario de una cantidad sujeta a retenciones. -Si eres un contribuyente en cualquier otra región diferente a los Estados Unidos, debes emitir un formato [W-8 BEN](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf) (individual) o [W-8 BEN-E](https://www.irs.gov/forms-pubs/about-form-w-8-ben-e) (para empresas) antes de publicar tu perfil de {% data variables.product.prodname_sponsors %}. Para obtener más información, consulta las secciones "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-tax-information)" y "[Confgurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)". {% data variables.product.prodname_dotcom %}te enviará los formatos adecuados, te notificará cuando vayan a expirar, y te dará una cantidad razonable de tiempo para completarlos y enviarlos. +Si eres un contribuyente en cualquier otra región diferente a los Estados Unidos, debes emitir un formato [W-8 BEN](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf) (individual) o [W-8 BEN-E](https://www.irs.gov/forms-pubs/about-form-w-8-ben-e) (para empresas) antes de publicar tu perfil de {% data variables.product.prodname_sponsors %}. Para obtener más información, consulta las secciones "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-tax-information)" y "[Configurar {% data variables.product.prodname_sponsors %} para tu organizaciòn](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)". {% data variables.product.prodname_dotcom %}te enviará los formatos adecuados, te notificará cuando vayan a expirar, y te dará una cantidad razonable de tiempo para completarlos y enviarlos. Si se te asignó un formato de impuestos incorrecto, [contacta al Soporte de {% data variables.product.prodname_dotcom %}](https://support.github.com/contact?form%5Bsubject%5D=GitHub%20Sponsors:%20tax%20form&tags=sponsors) para que se te reasigne el formato correcto para tu situación. diff --git a/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md index eec905910a..15580fe9d5 100644 --- a/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md +++ b/translations/es-ES/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md @@ -43,7 +43,7 @@ Puedes elegir si quieres mostrar tu patrocinio públicamente. Los patrocinios de Si la cuenta patrocinada retira tu nivel, éste permanecerá configurado hasta que elijas uno diferente o hasta que canceles tu suscripción. Para obtener más información, consulta "[Actualizar un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)." -Si la cuenta que quieres patrocinar no tiene un perfil en {% data variables.product.prodname_sponsors %}, puedes alentarla a que se una. Para obtener más información, consulta las secciones "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)" y "[Confgurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)". +Si la cuenta que quieres patrocinar no tiene un perfil en {% data variables.product.prodname_sponsors %}, puedes alentarla a que se una. Para obtener más información, consulta las secciones "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)" y "[Confgurar {% data variables.product.prodname_sponsors %} para tu organización](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)". {% data reusables.sponsors.sponsorships-not-tax-deductible %} diff --git a/translations/es-ES/data/features/integration-branch-protection-exceptions.yml b/translations/es-ES/data/features/integration-branch-protection-exceptions.yml new file mode 100644 index 0000000000..3c6a729fb9 --- /dev/null +++ b/translations/es-ES/data/features/integration-branch-protection-exceptions.yml @@ -0,0 +1,8 @@ +--- +#Reference: #6665 +#GitHub Apps are supported as actors in all types of exceptions to branch protections +versions: + fpt: '*' + ghec: '*' + ghes: '>= 3.6' + ghae: 'issue-6665' diff --git a/translations/es-ES/data/features/math.yml b/translations/es-ES/data/features/math.yml new file mode 100644 index 0000000000..b7b89eb201 --- /dev/null +++ b/translations/es-ES/data/features/math.yml @@ -0,0 +1,8 @@ +--- +#Issues 6054 +#Math support using LaTeX syntax +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.6' + ghae: 'issue-6054' diff --git a/translations/es-ES/data/features/security-managers.yml b/translations/es-ES/data/features/security-managers.yml index 6e62d12897..77f12eb126 100644 --- a/translations/es-ES/data/features/security-managers.yml +++ b/translations/es-ES/data/features/security-managers.yml @@ -4,5 +4,5 @@ versions: fpt: '*' ghes: '>=3.3' - ghae: 'issue-4999' + ghae: '*' ghec: '*' diff --git a/translations/es-ES/data/features/security-overview-feature-specific-alert-page.yml b/translations/es-ES/data/features/security-overview-feature-specific-alert-page.yml new file mode 100644 index 0000000000..1aebf50245 --- /dev/null +++ b/translations/es-ES/data/features/security-overview-feature-specific-alert-page.yml @@ -0,0 +1,8 @@ +--- +#Reference: #7028. +#Documentation for feature-specific page for security overview at enterprise-level. +versions: + fpt: '*' + ghec: '*' + ghes: '>3.5' + ghae: 'issue-7028' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/21.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/21.yml new file mode 100644 index 0000000000..2bf7279ba8 --- /dev/null +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/21.yml @@ -0,0 +1,24 @@ +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - 'Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/).' + - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' + bugs: + - 'In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`.' + - 'SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog.' + - 'For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out.' + - 'When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified.' + changes: + - 'In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status.' + - 'When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not supported.' + - 'Support bundles now include the row count of tables stored in MySQL.' + known_issues: + - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' + - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario adminsitrador.' + - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' + - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' + - 'Cuando se habilita la opción "Los usuarios pueden buscar en GitHub.com" con las propuestas de {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios internos y privados no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' + - 'Si se habilitan las {% data variables.product.prodname_actions %} para {% data variables.product.prodname_ghe_server %}, el desmontar un nodo de réplica con `ghe-repl-teardown` tendrá éxito, pero podría devolver un `ERROR:Running migrations`.' + - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/13.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/13.yml new file mode 100644 index 0000000000..31610675bb --- /dev/null +++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/13.yml @@ -0,0 +1,26 @@ +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - 'Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/).' + - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' + bugs: + - 'In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`.' + - 'SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog.' + - 'For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out.' + - 'Videos uploaded to issue comments would not be rendered properly.' + - 'When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified.' + - 'When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests.' + changes: + - 'In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status.' + - 'When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported.' + - 'Support bundles now include the row count of tables stored in MySQL.' + - 'Dependency Graph can now be enabled without vulnerability data, allowing you to see what dependencies are in use and at what versions. Enabling Dependency Graph without enabling {% data variables.product.prodname_github_connect %} will **not** provide vulnerability information.' + known_issues: + - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario adminsitrador.' + - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' + - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' + - 'Cuando se habilita la opción "Los usuarios pueden buscar en GitHub.com" con las propuestas de {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios internos y privados no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' + - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' + - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/8.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/8.yml new file mode 100644 index 0000000000..7825e41c9e --- /dev/null +++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/8.yml @@ -0,0 +1,33 @@ +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - 'Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/).' + - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' + bugs: + - 'In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`.' + - 'SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog' + - 'For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out.' + - 'Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`.' + - 'When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified.' + - 'Videos uploaded to issue comments would not be rendered properly.' + - 'When using the file finder on a repository page, typing the backspace key within the search field would result in search results being listed multiple times and cause rendering problems.' + - 'When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events.' + - 'When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests.' + changes: + - 'In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status.' + - 'When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported.' + - 'Support bundles now include the row count of tables stored in MySQL.' + - 'When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects.' + - 'The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload.' + known_issues: + - 'Después de haber actualizado a {% data variables.product.prodname_ghe_server %} 3.3, podría que las {% data variables.product.prodname_actions %} no inicien automáticamente. Para resolver este problema, conéctate al aplicativo a través de SSH y ejecuta el comando `ghe-actions-start`.' + - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario adminsitrador.' + - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' + - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' + - 'Cuando se habilita la opción "Los usuarios pueden buscar en GitHub.com" con las propuestas de {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios internos y privados no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' + - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' + - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' + - 'Los ajustes de almacenamiento de {% data variables.product.prodname_actions %} no pueden validarse y guardarse en la {% data variables.enterprise.management_console %} cuando se selecciona "Forzar estilo de ruta" y, en su lugar, debe configurarse la utilidad de línea de comando `ghe-actions-precheck`.' + - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-4/2.yml b/translations/es-ES/data/release-notes/enterprise-server/3-4/2.yml index c9c4416841..32d95b5c0a 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-4/2.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-4/2.yml @@ -51,5 +51,8 @@ sections: - heading: 'Obsoletización de extensiones de bit-caché personalizadas' notes: - "Desde {% data variables.product.prodname_ghe_server %} 3.1, el soporte de las extensiones bit-cache propietarias de {% data variables.product.company_short %} se comenzó a eliminar paulatinamente. Estas extensiones son obsoletas en {% data variables.product.prodname_ghe_server %} 3.3 en adelante.\n\nCualquier repositorio que ya haya estado presente y activo en {% data variables.product.product_location %} ejecutando la versión 3.1 o 3.2 ya se actualizó automáticamente.\n\nLos repositorios que no estuvieron presentes y activos antes de mejorar a {% data variables.product.prodname_ghe_server %} 3.3 podrían no funcionar de forma óptima sino hasta que se ejecute una tarea de mantenimiento de repositorio y esta se complete exitosamente.\n\nPara iniciar una tarea de mantenimiento de repositorio manualmente, dirígete a `https:///stafftools/repositories///network` en cada repositorio afectado y haz clic en el botón **Schedule**.\n" + - heading: 'Theme picker for GitHub Pages has been removed' + notes: + - "The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see \"[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll).\"\n" backups: - '{% data variables.product.prodname_ghe_server %} 3.4 requiere por lo menos de las [Utilidades de Respaldo de GitHub Enterprise 3.4.0](https://github.com/github/backup-utils) para la [Recuperación de Desastres y Respaldos](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-4/3.yml b/translations/es-ES/data/release-notes/enterprise-server/3-4/3.yml new file mode 100644 index 0000000000..5558cff86a --- /dev/null +++ b/translations/es-ES/data/release-notes/enterprise-server/3-4/3.yml @@ -0,0 +1,35 @@ +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - 'Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/).' + - 'Los paquetes se actualizaron a las últimas versiones de seguridad.' + bugs: + - 'In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`.' + - 'SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog.' + - 'When adding custom patterns and providing non-UTF8 test strings, match highlighting was incorrect.' + - 'LDAP users with an underscore character (`_`) in their user names can now login successfully.' + - 'For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out.' + - 'After enabling SAML encrypted assertions with Azure as identity provider, the sign in page would fail with a `500` error.' + - 'Character key shortcut preferences weren''t respected.' + - 'Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`.' + - 'When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified.' + - 'Videos uploaded to issue comments would not be rendered properly.' + - 'When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events.' + - 'When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests.' + changes: + - 'In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status.' + - 'The Nomad allocation timeout for Dependency Graph has been increased to ensure post-upgrade migrations can complete.' + - 'When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported.' + - 'Support bundles now include the row count of tables stored in MySQL.' + - 'When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects.' + - 'The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload.' + known_issues: + - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario adminsitrador.' + - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' + - 'Los archivos rastreados del LFS de Git que se [cargaron mediante la interface web](https://github.com/blog/2105-upload-files-to-your-repositories) se agregaron incorrecta y directamente al repositorio.' + - 'Las propuestas no pudieron cerrarse si contenían un permalink a un blob en el mismo repositorio en donde la ruta de archvio del blob era más grande a 255 caracteres.' + - 'Cuando se habilita la opción "Los usuarios pueden buscar en GitHub.com" con las propuestas de {% data variables.product.prodname_github_connect %}, las propuestas en los repositorios internos y privados no se incluyen en los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %}.' + - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.' + - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.' + - "Cuando utilizas las aserciones cifradas con {% data variables.product.prodname_ghe_server %} 3.4.0 y 3.4.1, un atributo nuevo de XML `WantAssertionsEncrypted` en el `SPSSODescriptor` contiene un atributo inválido para los metadatos de SAML. Los IdP que consumen esta terminal de metadatos de SAML podrían encontrar errores al validar el modelo XML de los metadatos de SAML. Habrá una corrección disponible en el siguiente lanzamiento de parche. [Actualizado: 2022-04-11]\n\nPara darle una solución a este problema, puedes tomar una de las dos acciones siguientes.\n- Reconfigurar el IdP cargando una copia estática de los metadatos de SAML sin el atributo `WantAssertionsEncrypted`.\n- Copiar los metadatos de SAML, eliminar el atributo `WantAssertionsEncrypted`, hospedarlo en un servidor web y reconfigurar el IdP para que apunte a esa URL.\n" diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml index bccf6e2211..d445ab3f00 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -145,6 +145,9 @@ sections: - heading: 'CodeQL runner deprecated in favor of CodeQL CLI' notes: - "The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, 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).\"\n" + - heading: 'Theme picker for GitHub Pages has been removed' + notes: + - "The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see \"[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll).\"\n" known_issues: - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario adminsitrador.' - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.' diff --git a/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml b/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml index 76d38f7860..032bc1087a 100644 --- a/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml +++ b/translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml @@ -1,7 +1,7 @@ date: '2021-12-06' friendlyDate: 'December 6, 2021' title: 'December 6, 2021' -currentWeek: true +currentWeek: false sections: features: - heading: 'Administration' diff --git a/translations/es-ES/data/release-notes/github-ae/2022-05/2022-05-17.yml b/translations/es-ES/data/release-notes/github-ae/2022-05/2022-05-17.yml new file mode 100644 index 0000000000..b8da1e31db --- /dev/null +++ b/translations/es-ES/data/release-notes/github-ae/2022-05/2022-05-17.yml @@ -0,0 +1,201 @@ +date: '2022-05-17' +friendlyDate: 'May 17, 2022' +title: 'May 17, 2022' +currentWeek: true +sections: + features: + - heading: 'GitHub Advanced Security features are generally available' + notes: + - | + Code scanning and secret scanning are now generally available for GitHub AE. For more information, see "[About code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)." + - | + Custom patterns for secret scanning is now generally available. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + + - heading: 'View all code scanning alerts for a pull request' + notes: + - | + You can now find all code scanning alerts associated with your pull request with the new pull request filter on the code scanning alerts page. The pull request checks page shows the alerts introduced in a pull request, but not existing alerts on the pull request branch. The new "View all branch alerts" link on the Checks page takes you to the code scanning alerts page with the specific pull request filter already applied, so you can see all the alerts associated with your pull request. This can be useful to manage lots of alerts, and to see more detailed information for individual alerts. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)." + + - heading: 'Security overview for organizations' + notes: + - | + GitHub Advanced Security now offers an organization-level view of the application security risks detected by code scanning, Dependabot, and secret scanning. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. + + In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + + ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) + + - heading: 'Dependency graph' + notes: + - | + Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." + + - heading: 'Dependabot alerts' + notes: + - | + Dependabot alerts can now notify you of vulnerabilities in your dependencies on GitHub AE. You can enable Dependabot alerts by enabling the dependency graph, enabling GitHub Connect, and syncing vulnerabilities from the GitHub Advisory Database. This feature is in beta and subject to change. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)." + + After you enable Dependabot alerts, members of your organization will receive notifications any time a new vulnerability that affects their dependencies is added to the GitHub Advisory Database or a vulnerable dependency is added to their manifest. Members can customize notification settings. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)." + + - heading: 'Security manager role for organizations' + notes: + - | + Organizations can now grant teams permission to manage security alerts and settings on all their repositories. The "security manager" role can be applied to any team and grants the team's members the following permissions. + + - Read access on all repositories in the organization + - Write access on all security alerts in the organization + - Access to the organization-level security tab + - Write access on security settings at the organization level + - Write access on security settings at the repository level + + For more information, see "[Managing security managers in your organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." + + - heading: 'Ephemeral runners and autoscaling webhooks for GitHub Actions' + notes: + - | + GitHub AE now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. + + Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, GitHub AE automatically unregisteres ephemeral runners, allowing you to perform any post-job management. + + You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to job requests from GitHub Actions. + + For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)." + + - heading: 'Composite actions for GitHub Actions' + notes: + - | + You can reduce duplication in your workflows by using composition to reference other actions. Previously, actions written in YAML could only use scripts. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)." + + - heading: 'New token scope for management of self-hosted runners' + notes: + - | + Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the `new manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to many REST API endpoints to manage your enterprise's self-hosted runners. + + - heading: 'Audit log accessible via REST API' + notes: + - | + You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." + + - heading: 'Expiration dates for personal access tokens' + notes: + - | + You can now set an expiration date on new and existing personal access tokens. GitHub AE will send you an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving you a duplicate token with the same properties as the original. When using a token with the GitHub AE API, you'll see a new header, `GitHub-Authentication-Token-Expiration`, indicating the token's expiration date. You can use this in scripts, for example to log a warning message as the expiration date approaches. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" and "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#using-personal-access-tokens)." + + - heading: 'Export a list of people with access to a repository' + notes: + - | + Organization owners can now export a list of the people with access to a repository in CSV format. For more information, see "[Viewing people with access to your repository](/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository#exporting-a-list-of-people-with-access-to-your-repository)." + + - heading: 'Improved management of code review assignments' + notes: + - | + New settings to manage code review assignment code review assignment help distribute a team's pull request review across the team members so reviews aren't the responsibility of just one or two team members. + + - Child team members: Limit assignment to only direct members of the team. Previously, team review requests could be assigned to direct members of the team or members of child teams. + - Count existing requests: Continue with automatic assignment even if one or more members of the team are already requested. Previously, a team member who was already requested would be counted as one of the team's automatic review requests. + - Team review request: Keep a team assigned to review even if one or more members is newly assigned. + + For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." + + - heading: 'New themes' + notes: + - | + Two new themes are available for the GitHub AE web UI. + + - A dark high contrast theme, with greater contrast between foreground and background elements + - Light and dark colorblind, which swap colors such as red and green for orange and blue + + For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + + - heading: 'Markdown improvements' + notes: + - | + You can now use footnote syntax in any Markdown field to reference relevant information without disrupting the flow of your prose. Footnotes are displayed as superscript links. Click a footnote to jump to the reference, displayed in a new section at the bottom of the document. 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#footnotes)." + + - | + You can now toggle between the source view and rendered Markdown view through the web UI by clicking the {% octicon "code" aria-label="The Code icon" %} button to "Display the source diff" at the top of any Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file. + + - | + You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + + - | + GitHub AE now automatically generates a table of contents for Wikis, based on headings. + + changes: + - heading: 'Performance' + notes: + - | + Page loads and jobs are now significantly faster for repositories with many Git refs. + + - heading: 'Administration' + notes: + - | + The user impersonation process is improved. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise owner. For more information, see "[Impersonating a user](/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)." + + - heading: 'GitHub Actions' + notes: + - | + To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." + + - | + The audit log now includes additional events for GitHub Actions. GitHub AE now records audit log entries for the following events. + + - A self-hosted runner is registered or removed. + - A self-hosted runner is added to a runner group, or removed from a runner group. + - A runner group is created or removed. + - A workflow run is created or completed. + - A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner. + + For more information, see "[Security hardening for GitHub Actions](/actions/security-guides/security-hardening-for-github-actions)." + + - heading: 'GitHub Advanced Security' + notes: + - | + Code scanning will now map alerts identified in `on:push` workflows to show up on pull requests, when possible. The alerts shown on the pull request are those identified by comparing the existing analysis of the head of the branch to the analysis for the target branch that you are merging against. Note that if the pull request's merge commit is not used, alerts can be less accurate when compared to the approach that uses `on:pull_request` triggers. For more information, see "[About code scanning with CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." + + Some other CI/CD systems can exclusively be configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, code scanning will try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see "[Uploading a SARIF file to GitHub](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)." + + - | + GitHub AE now detects secrets from additional providers. For more information, see "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets)." + + - heading: 'Pull requests' + notes: + - | + The timeline and Reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members because that team uses code review assignment. + + ![Screenshot of indicator for automatic assignment of code review](https://user-images.githubusercontent.com/2503052/134931920-409dea07-7a70-4557-b208-963357db7a0d.png) + + - | + You can now filter pull request searches to only include pull requests you are directly requested to review by choosing **Awaiting review from you**. For more information, see "[Searching issues and pull requests](https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests)." + + - | + If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list. + + - | + When viewing a branch that has a corresponding open pull request, GitHub AE now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request. + + - | + You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click in the toolbar. Note that this feature is currently only available in some browsers. + + - | + A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [GitHub Changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/). + + - heading: 'Repositories' + notes: + - | + GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](​​https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." + + - | + You can now add, delete, or view autolinks through the Repositories API's Autolinks endpoint. For more information, see "[Autolinked references and URLs](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)" and "[Repositories](/rest/reference/repos#autolinks)" in the REST API documentation. + + - heading: 'Releases' + notes: + + - | + The tag selection component for GitHub releases is now a drop-down menu rather than a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)." + + - heading: 'Markdown' + notes: + + - | + When dragging and dropping files such as images and videos into a Markdown editor, GitHub AE now uses the mouse pointer location instead of the cursor location when placing the file. diff --git a/translations/es-ES/data/reusables/actions/allow-specific-actions-intro.md b/translations/es-ES/data/reusables/actions/allow-specific-actions-intro.md index 3a4e454693..de119a931a 100644 --- a/translations/es-ES/data/reusables/actions/allow-specific-actions-intro.md +++ b/translations/es-ES/data/reusables/actions/allow-specific-actions-intro.md @@ -5,8 +5,8 @@ Cuando eliges {% data reusables.actions.policy-label-for-select-actions-workflows %}, se permiten las acciones locales{% if actions-workflow-policy %} y los flujos de trabajo reutilizables{% endif %} y hay opciones adicionales para permitir otras acciones específicas {% if actions-workflow-policy %} y flujos de trabajo reutilizables{% endif %}: -- **Permitir acciones que crea {% data variables.product.prodname_dotcom %}:** Puedes permitir que los flujos de trabajo utilicen todas las acciones que haya creado {% data variables.product.prodname_dotcom %}. Las acciones que crea {% data variables.product.prodname_dotcom %} se ubican en las organizaciones `actions` y `github`. Para obtener más información, consulta las organizaciones de [`actions`](https://github.com/actions) y [`github`](https://github.com/github).{% ifversion fpt or ghes or ghae-issue-5094 or ghec %} -- **Permite las acciones de Marketplace de creadores verificados:** {% ifversion ghes or ghae-issue-5094 %}Esta opción está disponible si tienes habilitado {% data variables.product.prodname_github_connect %} y si lo configuraste con {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de GitHub.com utilizando GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)."{% endif %} Puedes permitir que los flujos de trabajo utilicen todas las acciones de {% data variables.product.prodname_marketplace %} que hayan hecho los creadores verificados. Cuando GitHub haya verificado al creador de la acción como una organización asociada, se mostrará la insignia de {% octicon "verified" aria-label="The verified badge" %} junto a la acción en {% data variables.product.prodname_marketplace %}.{% endif %} +- **Permitir acciones que crea {% data variables.product.prodname_dotcom %}:** Puedes permitir que los flujos de trabajo utilicen todas las acciones que haya creado {% data variables.product.prodname_dotcom %}. Las acciones que crea {% data variables.product.prodname_dotcom %} se ubican en las organizaciones `actions` y `github`. Para obtener más información, consulta las organizaciones de [`actions`](https://github.com/actions) y [`github`](https://github.com/github).{% ifversion fpt or ghes or ghae or ghec %} +- **Permite las acciones de Marketplace de creadores verificados:** {% ifversion ghes or ghae %}Esta opción está disponible si tienes habilitado {% data variables.product.prodname_github_connect %} y si lo configuraste con {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[Habilitar el acceso automático a las acciones de GitHub.com utilizando GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)."{% endif %} Puedes permitir que los flujos de trabajo utilicen todas las acciones de {% data variables.product.prodname_marketplace %} que hayan hecho los creadores verificados. Cuando GitHub haya verificado al creador de la acción como una organización asociada, se mostrará la insignia de {% octicon "verified" aria-label="The verified badge" %} junto a la acción en {% data variables.product.prodname_marketplace %}.{% endif %} - **Permitir acciones específicas{% if actions-workflow-policy %} y flujos de trabajo reutilizables{% endif %}:** Puedes restringir a los flujos de trabajo para que utilicen acciones{% if actions-workflow-policy %} y flujos de trabajo reutilizables{% endif %} en repositorios y organizaciones específicos. Para restringir el acceso a las etiquetas o SHA de confirmación específicos de una acción{% if actions-workflow-policy %} o flujo de trabajo reutilizable{% endif %}, utiliza la misma sintaxis que se utiliza en el flujo de trabajo para seleccionar la acción{% if actions-workflow-policy %} o flujo de trabajo reutilizable{% endif %}. diff --git a/translations/es-ES/data/reusables/actions/jobs/using-matrix-strategy.md b/translations/es-ES/data/reusables/actions/jobs/using-matrix-strategy.md index de1ac26cb1..391a6469ff 100644 --- a/translations/es-ES/data/reusables/actions/jobs/using-matrix-strategy.md +++ b/translations/es-ES/data/reusables/actions/jobs/using-matrix-strategy.md @@ -1,4 +1,4 @@ -Utiliza `jobs..strategy.matrix` para definir una matriz de configuraciones de jobs diferentes. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a veriable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`: +Utiliza `jobs..strategy.matrix` para definir una matriz de configuraciones de jobs diferentes. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a variable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`: ```yaml jobs: diff --git a/translations/es-ES/data/reusables/actions/message-parameters.md b/translations/es-ES/data/reusables/actions/message-parameters.md index 932e4ffd18..28e7b2433d 100644 --- a/translations/es-ES/data/reusables/actions/message-parameters.md +++ b/translations/es-ES/data/reusables/actions/message-parameters.md @@ -1 +1 @@ -| Parámetro | Valor | | :- | :- |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `título` | Título personalizado |{% endif %} | `archivo` | Nombre de archivo | | `código` | Número de columna, comenzando en 1 |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `endColumn` | Número de columna final |{% endif %} | `línea` | Número de línea, comenzando en 1 |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `endLine` | Número de línea final |{% endif %} +| Parámetro | Valor | | :- | :- |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `título` | Título personalizado |{% endif %} | `archivo` | Nombre de archivo | | `código` | Número de columna, comenzando en 1 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endColumn` | Número de columna final |{% endif %} | `línea` | Número de línea, comenzando en 1 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endLine` | Número de línea final |{% endif %} diff --git a/translations/es-ES/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/es-ES/data/reusables/apps/deprecating_auth_with_query_parameters.md index a36077d0f1..be31507f48 100644 --- a/translations/es-ES/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/es-ES/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,4 +1,3 @@ -{% ifversion fpt or ghes or ghae or ghec %} {% warning %} **Aviso de Obsoletización:** {% data variables.product.prodname_dotcom %} descontinuará la autenticación a la API utilizando parámetros de consulta. Se debe autenticar en la API con [autenticación básica de HTTP](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% ifversion fpt or ghec %} El utilizar parámetros de consulta para autenticarse en la API ya no funcionará desde el 5 de mayo de 2021. {% endif %} Para obtener más información, incluyendo los periodos de interrupción programada, consulta la [publicación del blog](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). @@ -6,4 +5,3 @@ {% ifversion ghes or ghae %} La autenticación a la API a través de parámetros de búsqueda, si bien está disponible, ya no es compatible por motivos de seguridad. En vez de ésto, recomendamos a los integradores que migren su token de acceso, `client_id`, o `client_secret` al encabezado. {% data variables.product.prodname_dotcom %} notificará sobre la eliminación de la autenticación por parámetros de consulta con tiempo suficiente. {% endif %} {% endwarning %} -{% endif %} diff --git a/translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md b/translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md index 3c05a65e56..4eed4c0a5b 100644 --- a/translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md +++ b/translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md @@ -28,13 +28,13 @@ {%- ifversion ghes %} | `config_entry` | Contains activities related to configuration settings. Estos eventos solo se pueden ver en la bitácora de auditoría del administrador de sitio. {%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | `dependabot_alerts` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. Para obtener más información, consulta la sección "[Acerca de las alertas para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". | `dependabot_alerts_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. | `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access. {%- endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} | `dependabot_security_updates` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. Para obtener más información, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)". | `dependabot_security_updates_new_repos` | 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 or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} | `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". | `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization. {%- endif %} {%- ifversion fpt or ghec %} @@ -116,7 +116,7 @@ {%- ifversion fpt or ghec %} | `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization. {%- endif %} -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} | `repository_vulnerability_alert` | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies). {%- endif %} {%- ifversion fpt or ghec %} diff --git a/translations/es-ES/data/reusables/cli/filter-issues-and-pull-requests-tip.md b/translations/es-ES/data/reusables/cli/filter-issues-and-pull-requests-tip.md index c6ae95e4b4..d94a3be7c4 100644 --- a/translations/es-ES/data/reusables/cli/filter-issues-and-pull-requests-tip.md +++ b/translations/es-ES/data/reusables/cli/filter-issues-and-pull-requests-tip.md @@ -1,7 +1,5 @@ -{% ifversion fpt or ghes or ghae or ghec %} {% tip %} **Tip**: También puedes filtrar propuestas o solicitudes de cambios si utilizas el {% data variables.product.prodname_cli %}. Para obtener más información, consulta "[`gh issue list`](https://cli.github.com/manual/gh_issue_list)" o "[`gh pr list`](https://cli.github.com/manual/gh_pr_list)" en la documentación de {% data variables.product.prodname_cli %}. {% endtip %} -{% endif %} diff --git a/translations/es-ES/data/reusables/code-scanning/beta.md b/translations/es-ES/data/reusables/code-scanning/beta.md index 1e7fb13e55..eb25869b43 100644 --- a/translations/es-ES/data/reusables/code-scanning/beta.md +++ b/translations/es-ES/data/reusables/code-scanning/beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-5752 %} +{% ifversion ghae %} diff --git a/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md index d2f101906b..0a1e685eb9 100644 --- a/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ b/translations/es-ES/data/reusables/codespaces/click-remote-explorer-icon-vscode.md @@ -1 +1 @@ -1. En {% data variables.product.prodname_vscode %}, en la barra lateral izquierda, da clic en el icono de Explorador Remoto. ![El icono de explorador remoto en {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) +1. En {% data variables.product.prodname_vscode_shortname %}, en la barra lateral izquierda, da clic en el icono de Explorador Remoto. ![El icono de explorador remoto en {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) diff --git a/translations/es-ES/data/reusables/codespaces/committing-link-to-procedure.md b/translations/es-ES/data/reusables/codespaces/committing-link-to-procedure.md index b072b793c5..9d00dcf16a 100644 --- a/translations/es-ES/data/reusables/codespaces/committing-link-to-procedure.md +++ b/translations/es-ES/data/reusables/codespaces/committing-link-to-procedure.md @@ -1,3 +1,3 @@ -Una vez que hayas hecho cambios a tu codespace, ya sea de código nuevo o de cambios de configuración, necesitarás confirmar tus cambios. El confirmar los cambios en tu repositorio garantiza que cualquiera que cree un codespace desde este repositorio tendrá la misma configuración. Esto también significa que cualquier personalización que hagas, tal como agregar extensiones de {% data variables.product.prodname_vscode %}, aparecerá para todos los usuarios. +Una vez que hayas hecho cambios a tu codespace, ya sea de código nuevo o de cambios de configuración, necesitarás confirmar tus cambios. El confirmar los cambios en tu repositorio garantiza que cualquiera que cree un codespace desde este repositorio tendrá la misma configuración. Esto también significa que cualquier personalización que hagas, tal como agregar extensiones de {% data variables.product.prodname_vscode_shortname %}, aparecerá para todos los usuarios. Para obtener más información, consulta la sección "[Utilizar el control de código fuente en tu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)" diff --git a/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md index 363dffdd70..25972d7236 100644 --- a/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ b/translations/es-ES/data/reusables/codespaces/connect-to-codespace-from-vscode.md @@ -1 +1 @@ -Puedes conectarte a tu codespace directamente desde {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la sección "[Utilizar codespaces en {% data variables.product.prodname_vscode %}](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)". +Puedes conectarte a tu codespace directamente desde {% data variables.product.prodname_vscode_shortname %}. Para obtener más información, consulta la sección "[Utilizar codespaces en {% data variables.product.prodname_vscode_shortname %}](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)". diff --git a/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md index b7f37db217..2531a8c427 100644 --- a/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md +++ b/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md @@ -1,8 +1,8 @@ -Después de que conectes tu cuenta de {% data variables.product.product_location %} a la extensión de {% data variables.product.prodname_github_codespaces %}, puedes crear un codespace nuevo. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). +Después de que conectes tu cuenta de {% data variables.product.product_location %} a la extensión de {% data variables.product.prodname_github_codespaces %}, puedes crear un codespace nuevo. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). {% note %} -**Note**: Currently, {% data variables.product.prodname_vscode %} doesn't allow you to choose a dev container configuration when you create a codespace. Si quieres elegir una configuración de contenedor dev específica, utiliza la interfaz web de {% data variables.product.prodname_dotcom %} para crear tu codespace. For more information, click the **Web browser** tab at the top of this page. +**Nota**: Actualmente, {% data variables.product.prodname_vscode_shortname %} no te permite elegir una configuración de contenedor dev cuando creas un codespace. Si quieres elegir una configuración de contenedor dev específica, utiliza la interfaz web de {% data variables.product.prodname_dotcom %} para crear tu codespace. For more information, click the **Web browser** tab at the top of this page. {% endnote %} diff --git a/translations/es-ES/data/reusables/codespaces/deleting-a-codespace-in-vscode.md b/translations/es-ES/data/reusables/codespaces/deleting-a-codespace-in-vscode.md index 8c4ea090f3..6531fb1e5b 100644 --- a/translations/es-ES/data/reusables/codespaces/deleting-a-codespace-in-vscode.md +++ b/translations/es-ES/data/reusables/codespaces/deleting-a-codespace-in-vscode.md @@ -1,4 +1,4 @@ -You can delete codespaces from within {% data variables.product.prodname_vscode %} when you are not currently working in a codespace. +You can delete codespaces from within {% data variables.product.prodname_vscode_shortname %} when you are not currently working in a codespace. {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 1. Under "GITHUB CODESPACES", right-click the codespace you want to delete. diff --git a/translations/es-ES/data/reusables/codespaces/more-info-devcontainer.md b/translations/es-ES/data/reusables/codespaces/more-info-devcontainer.md index 430a9f1156..f0fd5c863b 100644 --- a/translations/es-ES/data/reusables/codespaces/more-info-devcontainer.md +++ b/translations/es-ES/data/reusables/codespaces/more-info-devcontainer.md @@ -1 +1 @@ -For information about the settings and properties that you can set in a `devcontainer.json` file, see "[devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json)" in the {% data variables.product.prodname_vscode %} documentation. \ No newline at end of file +For information about the settings and properties that you can set in a `devcontainer.json` file, see "[devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json)" in the {% data variables.product.prodname_vscode_shortname %} documentation. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/codespaces/use-visual-studio-features.md b/translations/es-ES/data/reusables/codespaces/use-visual-studio-features.md index 17af192cf7..89cdff1ebc 100644 --- a/translations/es-ES/data/reusables/codespaces/use-visual-studio-features.md +++ b/translations/es-ES/data/reusables/codespaces/use-visual-studio-features.md @@ -1 +1 @@ -Puedes editar código, depurar y utilizar comandos de git mientras que desarrollas en un codespace con {% data variables.product.prodname_vscode %}. Para obtener más información, consulta la sección [documentación de {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/docs). +Puedes editar código, depurar y utilizar comandos de git mientras que desarrollas en un codespace con {% data variables.product.prodname_vscode_shortname %}. Para obtener más información, consulta la sección [documentación de {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs). diff --git a/translations/es-ES/data/reusables/codespaces/vscode-settings-order.md b/translations/es-ES/data/reusables/codespaces/vscode-settings-order.md index 1519e4c06f..e7d8ffe0e2 100644 --- a/translations/es-ES/data/reusables/codespaces/vscode-settings-order.md +++ b/translations/es-ES/data/reusables/codespaces/vscode-settings-order.md @@ -1 +1 @@ -Cuando configuras los ajustes de editor para {% data variables.product.prodname_vscode %}, hay tres alcances disponibles: _Espacio de trabajo_, _[Codespaces] Remotos _, y _Usuario_. Si una configuración se define en varios alcances, los ajustes de _espacio de trabajo_ tomarán prioridad, luego los de _[Codespaces] Remotos_, y luego los de _Usuario_. +Cuando configuras los ajustes de editor para {% data variables.product.prodname_vscode_shortname %}, hay tres alcances disponibles: _Espacio de trabajo_, _[Codespaces] Remotos _, y _Usuario_. Si una configuración se define en varios alcances, los ajustes de _espacio de trabajo_ tomarán prioridad, luego los de _[Codespaces] Remotos_, y luego los de _Usuario_. diff --git a/translations/es-ES/data/reusables/dependabot/dependabot-alerts-beta.md b/translations/es-ES/data/reusables/dependabot/dependabot-alerts-beta.md index 3af11899ae..e89ba6fb00 100644 --- a/translations/es-ES/data/reusables/dependabot/dependabot-alerts-beta.md +++ b/translations/es-ES/data/reusables/dependabot/dependabot-alerts-beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-4864 %} +{% ifversion ghae %} {% note %} **Nota:** {% data variables.product.prodname_dependabot_alerts %} se encuentra acutalmente en beta y está sujeto a cambios. diff --git a/translations/es-ES/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md b/translations/es-ES/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md index 704200fb54..d5ede5dbcc 100644 --- a/translations/es-ES/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md +++ b/translations/es-ES/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md @@ -1,3 +1,3 @@ -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} Los propietarios de empresa pueden configurar {% ifversion ghes %}la gráfica de dependencias y {% endif %} las {% data variables.product.prodname_dependabot_alerts %} para una empresa. Para obtener más información, consulta la sección {% ifversion ghes %}"[Habilitar la gráfica de dependencias para tu empresa](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" y {% endif %}"[Habilitar el {% data variables.product.prodname_dependabot %} para tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". {% endif %} diff --git a/translations/es-ES/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md b/translations/es-ES/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md index f50a5571c8..16220f08cf 100644 --- a/translations/es-ES/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md +++ b/translations/es-ES/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md @@ -1 +1 @@ -If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for any {% data variables.product.prodname_codespaces %} usage, and for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} usage beyond the amounts included with your account. +Si compraste {% data variables.product.prodname_enterprise %} mediante un Acuerdo Empresarial de Microsoft, puedes conectar tu ID de suscripción de Azure a tu cuenta empresarial para habilitar y pagar por cualquier uso de {% data variables.product.prodname_codespaces %} y por el uso de {% data variables.product.prodname_actions %} o {% data variables.product.prodname_registry %} más allá de las cantidades que incluye tu cuenta. diff --git a/translations/es-ES/data/reusables/gated-features/dependency-review.md b/translations/es-ES/data/reusables/gated-features/dependency-review.md index 8c6343bbcd..a6169c679d 100644 --- a/translations/es-ES/data/reusables/gated-features/dependency-review.md +++ b/translations/es-ES/data/reusables/gated-features/dependency-review.md @@ -7,7 +7,7 @@ La revisión de dependencias se incluye en {% data variables.product.product_nam {%- elsif ghes > 3.1 %} La revisión de dependencias se encuentra disponible para los repositorios que pertenecen a las organizaciones en {% data variables.product.product_name %}. Esta característica requiere una licencia para la {% data variables.product.prodname_GH_advanced_security %}. -{%- elsif ghae-issue-4864 %} +{%- elsif ghae %} La revisión de dependencias se encuentra disponible para los repositorios que pertenecen a las organizaciones en {% data variables.product.product_name %}. Esta es una característica de la {% data variables.product.prodname_GH_advanced_security %} (gratuita durante el lanzamiento beta). -{%- endif %} {% data reusables.advanced-security.more-info-ghas %} \ No newline at end of file +{%- endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md index 2e4e525349..854ecbe7c5 100644 --- a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md +++ b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} Puedes elegir el método de entrega y la frecuencia de las notificaciones de las {% data variables.product.prodname_dependabot_alerts %} en los repositorios que estás observando o donde te hayas suscrito a las notificaciones para las alertas de seguridad. {% endif %} diff --git a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md index b7a01f72c4..8ee57be68b 100644 --- a/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md +++ b/translations/es-ES/data/reusables/notifications/vulnerable-dependency-notification-options.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} -{% ifversion fpt or ghec %}Predeterminadamente, recibirás notificaciones:{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 %}Predeterminadamente, si tu propietario de empresa configuró las notificaciones por correo electrónico en tu instancia, recibiras {% data variables.product.prodname_dependabot_alerts %}:{% endif %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +{% ifversion fpt or ghec %}Predeterminadamente, recibirás notificaciones:{% endif %}{% ifversion ghes > 3.1 or ghae %}Predeterminadamente, si tu propietario de empresa configuró las notificaciones por correo electrónico en tu instancia, recibiras {% data variables.product.prodname_dependabot_alerts %}:{% endif %} - por correo electrónico, se enviará un mensaje de correo electrónico cuando se habilite el {% data variables.product.prodname_dependabot %} para un repositorio cuando se confirme un archivo de manifiesto nuevo en dicho repositorio y cuando se encuentre una vulnerabilidad nueva de severidad crítica o alta (opción **Enviar un correo electrónico cada vez que se encuentra una vulnerabilidad**). - en la interface de usuario, se muestra una advertencia en tu archivo de repositorio y vistas de código si hay dependencias vulnerables (opción de **Alertas de la IU**). diff --git a/translations/es-ES/data/reusables/organizations/security-overview-feature-specific-page.md b/translations/es-ES/data/reusables/organizations/security-overview-feature-specific-page.md new file mode 100644 index 0000000000..183ce587b5 --- /dev/null +++ b/translations/es-ES/data/reusables/organizations/security-overview-feature-specific-page.md @@ -0,0 +1 @@ +1. Como alternativa y opción, utiliza la barra lateral a la izquierda para filtrar información por característica de seguridad. On each page, you can use filters that are specific to that feature to fine-tune your search. diff --git a/translations/es-ES/data/reusables/organizations/team_maintainers_can.md b/translations/es-ES/data/reusables/organizations/team_maintainers_can.md index 922c2d3a13..799f1d5c89 100644 --- a/translations/es-ES/data/reusables/organizations/team_maintainers_can.md +++ b/translations/es-ES/data/reusables/organizations/team_maintainers_can.md @@ -10,6 +10,6 @@ Los miembros con permisos de mantenedor del equipo pueden hacer lo siguiente: - [Agregar a miembros de la organización al equipo](/articles/adding-organization-members-to-a-team) - [Eliminar a miembros de la organización del equipo](/articles/removing-organization-members-from-a-team) - [Promover un miembro del equipo existente a mantenedor del equipo](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member) -- Eliminar el acceso del equipo a los repositorios {% ifversion fpt or ghes or ghae or ghec %} -- [Administrar los ajustes de revisión de código para el equipo](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% endif %}{% ifversion fpt or ghec %} +- Eliminar el acceso del equipo a los repositorios +- [Administrar los ajustes de revisión de código para el equipo](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% ifversion fpt or ghec %} - [Administrar los recordatorios programados para las solicitudes de extracción](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md index 7a4eea9666..833ffffaa4 100644 --- a/translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md +++ b/translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md @@ -1,7 +1,7 @@ 1. Crea un token de acceso personal nuevo (PAT) con los alcances adecuados para las tareas que quieres realizar. Si tu organización requiere SSO, debes hablitarlo para tu token nuevo. {% warning %} - **Nota:** Predeterminadamente, cuando seleccionas el alcance `write:packages` para tu token de acceso personal (PAT) en la interface de usuario, también se seleccionará el alcance `repo`. El alcance `repo` ofrece un acceso amplio e innecesario, el cual te recomendamos no utilices para los flujos de trabajo de GitHub Actions en particualr. Para obtener más información, consulta la sección "[Fortalecimiento de la seguridad para las GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)". As a workaround, you can select just the `write:packages` scope for your PAT in the user interface with this url: `https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/settings/tokens/new?scopes=write:packages`. + **Nota:** Predeterminadamente, cuando seleccionas el alcance `write:packages` para tu token de acceso personal (PAT) en la interface de usuario, también se seleccionará el alcance `repo`. El alcance `repo` ofrece un acceso amplio e innecesario, el cual te recomendamos no utilices para los flujos de trabajo de GitHub Actions en particualr. Para obtener más información, consulta la sección "[Fortalecimiento de la seguridad para las GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)". Como solución alterna, puedes seleccionar solo el alcance de `write:packages` para tu PAT en la interfaz de usuario con esta url: `https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/settings/tokens/new?scopes=write:packages`. {% endwarning %} @@ -16,7 +16,7 @@ $ export CR_PAT=YOUR_TOKEN ``` 3. Utilizando el CLI para tu tipo de contenedor, ingresa en el -{% data variables.product.prodname_container_registry %} service at `{% data reusables.package_registry.container-registry-hostname %}`. +servicio del {% data variables.product.prodname_container_registry %} en `{% data reusables.package_registry.container-registry-hostname %}`. {% raw %} ```shell $ echo $CR_PAT | docker login {% endraw %}{% data reusables.package_registry.container-registry-hostname %}{% raw %} -u USERNAME --password-stdin diff --git a/translations/es-ES/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/es-ES/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md index bce8a5e711..710a154d36 100644 --- a/translations/es-ES/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md +++ b/translations/es-ES/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md @@ -1,8 +1,8 @@ {% ifversion fpt or ghec or ghes > 3.4 %} -Para autenticarse en el {% data variables.product.prodname_container_registry %} dentro de un flujo de trabajo de {% data variables.product.prodname_actions %}, utiliza el `GITHUB_TOKEN` para tener la mejor experiencia en seguridad. If your workflow is using a personal access token (PAT) to authenticate to `{% data reusables.package_registry.container-registry-hostname %}`, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`. +Para autenticarse en el {% data variables.product.prodname_container_registry %} dentro de un flujo de trabajo de {% data variables.product.prodname_actions %}, utiliza el `GITHUB_TOKEN` para tener la mejor experiencia en seguridad. Si tu flujo de trabajo utiliza un token de acceso personal (PAT) para autenticarse en `{% data reusables.package_registry.container-registry-hostname %}`, entonces te recomendamos ampliamente que lo actualices para que utilice el `GITHUB_TOKEN`. -{% ifversion fpt or ghec %}For guidance on updating your workflows that authenticate to `{% data reusables.package_registry.container-registry-hostname %}` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)."{% endif %} +{% ifversion fpt or ghec %}Para obtener orientación sobre cómo actualizar tus flujos de trabajo que se autentican con `{% data reusables.package_registry.container-registry-hostname %}` con un token de acceso personal, consulta la sección "[Actualizar un flujo de trab ajo que accede a `ghcr.io`](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)".{% endif %} Para obtener más información sobre el `GITHUB_TOKEN`, consulta la sección "[Autenticación en un flujo de trabajo](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)". diff --git a/translations/es-ES/data/reusables/package_registry/container-registry-ghes-beta.md b/translations/es-ES/data/reusables/package_registry/container-registry-ghes-beta.md index 4105fa740b..526eea575d 100644 --- a/translations/es-ES/data/reusables/package_registry/container-registry-ghes-beta.md +++ b/translations/es-ES/data/reusables/package_registry/container-registry-ghes-beta.md @@ -2,7 +2,7 @@ {% note %} -**Note**: {% data variables.product.prodname_container_registry %} is currently in beta for {% data variables.product.product_name %} and subject to change. +**Nota:**: {% data variables.product.prodname_container_registry %} se encuentra actualmente en beta para {% data variables.product.product_name %} y está sujeto a cambios. Both {% data variables.product.prodname_registry %} and subdomain isolation must be enabled to use {% data variables.product.prodname_container_registry %}. Para obtener más información, consulta la sección "[Trabajar con el registro de contenedores](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." diff --git a/translations/es-ES/data/reusables/pull_requests/close-issues-using-keywords.md b/translations/es-ES/data/reusables/pull_requests/close-issues-using-keywords.md index 0bc7bfc8af..c570cc50f9 100644 --- a/translations/es-ES/data/reusables/pull_requests/close-issues-using-keywords.md +++ b/translations/es-ES/data/reusables/pull_requests/close-issues-using-keywords.md @@ -1 +1 @@ -Puedes vincular una solicitud de extracción a un informe de problemas para {% ifversion fpt or ghes or ghae or ghec %} mostrar que se está trabajando en una solución y para cerrar {% endif %}automáticamente el informe de problemas cuando alguien fusione la solicitud de extracción. Para obtener más información, consulta la sección "[Vincular una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". +Puedes enlazar una solicitud de cambios a una propuesta para mostrar que se está haciendo una corrección actualmente y para cerrar dicha propuesta automáticamente cuando alguien fusione la solicitud de cambios. Para obtener más información, consulta la sección "[Vincular una solicitud de extracción a un informe de problemas](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)". diff --git a/translations/es-ES/data/reusables/repositories/copy-clone-url.md b/translations/es-ES/data/reusables/repositories/copy-clone-url.md index 6ff21fe76a..84d73305fe 100644 --- a/translations/es-ES/data/reusables/repositories/copy-clone-url.md +++ b/translations/es-ES/data/reusables/repositories/copy-clone-url.md @@ -1,6 +1,6 @@ 1. Sobre la lista de archivos, da clic en {% octicon "download" aria-label="The download icon" %} **Código**. ![Botón de "Código"](/assets/images/help/repository/code-button.png) -1. Para clonar el repositorio utilizando HTTPS, debajo de "Clonar con HTTPS", da clic en -{% octicon "clippy" aria-label="The clipboard icon" %}. Para clonar el repositorio utilizando una llave SSH, incluyendo un certificado emitido por la autoridad de certificados SSH de tu organización, haz clic en **Utilizar SSH** y luego en {% octicon "clippy" aria-label="The clipboard icon" %}. Para clonar un repositorio utilizando el {% data variables.product.prodname_cli %}, haz clic en **Utilizar el {% data variables.product.prodname_cli %}** y luego en {% octicon "clippy" aria-label="The clipboard icon" %}. - ![El icono de portapapeles para copiar la URL para clonar un repositorio](/assets/images/help/repository/https-url-clone.png) - {% ifversion fpt or ghes or ghae or ghec %} - ![El icono del portapapeles para copiar la URL para clonar un repositorio con el CLI de GitHub](/assets/images/help/repository/https-url-clone-cli.png){% endif %} +1. Copia la URL del repositorio. + + - Para clonar el repositorio utilizando HTTPS, debajo de "HTTPS", haz clic en {% octicon "clippy" aria-label="The clipboard icon" %}. + - Para clonar el repositorio utilizando una llave SSH, incluyendo un certificado que emita la autoridad de certificados SSH de tu organización, da clic en **SSH** y luego en {% octicon "clippy" aria-label="The clipboard icon" %}. + - Para clonar un repositorio utilizando el {% data variables.product.prodname_cli %}, haz clic en **{% data variables.product.prodname_cli %}** y luego en {% octicon "clippy" aria-label="The clipboard icon" %}. ![El icono del portapapeles para copiar la URL para clonar un repositorio con el CLI de GitHub](/assets/images/help/repository/https-url-clone-cli.png) diff --git a/translations/es-ES/data/reusables/repositories/default-issue-templates.md b/translations/es-ES/data/reusables/repositories/default-issue-templates.md index d18e42da36..dc21ef6329 100644 --- a/translations/es-ES/data/reusables/repositories/default-issue-templates.md +++ b/translations/es-ES/data/reusables/repositories/default-issue-templates.md @@ -1,2 +1 @@ -Puedes crear plantillas de propuesta predeterminadas{% ifversion fpt or ghes or ghae or ghec %} y un archivo de configuración predeterminado para estas{% endif %} en tu cuenta de organización{% ifversion fpt or ghes or ghae or ghec %} o personal{% endif %}. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." - +Puedes crear plantillas de propuestas predeterminadas y un archivo de configuración predeterminado para las plantillas de propuestas de tu organización o cuenta personal. Para obtener más información, consulta "[Crear un archivo de salud predeterminado para la comunidad](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." diff --git a/translations/es-ES/data/reusables/repositories/dependency-review.md b/translations/es-ES/data/reusables/repositories/dependency-review.md index e84202ef5a..048e977602 100644 --- a/translations/es-ES/data/reusables/repositories/dependency-review.md +++ b/translations/es-ES/data/reusables/repositories/dependency-review.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} Adicionalmente, {% data variables.product.prodname_dotcom %} puede revisar cualquier dependencia que se agregue, actualice o elimine en una solicitud de cambios que se haga contra la rama predeterminada de un repositorio así como marcar cualquier cambio que pudiera introducir una vulnerabilidad en tu proyecto. Esto te permite ubicar y tratar las dependencias vulnerables antes, en vez de después, de que lleguen a tu base de código. Para obtener más información, consulta la sección "[Revisar los cambios a las dependencias en una solicitud de cambios](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". {% endif %} diff --git a/translations/es-ES/data/reusables/repositories/enable-security-alerts.md b/translations/es-ES/data/reusables/repositories/enable-security-alerts.md index 719229a0fb..e8af3377c6 100644 --- a/translations/es-ES/data/reusables/repositories/enable-security-alerts.md +++ b/translations/es-ES/data/reusables/repositories/enable-security-alerts.md @@ -1,4 +1,4 @@ -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} Los propietarios de empresas deben habilitar las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables de {% data variables.product.product_location %} antes de que puedas utilizar esta característica. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_dependabot %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)". {% endif %} diff --git a/translations/es-ES/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/es-ES/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index eb0141e3a6..162976adc3 100644 --- a/translations/es-ES/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/es-ES/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% ifversion fpt or ghes or ghae or ghec %} Si existe una regla de rama protegida en tu repositorio que requiera un historial de confirmaciones linear, debes permitir la fusión por combinación, por rebase, o ambas. Para obtener más información, consulta la sección "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)".{% endif %} +Si existe una regla de rama protegida en tu repositorio que requiera un historial de confirmaciones linear, debes permitir la fusión por combinación, por rebase, o ambas. Para obtener más información, consulta"[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)". diff --git a/translations/es-ES/data/reusables/repositories/start-line-comment.md b/translations/es-ES/data/reusables/repositories/start-line-comment.md index 27223c8992..f2d92ff07f 100644 --- a/translations/es-ES/data/reusables/repositories/start-line-comment.md +++ b/translations/es-ES/data/reusables/repositories/start-line-comment.md @@ -1 +1 @@ -1. Pasa el puntero sobre la línea de código en la que deseas agregar un comentario y da clic en el icono de comentario azul. {% ifversion fpt or ghes or ghae or ghec %} Para agregar un comentario en líneas múltiples, da clic y arrastra para seleccionar el rango de líneas, luego da clic en el icono de comentario azul.{% endif %} ![Icono de comentario azul](/assets/images/help/commits/hover-comment-icon.gif) +1. Pasa el puntero del mouse sobre la línea de código en donde te gustaría agregar un comentario y haz clic en el icono de comentarios azul. Para agregar un comentario en varias líneas, haz clic y arrastra le mouse para seleccionar el rango de líneas y luego haz clic en el icono de comentarios azul. ![Icono de comentario azul](/assets/images/help/commits/hover-comment-icon.gif) diff --git a/translations/es-ES/data/reusables/repositories/suggest-changes.md b/translations/es-ES/data/reusables/repositories/suggest-changes.md index 4f654a1119..59d5447114 100644 --- a/translations/es-ES/data/reusables/repositories/suggest-changes.md +++ b/translations/es-ES/data/reusables/repositories/suggest-changes.md @@ -1 +1 @@ -1. Opcionalmente, para sugerir un cambio específico a la línea {% ifversion fpt or ghes or ghae or ghec %} o líneas{% endif %},da clic en{% octicon "diff" aria-label="The diff symbol" %}, luego edita el texto dentro del bloque de sugerencia. ![Bloque de sugerencia](/assets/images/help/pull_requests/suggestion-block.png) +1. Opcionalmente, para sugerir un cambio específico a la línea o líneas, haz clic en {% octicon "diff" aria-label="The diff symbol" %} y luego edita el texto dentro del bloque de sugerencias. ![Bloque de sugerencia](/assets/images/help/pull_requests/suggestion-block.png) diff --git a/translations/es-ES/data/reusables/secret-scanning/beta.md b/translations/es-ES/data/reusables/secret-scanning/beta.md index c997ecba8b..29bbb89784 100644 --- a/translations/es-ES/data/reusables/secret-scanning/beta.md +++ b/translations/es-ES/data/reusables/secret-scanning/beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-5752 %} +{% ifversion ghae %} diff --git a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md index f49bf8a249..1752782d1c 100644 --- a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -13,9 +13,9 @@ Adobe | Token Web de JSON de Adobe | adobe_jwt{% endif %} Alibaba Cloud | ID de Amazon | ID de Cliente OAuth de Amazon | amazon_oauth_client_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Amazon | Secreto de Cliente OAuth de Amazon | amazon_oauth_client_secret{% endif %} Amazon Web Services (AWS) | ID de Llave de Acceso a Amazon AWS | aws_access_key_id Amazon Web Services (AWS) | Llave de Acceso al Secreto de Amazon AWS | aws_secret_access_key -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Amazon Web Services (AWS) | Token de Sesión de Amazon AWS | aws_session_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Amazon Web Services (AWS) | ID de Llave de Acceso Temporal de Amazon AWS | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Asana | Token de Acceso Personal de Asana | asana_personal_access_token{% endif %} Atlassian | Token de la API de Atlassian | atlassian_api_token Atlassian | Token Web JSON de Atlassian | atlassian_jwt @@ -27,7 +27,7 @@ Azure | Secreto de la Aplicación de Azure Active Directory | azure_active_direc Azure | Llave del Caché de Azure para Redis | azure_cache_for_redis_access_key{% endif %} Azure | Token de Acceso Personal de Azure DevOps | azure_devops_personal_access_token Azure | Token de SAS de Azure | azure_sas_token Azure | Certificado de Azure Service Management | azure_management_certificate {%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %} Azure | Secuencia de Conexión SQL de Azure | azure_sql_connection_string{% endif %} Azure | Llave de Cuenta de Almacenamiento de Azure | azure_storage_account_key -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Beamer | Llave de la API de Beamer | beamer_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Checkout.com | Llave de Secreto de Producción de Checkout.com | checkout_production_secret_key{% endif %} @@ -35,7 +35,7 @@ Checkout.com | Llave de Secreto de Producción de Checkout.com | checkout_produc Checkout.com | Llave Secreta de Pruebas de Checkout.com | checkout_test_secret_key{% endif %} Clojars | Token de Despliegue de Clojars | clojars_deploy_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} CloudBees CodeShip | Credencial de CodeShip de CloudBees | codeship_credential{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Contentful | Token de Acceso Personal a Contentful | contentful_personal_access_token{% endif %} Databricks | Token de Acceso a Databricks | databricks_access_token {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} DigitalOcean | Token de Acceso personal a DigitalOcean | digitalocean_personal_access_token DigitalOcean | Token OAuth de DigitalOcean | digitalocean_oauth_token DigitalOcean | Token de Actualización de DigitalOcean | digitalocean_refresh_token DigitalOcean | Token de Sistema de DigitalOcean | digitalocean_system_token{% endif %} Discord | Token del Bot de Discord | discord_bot_token Doppler | Token Personal de Doppler | doppler_personal_token Doppler | Token de Servicio de Doppler | doppler_service_token Doppler | Token del CLI de Doppler | doppler_cli_token Doppler | Token de SCIM de Doppler | doppler_scim_token @@ -55,7 +55,7 @@ Fastly | Token de la API de Fastly | fastly_api_token{% endif %} Finicity | Llav Flutterwave | Llave de Secreto de la API en Vivo de Flutterwave | flutterwave_live_api_secret_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Flutterwave | Ññave Secreta de la API de Pruebas de Flutterwave | flutterwave_test_api_secret_key{% endif %} Frame.io | Token Web JSON de Frame.io | frameio_jwt Frame.io| Token de Desarrollador de Frame.io | frameio_developer_token -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} FullStory | Llave de la API de FullStory | fullstory_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} GitHub | Token de Acceso Personal de GitHub | github_personal_access_token{% endif %} @@ -67,13 +67,13 @@ GitHub | Token de Actualización de GitHub | github_refresh_token{% endif %} GitHub | Token de Acceso a la Instalación de GitHub App | github_app_installation_access_token{% endif %} GitHub | Llave Privada SSH de GitHub | github_ssh_private_key {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} GitLab | Token de Acceso a GitLab | gitlab_access_token{% endif %} GoCardless | Toekn de Acceso en Vivo a GoCardless | gocardless_live_access_token GoCardless | Token de Acceso de Prueba a GoCardless | gocardless_sandbox_access_token -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Llave del Servidor de Mensajería de Firebase Cloud | firebase_cloud_messaging_server_key{% endif %} Google | Llave de la API de Google | google_api_key Google | ID de Llave Privada de Google Cloud | google_cloud_private_key_id -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Secreto de la Llave de Acceso de Almacenamiento de Google Cloud | google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | ID de la Llave de Acceso de la Cuenta de Servicio de Almacenamiento de Google Cloud | google_cloud_storage_service_account_access_key_id{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | ID de la Llave de Acceso de Usuario de Almacenamiento de Google Cloud | google_cloud_storage_user_access_key_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Google | Token de Acceso OAuth a Google | google_oauth_access_token{% endif %} @@ -93,9 +93,9 @@ Ionic | Token de Acceso Personal de Ionic | ionic_personal_access_token{% endif Ionic | Token de Actualización de Ionic | ionic_refresh_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} JD Cloud | Llave de Acceso de JD Cloud | jd_cloud_access_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} JFrog | Token de Acceso a la Plataforma de JFrog | jfrog_platform_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} JFrog | Llave de la API de la Plataforma de JFrog | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Linear | Llave de la API de Linear | linear_api_key{% endif %} @@ -115,13 +115,13 @@ Meta | Token de Acceso a Facebook | facebook_access_token{% endif %} Midtrans | Llave del Servidor Productivo de Midtrans | midtrans_production_server_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Midtrans | Llave del Servidor de Pruebas de Midtrans | midtrans_sandbox_server_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | Llave Personal de la API de New Relic | new_relic_personal_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | Llave de la API de REST de New Relic | new_relic_rest_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | Llave de Consulta de Perspectivas de New Relic | new_relic_insights_query_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | Llave de Licencia de New Relic | new_relic_license_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Notion | Token de Integración a Notion | notion_integration_token{% endif %} @@ -135,15 +135,15 @@ Onfido | Token de la API de Onfido Live | onfido_live_api_token{% endif %} Onfido | Token de la API de Onfido Sandbox | onfido_sandbox_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} OpenAI | Llave de la API de OpenAI | openai_api_key{% endif %} Palantir | Token Web JSON de Palantir | palantir_jwt -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | Contraseña de la Base de Datos de PlanetScale | planetscale_database_password{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | Token de OAuth de PlanetScale | planetscale_oauth_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | Token de Servicio de PlanetScale | planetscale_service_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Plivo | ID de Auth de Plivo | plivo_auth_id{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Plivo | Token de Autenticación a Plivo | plivo_auth_token{% endif %} Postman | Llave de la API de Postman | postman_api_key Proctorio | Llave de Consumidor de Proctorio | proctorio_consumer_key Proctorio | Llave de Vinculación de Proctorio | proctorio_linkage_key Proctorio | Llave de Registro de Proctorio | proctorio_registration_key Proctorio | Llave de Secreto de Proctorio | proctorio_secret_key Pulumi | Toekn de Acceso a Pulumi | pulumi_access_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} PyPI | Token de la API de PyPI | pypi_api_token{% endif %} @@ -153,9 +153,9 @@ RubyGems | Llave de la API de RubyGems | rubygems_api_key{% endif %} Samsara | T Segment | Token de la API Público de Segment | segment_public_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} SendGrid | Llave de la API de SendGrid | sendgrid_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Sendinblue | Llave de la API de Sendinblue | sendinblue_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Sendinblue | Llave de SMTP de Sendinblue | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Shippo | Token de la API de Shippo Live | shippo_live_api_token{% endif %} diff --git a/translations/es-ES/data/reusables/security-center/permissions.md b/translations/es-ES/data/reusables/security-center/permissions.md new file mode 100644 index 0000000000..a6e7176abc --- /dev/null +++ b/translations/es-ES/data/reusables/security-center/permissions.md @@ -0,0 +1 @@ +Organization owners and security managers can access the security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} and view their organization's repositories via the enterprise-level security overview. Enterprise owners can use the enterprise-level security overview to view all repositories in their enterprise's organizations{% endif %}. Los miembros de un equipo pueden ver el resumen de seguridad de los repositorios para los cuales dicho equipo tiene privilegios administrativos. \ No newline at end of file diff --git a/translations/es-ES/data/reusables/security/compliance-report-list.md b/translations/es-ES/data/reusables/security/compliance-report-list.md index e1e9c19c57..db6b9af39f 100644 --- a/translations/es-ES/data/reusables/security/compliance-report-list.md +++ b/translations/es-ES/data/reusables/security/compliance-report-list.md @@ -1,4 +1,5 @@ - SOC 1, Tipo 2 - SOC 2, Tipo 2 - Cloud Security Alliance CAIQ self-assessment (CSA CAIQ) +- ISO/IEC 27001:2013 certification - {% data variables.product.prodname_dotcom_the_website %} Services Continuity and Incident Management Plan diff --git a/translations/es-ES/data/reusables/sponsors/tax-form-link.md b/translations/es-ES/data/reusables/sponsors/tax-form-link.md index 6ccf0a9173..00ac3afeb0 100644 --- a/translations/es-ES/data/reusables/sponsors/tax-form-link.md +++ b/translations/es-ES/data/reusables/sponsors/tax-form-link.md @@ -1,2 +1,2 @@ -1. Click **tax forms**. ![Enlace para llenar el formato de impuestos](/assets/images/help/sponsors/tax-form-link.png) +1. Haz clic en **formularios de impuestos**. ![Enlace para llenar el formato de impuestos](/assets/images/help/sponsors/tax-form-link.png) 2. Completa, firma y emite el formato de impuestos. diff --git a/translations/es-ES/data/reusables/ssh/key-type-support.md b/translations/es-ES/data/reusables/ssh/key-type-support.md index 30cf390f29..55fd947329 100644 --- a/translations/es-ES/data/reusables/ssh/key-type-support.md +++ b/translations/es-ES/data/reusables/ssh/key-type-support.md @@ -1,3 +1,4 @@ +{% ifversion fpt or ghec %} {% note %} **Nota:** {% data variables.product.company_short %} mejorò la seguridad al dejar los tipos de llave inseguros el 15 de marzo de 2022. @@ -7,3 +8,4 @@ Desde esta fecha, las llaves DSA (`ssh-dss`) ya no son compatibles. No puedes ag Las llaves RSA (`ssh-rsa`) con un `valid_after` anterior al 2 de noviembre de 2021 podrán continuar utilizando cualquier algoritmo de firma. Las llaves RSA que se generaron después de esta fecha deberán utilizar un algoritmo de firma de tipo SHA-2. Algunos clientes más angituos podrían necesitar actualizarse para poder utilizar firmas de tipo SHA-2. {% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/es-ES/data/reusables/user-settings/removes-personal-access-tokens.md b/translations/es-ES/data/reusables/user-settings/removes-personal-access-tokens.md index 61427e4b07..ea8d4f8ecd 100644 --- a/translations/es-ES/data/reusables/user-settings/removes-personal-access-tokens.md +++ b/translations/es-ES/data/reusables/user-settings/removes-personal-access-tokens.md @@ -1 +1 @@ -Como medida precautoria de seguridad, {% data variables.product.company_short %} elimina automáticamente los tokens de acceso personal que no se hayan utilizado en un año.{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} Para proporcionar seguridad adicional, te recomendamos ampliamente agregar un vencimiento a tus tokens de acceso personal.{% endif %} +Como medida precautoria de seguridad, {% data variables.product.company_short %} elimina automáticamente los tokens de acceso personal que no se hayan utilizado en un año.{% ifversion fpt or ghes > 3.1 or ghae or ghec %} Para proporcionar seguridad adicional, te recomendamos ampliamente agregar un vencimiento a tus tokens de acceso personal.{% endif %} diff --git a/translations/es-ES/data/reusables/webhooks/check_run_properties.md b/translations/es-ES/data/reusables/webhooks/check_run_properties.md index c4bd6cf49d..a48ac94c40 100644 --- a/translations/es-ES/data/reusables/webhooks/check_run_properties.md +++ b/translations/es-ES/data/reusables/webhooks/check_run_properties.md @@ -1,12 +1,12 @@ -| Clave | Tipo | Descripción | -| --------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada. Puede ser una de las siguientes:
  • `created` - Se creó una ejecución de verificación.
  • `completed` - El `status` de la ejecución de verificación es `completed`.
  • `rerequested` - Alguien volvió a solicitar que se volviera a ejecutar tu ejecución de verificación desde la IU de la solicitud de extracción. Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles sobre la IU de GitHub. Cuando recibes una acción de tipo `rerequested`, necesitarás [crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run). Solo la {% data variables.product.prodname_github_app %} para la cual alguien solicitó volver a ejecutar la verificación recibirá la carga útil de `rerequested`.
  • `requested_action` - Alguien volvió a solicitar que se tome una acción que proporciona tu app. Solo la {% data variables.product.prodname_github_app %} para la cual alguien solicitó llevar a cabo una acción recibirá la carga útil de `requested_action`. Para aprender más sobre las ejecuciones de verificación y las acciones solicitadas, consulta la sección "[Ejecuciones de ferificación y acciones solicitadas](/rest/reference/checks#check-runs-and-requested-actions)."
| -| `check_run` | `objeto` | La [check_run](/rest/reference/checks#get-a-check-run). | -| `check_run[status]` | `secuencia` | El estado actual de la ejecución de verificación. Puede ser `queued`, `in_progress`, o `completed`. | -| `check_run[conclusion]` | `secuencia` | El resultado de la ejecución de verificación que se completó. Puede ser una de entre `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% ifversion fpt or ghes or ghae or ghec %}`action_required` o `stale`{% else %}o `action_required`{% endif %}. Este valor será `null` hasta que la ejecución de verificación esté como `completed`. | -| `check_run[name]` | `secuencia` | El nombre de la ejecución de verificación. | -| `check_run[check_suite][id]` | `número` | La id de la suite de verificaciones de la cual es parte esta ejecución de verificación. | -| `check_run[check_suite][pull_requests]` | `arreglo` | Una matriz de solicitudes de extracción que empatan con esta suite de verificaciones. Una solicitud de cambios empata con una suite de verificaciones si tienen la misma `head_branch`.

**Nota:**
  • El `head_sha` de la suite de verificaciones puede diferir del `sha` de la solicitud de cambios si se sube información subsecuentemente a la solicitud de cambios.
  • Cuando la `head_branch` de la suite de verificación está en un repositorio bifurcado, esta será `null` y el arreglo de `pull_requests` estará vacío.
| -| `check_run[check_suite][deployment]` | `objeto` | Un despliegue a un ambiente de repositorio. Este solo se poblará si un job de flujo de trabajo de {% data variables.product.prodname_actions %} que referencia un ambiente crea la ejecución de verificación. | -| `requested_action` | `objeto` | La acción que solicitó el usuario. | -| `requested_action[identifier]` | `secuencia` | La referencia del integrador de la acción que solicitó el usuario. | +| Clave | Tipo | Descripción | +| --------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `Acción` | `secuencia` | La acción realizada. Puede ser una de las siguientes:
  • `created` - Se creó una ejecución de verificación.
  • `completed` - El `status` de la ejecución de verificación es `completed`.
  • `rerequested` - Alguien volvió a solicitar que se volviera a ejecutar tu ejecución de verificación desde la IU de la solicitud de extracción. Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles sobre la IU de GitHub. Cuando recibes una acción de tipo `rerequested`, necesitarás [crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run). Solo la {% data variables.product.prodname_github_app %} para la cual alguien solicitó volver a ejecutar la verificación recibirá la carga útil de `rerequested`.
  • `requested_action` - Alguien volvió a solicitar que se tome una acción que proporciona tu app. Solo la {% data variables.product.prodname_github_app %} para la cual alguien solicitó llevar a cabo una acción recibirá la carga útil de `requested_action`. Para aprender más sobre las ejecuciones de verificación y las acciones solicitadas, consulta la sección "[Ejecuciones de ferificación y acciones solicitadas](/rest/reference/checks#check-runs-and-requested-actions)."
| +| `check_run` | `objeto` | La [check_run](/rest/reference/checks#get-a-check-run). | +| `check_run[status]` | `secuencia` | El estado actual de la ejecución de verificación. Puede ser `queued`, `in_progress`, o `completed`. | +| `check_run[conclusion]` | `secuencia` | El resultado de la ejecución de verificación que se completó. Puede ser uno de entre `success`, `failure`, `neutral`, `cancelled`, `timed_out`, `action_required` o `stale`. Este valor será `null` hasta que la ejecución de verificación esté como `completed`. | +| `check_run[name]` | `secuencia` | El nombre de la ejecución de verificación. | +| `check_run[check_suite][id]` | `número` | La id de la suite de verificaciones de la cual es parte esta ejecución de verificación. | +| `check_run[check_suite][pull_requests]` | `arreglo` | Una matriz de solicitudes de extracción que empatan con esta suite de verificaciones. Una solicitud de cambios empata con una suite de verificaciones si tienen la misma `head_branch`.

**Nota:**
  • El `head_sha` de la suite de verificaciones puede diferir del `sha` de la solicitud de cambios si se sube información subsecuentemente a la solicitud de cambios.
  • Cuando la `head_branch` de la suite de verificación está en un repositorio bifurcado, esta será `null` y el arreglo de `pull_requests` estará vacío.
| +| `check_run[check_suite][deployment]` | `objeto` | Un despliegue a un ambiente de repositorio. Este solo se poblará si un job de flujo de trabajo de {% data variables.product.prodname_actions %} que referencia un ambiente crea la ejecución de verificación. | +| `requested_action` | `objeto` | La acción que solicitó el usuario. | +| `requested_action[identifier]` | `secuencia` | La referencia del integrador de la acción que solicitó el usuario. | diff --git a/translations/es-ES/data/reusables/webhooks/check_suite_properties.md b/translations/es-ES/data/reusables/webhooks/check_suite_properties.md index 0a427b06c8..ff27a5f4d7 100644 --- a/translations/es-ES/data/reusables/webhooks/check_suite_properties.md +++ b/translations/es-ES/data/reusables/webhooks/check_suite_properties.md @@ -1,10 +1,10 @@ -| Clave | Tipo | Descripción | -| ---------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción realizada. Puede ser:
  • `completed` - Todas las ejecuciones de verificación en una suite de verificación se completaron.
  • `requested` - Ocurre cuando se carga código nuevo al repositorio de la app. Cuando recibes un evento de acción de tipo `requested`, necesitarás [Crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run).
  • `rerequested` - Ocurre cuando alguien solicita volver a ejecutar toda la suite de verificaciones desde la IU de la solicitud de extracción. Cuando recibes los eventos de una acción de tipo `rerequested, necesitarás [crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run). Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles sobre la IU de GitHub.
| -| `check_suite` | `objeto` | La [check_suite](/rest/reference/checks#suites). | -| `check_suite[head_branch]` | `secuencia` | El nombre de la rama principal en la cual están los cambios. | -| `check_suite[head_sha]` | `secuencia` | El SHA de la confirmación más reciente para esta suite de verificaciones. | -| `check_suite[status]` | `secuencia` | El estado de resumen para todas las ejecuciones de verificación que son parte de la suite de verificaciones. Puede ser `requested`, `in_progress`, o `completed`. | -| `check_suite[conclusion]` | `secuencia` | La conclusión de resumen para todas las ejecuciones de verificación que son parte de la suite de verificaciones. Puede ser una de entre `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% ifversion fpt or ghes or ghae or ghec %}`action_required` o `stale`{% else %}o `action_required`{% endif %}. Este valor será `null` hasta que la ejecución de verificación esté como `completed`. | -| `check_suite[url]` | `secuencia` | La URL que apunta al recurso de la API de suite de verificación. | -| `check_suite[pull_requests]` | `arreglo` | Una matriz de solicitudes de extracción que empatan con esta suite de verificaciones. Una solicitud de cambios empata con una suite de verificaciones si tienen la misma `head_branch`.

**Nota:**
  • El `head_sha` de la suite de verificaciones puede diferir del `sha` de la solicitud de cambios si se sube información subsecuentemente a la solicitud de cambios.
  • Cuando la `head_branch` de la suite de verificación está en un repositorio bifurcado, esta será `null` y el arreglo de `pull_requests` estará vacío.
| +| Clave | Tipo | Descripción | +| ---------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Acción` | `secuencia` | La acción realizada. Puede ser:
  • `completed` - Todas las ejecuciones de verificación en una suite de verificación se completaron.
  • `requested` - Ocurre cuando se carga código nuevo al repositorio de la app. Cuando recibes un evento de acción de tipo `requested`, necesitarás [Crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run).
  • `rerequested` - Ocurre cuando alguien solicita volver a ejecutar toda la suite de verificaciones desde la IU de la solicitud de extracción. Cuando recibes los eventos de una acción de tipo `rerequested, necesitarás [crear una ejecución de verificación nueva](/rest/reference/checks#create-a-check-run). Consulta la sección "[Acerca de las verificaciones de estado](/articles/about-status-checks#checks)" para obtener más detalles sobre la IU de GitHub.
| +| `check_suite` | `objeto` | La [check_suite](/rest/reference/checks#suites). | +| `check_suite[head_branch]` | `secuencia` | El nombre de la rama principal en la cual están los cambios. | +| `check_suite[head_sha]` | `secuencia` | El SHA de la confirmación más reciente para esta suite de verificaciones. | +| `check_suite[status]` | `secuencia` | El estado de resumen para todas las ejecuciones de verificación que son parte de la suite de verificaciones. Puede ser `requested`, `in_progress`, o `completed`. | +| `check_suite[conclusion]` | `secuencia` | La conclusión de resumen para todas las ejecuciones de verificación que son parte de la suite de verificaciones. Puede ser uno de entre `success`, `failure`, `neutral`, `cancelled`, `timed_out`, `action_required` o `stale`. Este valor será `null` hasta que la ejecución de verificación esté como `completed`. | +| `check_suite[url]` | `secuencia` | La URL que apunta al recurso de la API de suite de verificación. | +| `check_suite[pull_requests]` | `arreglo` | Una matriz de solicitudes de extracción que empatan con esta suite de verificaciones. Una solicitud de cambios empata con una suite de verificaciones si tienen la misma `head_branch`.

**Nota:**
  • El `head_sha` de la suite de verificaciones puede diferir del `sha` de la solicitud de cambios si se sube información subsecuentemente a la solicitud de cambios.
  • Cuando la `head_branch` de la suite de verificación está en un repositorio bifurcado, esta será `null` y el arreglo de `pull_requests` estará vacío.
| diff --git a/translations/es-ES/data/reusables/webhooks/installation_properties.md b/translations/es-ES/data/reusables/webhooks/installation_properties.md index 2746802fde..391d96f55c 100644 --- a/translations/es-ES/data/reusables/webhooks/installation_properties.md +++ b/translations/es-ES/data/reusables/webhooks/installation_properties.md @@ -1,4 +1,4 @@ | Clave | Tipo | Descripción | | -------------- | ----------- | ----------------------------------------------------------------------------------- | -| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
  • `created` - Alguien instala una {% data variables.product.prodname_github_app %}.
  • `deleted` - Alguien desinstala una {% data variables.product.prodname_github_app %}
    • {% ifversion fpt or ghes or ghae or ghec %}
  • `suspend` - alguien suspende la instalación de una {% data variables.product.prodname_github_app %}.
  • `unsuspend` - Alguien deja de suspender una instalación de {% data variables.product.prodname_github_app %}.
    • {% endif %}
  • `new_permissions_accepted` - Alguien acepta permisos nuevos para una instalación de {% data variables.product.prodname_github_app %}. Cuando un propietario de una {% data variables.product.prodname_github_app %} solcita permisos nuevos, la persona que instaló dicha {% data variables.product.prodname_github_app %} debe aceptar la solicitud de estos permisos nuevos.
| +| `Acción` | `secuencia` | La acción que se realizó. Puede ser una de las siguientes:
  • `created` - Alguien instala una {% data variables.product.prodname_github_app %}.
  • `deleted` - Alguien desinstala una {% data variables.product.prodname_github_app %}
  • `suspend` - alguien suspende la instalación de una {% data variables.product.prodname_github_app %}.
  • `unsuspend` - Alguien deja de suspender una instalación de {% data variables.product.prodname_github_app %}.
  • `new_permissions_accepted` - Alguien acepta permisos nuevos para una instalación de {% data variables.product.prodname_github_app %}. Cuando un propietario de una {% data variables.product.prodname_github_app %} solcita permisos nuevos, la persona que instaló dicha {% data variables.product.prodname_github_app %} debe aceptar la solicitud de estos permisos nuevos.
| | `repositories` | `arreglo` | Un areglo de objetos de repositorio al que puede acceder la instalación. | diff --git a/translations/es-ES/data/variables/product.yml b/translations/es-ES/data/variables/product.yml index 22d26a6f0f..0aea03f916 100644 --- a/translations/es-ES/data/variables/product.yml +++ b/translations/es-ES/data/variables/product.yml @@ -140,10 +140,14 @@ prodname_advisory_database: 'GitHub Advisory Database' prodname_codeql_workflow: 'Flujo de trabajo de análisis de CodeQL' #Visual Studio prodname_vs: 'Visual Studio' +prodname_vscode_shortname: 'VS Code' prodname_vscode: 'Visual Studio Code' prodname_vss_ghe: 'Suscripciones a Visual Studio con GitHub Enterprise' prodname_vss_admin_portal_with_url: 'el [portal de admnistrador para las suscripciones de Visual Studio](https://visualstudio.microsoft.com/subscriptions-administration/)' -prodname_vscode_command_palette: 'Paleta de Comandos de VS Code' +prodname_vscode_command_palette_shortname: 'Paleta de Comandos de VS Code' +prodname_vscode_command_palette: 'Paleta de comandos de Visual Studio Code' +prodname_vscode_marketplace: 'Mercado de Visual Studio Code' +prodname_vs_marketplace_shortname: 'Mercado de VS Code' #GitHub Dependabot prodname_dependabot: 'Dependabot' prodname_dependabot_alerts: 'Las alertas del dependabot' diff --git a/translations/ja-JP/content/account-and-profile/index.md b/translations/ja-JP/content/account-and-profile/index.md index 2c63ecf2ea..9b054011ae 100644 --- a/translations/ja-JP/content/account-and-profile/index.md +++ b/translations/ja-JP/content/account-and-profile/index.md @@ -1,6 +1,6 @@ --- title: Your account and profile on GitHub -shortTitle: Account and profile +shortTitle: アカウントとプロフィール intro: 'Make {% data variables.product.product_name %} work best for you by adjusting the settings for your personal account, personalizing your profile page, and managing the notifications you receive for activity on {% data variables.product.prodname_dotcom %}.' introLinks: quickstart: /get-started/onboarding/getting-started-with-your-github-account @@ -37,7 +37,7 @@ topics: - Profiles - Notifications children: - - /setting-up-and-managing-your-github-user-account + - /setting-up-and-managing-your-personal-account-on-github - /setting-up-and-managing-your-github-profile - /managing-subscriptions-and-notifications-on-github --- diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md index 8bf7e159fe..9f48a72b7c 100644 --- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md @@ -129,8 +129,8 @@ Email notifications from {% data variables.product.product_location %} contain t | --- | --- | | `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. | | `To` field | This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} | -| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
  • `assign`: You were assigned to an issue or pull request.
  • `author`: You created an issue or pull request.
  • `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
  • `comment`: You commented on an issue or pull request.
  • `manual`: There was an update to an issue or pull request you manually subscribed to.
  • `mention`: You were mentioned on an issue or pull request.
  • `push`: Someone committed to a pull request you're subscribed to.
  • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
    • {% endif %}
  • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
  • `subscribed`: There was an update in a repository you're watching.
  • `team_mention`: A team you belong to was mentioned on an issue or pull request.
  • `your_activity`: You opened, commented on, or closed an issue or pull request.
| -| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
  • `assign`: You were assigned to an issue or pull request.
  • `author`: You created an issue or pull request.
  • `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
  • `comment`: You commented on an issue or pull request.
  • `manual`: There was an update to an issue or pull request you manually subscribed to.
  • `mention`: You were mentioned on an issue or pull request.
  • `push`: Someone committed to a pull request you're subscribed to.
  • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • {% ifversion fpt or ghes or ghae or ghec %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
    • {% endif %}
  • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
  • `subscribed`: There was an update in a repository you're watching.
  • `team_mention`: A team you belong to was mentioned on an issue or pull request.
  • `your_activity`: You opened, commented on, or closed an issue or pull request.
| +| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae or ghec %} | `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
  • `low`
  • `moderate`
  • `high`
  • `critical`
For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %} ## Choosing your notification settings @@ -139,7 +139,7 @@ Email notifications from {% data variables.product.product_location %} contain t {% data reusables.notifications-v2.manage-notifications %} 3. On the notifications settings page, choose how you receive notifications when: - There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)." - - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} + - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae or ghec %} - There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% endif %} {% ifversion fpt or ghec %} - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5668 %} - There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."{% endif %} @@ -194,7 +194,7 @@ If you are a member of more than one organization, you can configure each one to 5. Select one of your verified email addresses, then click **Save**. ![Switching your per-org email address](/assets/images/help/notifications/notifications_switching_org_email.gif) -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## {% data variables.product.prodname_dependabot_alerts %} notification options {% data reusables.notifications.vulnerable-dependency-notification-enable %} diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md index 42aacb7562..e63fea1757 100644 --- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md +++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md @@ -112,13 +112,13 @@ shortTitle: Manage from your inbox - `is:gist` - `is:issue-or-pull-request` - `is:release` -- `is:repository-invitation`{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +- `is:repository-invitation`{% ifversion fpt or ghes or ghae or ghec %} - `is:repository-vulnerability-alert`{% endif %}{% ifversion fpt or ghec %} - `is:repository-advisory`{% endif %} - `is:team-discussion`{% ifversion fpt or ghec %} - `is:discussion`{% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)." {% endif %} @@ -133,20 +133,20 @@ For information about reducing noise from notifications for {% data variables.pr 更新を受信した理由で通知をフィルタするには、`reason:` クエリを使用できます。 たとえば、自分 (または自分が所属する Team) がプルリクエストのレビューをリクエストされたときに通知を表示するには、`reason:review-requested` を使用します。 詳しい情報については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)」を参照してください。 -| クエリ | 説明 | -| ------------------------- | ----------------------------------------------------------------------------------------------------- | -| `reason:assign` | 割り当てられている Issue またはプルリクエストに更新があるとき。 | -| `reason:author` | プルリクエストまたは Issue を開くと、更新または新しいコメントがあったとき。 | -| `reason:comment` | Issue、プルリクエスト、または Team ディスカッションにコメントしたとき。 | -| `reason:participating` | Issue、プルリクエスト、Team ディスカッションについてコメントしたり、@メンションされているとき。 | -| `reason:invitation` | Team、Organization、またはリポジトリに招待されたとき。 | -| `reason:manual` | まだサブスクライブしていない Issue またはプルリクエストで [**Subscribe**] をクリックしたとき。 | -| `reason:mention` | 直接@メンションされたとき。 | -| `reason:review-requested` | 自分または参加している Team が、プルリクエストを確認するようにリクエストされているとき。{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| クエリ | 説明 | +| ------------------------- | ------------------------------------------------------------------------------------------ | +| `reason:assign` | 割り当てられている Issue またはプルリクエストに更新があるとき。 | +| `reason:author` | プルリクエストまたは Issue を開くと、更新または新しいコメントがあったとき。 | +| `reason:comment` | Issue、プルリクエスト、または Team ディスカッションにコメントしたとき。 | +| `reason:participating` | Issue、プルリクエスト、Team ディスカッションについてコメントしたり、@メンションされているとき。 | +| `reason:invitation` | Team、Organization、またはリポジトリに招待されたとき。 | +| `reason:manual` | まだサブスクライブしていない Issue またはプルリクエストで [**Subscribe**] をクリックしたとき。 | +| `reason:mention` | 直接@メンションされたとき。 | +| `reason:review-requested` | 自分または参加している Team が、プルリクエストを確認するようにリクエストされているとき。{% ifversion fpt or ghes or ghae or ghec %} | `reason:security-alert` | リポジトリに対してセキュリティアラートが発行されたとき。{% endif %} -| `reason:state-change` | プルリクエストまたは Issue の状態が変更されたとき。 たとえば、Issue がクローズされたり、プルリクエストがマージされた場合です。 | -| `reason:team-mention` | メンバーになっている Team が@メンションされたとき。 | -| `reason:ci-activity` | リポジトリに、新しいワークフロー実行ステータスなどの CI 更新があるとき。 | +| `reason:state-change` | プルリクエストまたは Issue の状態が変更されたとき。 たとえば、Issue がクローズされたり、プルリクエストがマージされた場合です。 | +| `reason:team-mention` | メンバーになっている Team が@メンションされたとき。 | +| `reason:ci-activity` | リポジトリに、新しいワークフロー実行ステータスなどの CI 更新があるとき。 | {% ifversion fpt or ghec %} ### サポートされている `author:` クエリ @@ -161,7 +161,7 @@ Organization ごとに通知をフィルタするには、`org:` クエリを使 {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## {% data variables.product.prodname_dependabot %}カスタムフィルタ {% ifversion fpt or ghec or ghes > 3.2 %} @@ -173,7 +173,7 @@ If you use {% data variables.product.prodname_dependabot %} to keep your depende {% data variables.product.prodname_dependabot %} の詳細については、「[{% data variables.product.prodname_dependabot_alerts %} について](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)」を参照してください。 {% endif %} -{% ifversion ghes < 3.3 or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae %} If you use {% data variables.product.prodname_dependabot %} to tell you about vulnerable dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}: - `is:repository_vulnerability_alert` diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md index 78f74ca3f7..c00c16fcab 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md @@ -91,10 +91,7 @@ The contribution activity section includes a detailed timeline of your work, inc ![Contribution activity time filter](/assets/images/help/profile/contributions_activity_time_filter.png) -{% ifversion fpt or ghes or ghae or ghec %} - ## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %} If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and your enterprise owner enables {% data variables.product.prodname_unified_contributions %}, you can send enterprise contribution counts from to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)." -{% endif %} diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md deleted file mode 100644 index 7c611a4533..0000000000 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md +++ /dev/null @@ -1,90 +0,0 @@ ---- -title: Permission levels for a user account repository -intro: 'A repository owned by a personal account has two permission levels: the repository owner and collaborators.' -redirect_from: - - /articles/permission-levels-for-a-user-account-repository - - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository - - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -topics: - - Accounts -shortTitle: Permission user repositories ---- -## About permissions levels for a personal account repository - -Repositories owned by personal accounts have one owner. Ownership permissions can't be shared with another personal account. - -You can also {% ifversion fpt or ghec %}invite{% else %}add{% endif %} users on {% data variables.product.product_name %} to your repository as collaborators. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)." - -{% tip %} - -**Tip:** If you require more granular access to a repository owned by your personal account, consider transferring the repository to an organization. For more information, see "[Transferring a repository](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)." - -{% endtip %} - -## Owner access for a repository owned by a personal account - -The repository owner has full control of the repository. In addition to the actions that any collaborator can perform, the repository owner can perform the following actions. - -| Action | More information | -| :- | :- | -| {% ifversion fpt or ghec %}Invite collaborators{% else %}Add collaborators{% endif %} | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" | -| Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %} -| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %} -| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" | -| Merge a pull request on a protected branch, even if there are no approving reviews | "[About protected branches](/github/administering-a-repository/about-protected-branches)" | -| Delete the repository | "[Deleting a repository](/repositories/creating-and-managing-repositories/deleting-a-repository)" | -| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %} -| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %} -| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.1 or ghec or ghae %} -| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |{% endif %} -| Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | -| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| Control access to {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies | "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %} -| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | -| Manage data use for a private repository | "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %} -| Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | -| Archive the repository | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %} -| Create security advisories | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" | -| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %} -| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | - -## Collaborator access for a repository owned by a personal account - -Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository. - -{% note %} - -**Note:** In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a personal account. - -{% endnote %} - -Collaborators can also perform the following actions. - -| Action | More information | -| :- | :- | -| Fork the repository | "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |{% ifversion fpt or ghes > 3.1 or ghae or ghec %} -| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |{% endif %} -| Create, edit, and delete comments on commits, pull requests, and issues in the repository |
  • "[About issues](/github/managing-your-work-on-github/about-issues)"
  • "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"
  • "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"
| -| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" | -| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" | -| Manage milestones for issues and pull requests in the repository | "[Creating and editing milestones for issues and pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" | -| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" | -| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" | -| Enable and disable auto-merge for a pull request | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" -| Apply suggested changes to pull requests in the repository |"[Incorporating feedback in your pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" | -| Create a pull request from a fork of the repository | "[Creating a pull request from a fork](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" | -| Submit a review on a pull request that affects the mergeability of the pull request | "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" | -| Create and edit a wiki for the repository | "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)" | -| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" | -| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %} -| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %} -| Remove themselves as collaborators on the repository | "[Removing yourself from a collaborator's repository](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" | - -## Further reading - -- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md similarity index 50% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md index 546240072c..5a437e284b 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md @@ -1,10 +1,11 @@ --- -title: Setting up and managing your GitHub user account -intro: 'You can manage settings in your GitHub personal account including email preferences, collaborator access for personal repositories, and organization memberships.' +title: Setting up and managing your personal account on GitHub +intro: 'You can manage settings for your personal account on {% data variables.product.prodname_dotcom %}, including email preferences, collaborator access for personal repositories, and organization memberships.' shortTitle: Personal accounts redirect_from: - /categories/setting-up-and-managing-your-github-user-account - /github/setting-up-and-managing-your-github-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account versions: fpt: '*' ghes: '*' @@ -13,7 +14,7 @@ versions: topics: - Accounts children: - - /managing-user-account-settings + - /managing-personal-account-settings - /managing-email-preferences - /managing-access-to-your-personal-repositories - /managing-your-membership-in-organizations diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md similarity index 81% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md index dc674934fd..5d4d1fc1da 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md @@ -6,6 +6,7 @@ redirect_from: - /categories/managing-repository-collaborators - /articles/managing-access-to-your-personal-repositories - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' @@ -19,7 +20,7 @@ children: - /inviting-collaborators-to-a-personal-repository - /removing-a-collaborator-from-a-personal-repository - /removing-yourself-from-a-collaborators-repository - - /maintaining-ownership-continuity-of-your-user-accounts-repositories + - /maintaining-ownership-continuity-of-your-personal-accounts-repositories shortTitle: Access to your repositories --- 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-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md similarity index 91% rename from 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 rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index 5729c2d51b..b08bb3b868 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-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md @@ -7,6 +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 + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' @@ -41,7 +42,7 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y {% 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) +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) {% else %} 5. 左サイドバーで [**Collaborators**] をクリックします。 ![リポジトリの [Settings] サイドバーで [Collaborators] を選択](/assets/images/help/repository/user-account-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/maintaining-ownership-continuity-of-your-user-accounts-repositories.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md similarity index 91% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md index 2ab1469e9e..73254d889d 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md @@ -1,5 +1,5 @@ --- -title: ユーザアカウントのリポジトリの所有権の継続性を管理する +title: Maintaining ownership continuity of your personal account's repositories intro: 自分が管理できない場合にユーザ所有のリポジトリを管理してもらえるように、他のユーザを招待することができます。 versions: fpt: '*' @@ -10,6 +10,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories shortTitle: Ownership continuity --- 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md similarity index 94% rename from 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 rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md index b6d25ac209..aebf85b4ba 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md @@ -10,6 +10,7 @@ redirect_from: - /articles/removing-a-collaborator-from-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md similarity index 90% rename from 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 rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md index d0b4e4d067..2137b6e8de 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md @@ -9,6 +9,7 @@ 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 + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md similarity index 91% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md index bf63417856..3b5045f83d 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -5,6 +5,7 @@ redirect_from: - /articles/adding-an-email-address-to-your-github-account - /github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md similarity index 92% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md index 83e612b0e0..ba49713732 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/blocking-command-line-pushes-that-expose-your-personal-email-address - /github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address versions: fpt: '*' ghec: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md similarity index 93% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md index e50d66dbbc..d973a0e9b0 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/changing-your-primary-email-address - /github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md similarity index 91% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md index 8f6e50b222..238723cfb1 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md @@ -5,6 +5,7 @@ redirect_from: - /categories/managing-email-preferences - /articles/managing-email-preferences - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md similarity index 93% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md index 5e2d7c4919..678add5d1c 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md @@ -5,6 +5,7 @@ redirect_from: - /articles/managing-marketing-emails-from-github - /github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github versions: fpt: '*' ghec: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md similarity index 94% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md index 7f780d61b6..540b67c3f8 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md @@ -7,6 +7,7 @@ redirect_from: - /articles/remembering-your-github-username-or-email - /github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email versions: fpt: '*' ghes: '*' @@ -72,5 +73,5 @@ origin https://{% data variables.command_line.codeblock %}/ご使用のユ {% ifversion fpt or ghec %} ## 参考リンク -- "[メールアドレスを検証する](/articles/verifying-your-email-address)" +- 「[メールアドレスを検証する](/articles/verifying-your-email-address)」 {% endif %} diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md similarity index 91% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md index 1e34d75e38..2ef7695734 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/setting-a-backup-email-address - /github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md similarity index 97% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md index 448a62a0ae..6f43efbad4 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md @@ -12,6 +12,7 @@ redirect_from: - /articles/setting-your-commit-email-address - /github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address versions: fpt: '*' ghes: '*' @@ -35,7 +36,7 @@ For web-based Git operations, you can set your commit email address on {% ifvers {% note %} -**Note**: {% data reusables.user-settings.no-verification-disposable-emails %} +**参考**:{% data reusables.user-settings.no-verification-disposable-emails %} {% endnote %} diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md similarity index 96% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md index 06e761a80b..39232fde75 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md @@ -5,6 +5,7 @@ redirect_from: - /articles/types-of-emails-github-sends - /github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends versions: fpt: '*' ghec: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md similarity index 97% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md index c0c7c3bb13..d1cde5e951 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md @@ -6,6 +6,7 @@ redirect_from: - /articles/about-your-personal-dashboard - /github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard intro: 'You can visit your personal dashboard to keep track of issues and pull requests you''re working on or following, navigate to your top repositories and team pages, stay updated on recent activities in organizations and repositories you''re subscribed to, and explore recommended repositories.' versions: fpt: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md similarity index 95% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md index 655725480a..61baae437b 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md @@ -5,6 +5,7 @@ redirect_from: - /articles/best-practices-for-leaving-your-company - /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company versions: fpt: '*' ghec: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md similarity index 88% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md index 9245742ce0..42aefd06a9 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md @@ -9,6 +9,7 @@ redirect_from: - /articles/changing-your-github-username - /github/setting-up-and-managing-your-github-user-account/changing-your-github-username - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username versions: fpt: '*' ghes: '*' @@ -76,10 +77,10 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.account_settings %} -3. [Change username] セクションで [**Change username**] をクリックします。 ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %} -4. ユーザ名を変更することに関する警告を読みます。 ユーザ名を変更したい場合は、[**I understand, let's change my username**] をクリックします。 ![[Change Username] 警告ボタン](/assets/images/help/settings/settings-change-username-warning-button.png) +3. In the "Change username" section, click **Change username**. ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %} +4. ユーザ名を変更することに関する警告を読みます。 If you still want to change your username, click **I understand, let's change my username**. ![[Change Username] 警告ボタン](/assets/images/help/settings/settings-change-username-warning-button.png) 5. 新しいユーザ名を入力します。 ![新しいユーザ名のフィールド](/assets/images/help/settings/settings-change-username-enter-new-username.png) -6. 選択したユーザ名が利用できる場合、[**Change my username**] をクリックします。 選択したユーザ名が利用できない場合、別のユーザ名を入力するか、提案されたユーザ名を利用できます。 ![[Change Username] 警告ボタン](/assets/images/help/settings/settings-change-my-username-button.png) +6. If the username you've chosen is available, click **Change my username**. 選択したユーザ名が利用できない場合、別のユーザ名を入力するか、提案されたユーザ名を利用できます。 ![[Change Username] 警告ボタン](/assets/images/help/settings/settings-change-my-username-button.png) {% endif %} ## 参考リンク diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md similarity index 97% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md index 8c45a8cc51..339f4cbc9d 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md @@ -6,6 +6,7 @@ redirect_from: - /articles/converting-a-user-into-an-organization - /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization intro: You can convert your personal account into an organization. これにより、Organization に属するリポジトリに対して、より細かく権限を設定できます。 versions: fpt: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md similarity index 96% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md index ae4cadf0d2..cc6d495b49 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md @@ -1,11 +1,12 @@ --- -title: 自分のユーザアカウントの削除 +title: Deleting your personal account intro: 'You can delete your personal account on {% data variables.product.product_name %} at any time.' redirect_from: - /articles/deleting-a-user-account - /articles/deleting-your-user-account - /github/setting-up-and-managing-your-github-user-account/deleting-your-user-account - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md similarity index 68% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md index d69801c11d..a2d3ec2c4e 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md @@ -6,6 +6,7 @@ redirect_from: - /categories/user-accounts - /articles/managing-user-account-settings - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings versions: fpt: '*' ghes: '*' @@ -18,15 +19,15 @@ children: - /managing-your-theme-settings - /managing-your-tab-size-rendering-preference - /changing-your-github-username - - /merging-multiple-user-accounts + - /merging-multiple-personal-accounts - /converting-a-user-into-an-organization - - /deleting-your-user-account - - /permission-levels-for-a-user-account-repository - - /permission-levels-for-user-owned-project-boards + - /deleting-your-personal-account + - /permission-levels-for-a-personal-account-repository + - /permission-levels-for-a-project-board-owned-by-a-personal-account - /managing-accessibility-settings - /managing-the-default-branch-name-for-your-repositories - - /managing-security-and-analysis-settings-for-your-user-account - - /managing-access-to-your-user-accounts-project-boards + - /managing-security-and-analysis-settings-for-your-personal-account + - /managing-access-to-your-personal-accounts-project-boards - /integrating-jira-with-your-personal-projects - /best-practices-for-leaving-your-company - /what-does-the-available-for-hire-checkbox-do 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-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md similarity index 92% rename from 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 rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md index 58eaa978e6..ef0a354036 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-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md @@ -5,6 +5,7 @@ redirect_from: - /articles/integrating-jira-with-your-personal-projects - /github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects versions: ghes: '*' ghae: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md similarity index 92% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md index f3cea6bf7e..3bc4be6736 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md @@ -1,5 +1,5 @@ --- -title: ユーザ アカウントのプロジェクトボードに対するアクセスを管理する +title: Managing access to your personal account's project boards intro: プロジェクトボードのオーナーは、コラボレーターを追加または削除して、そのプロジェクトボードに対する権限をカスタマイズすることができます。 redirect_from: - /articles/managing-project-boards-in-your-repository-or-organization @@ -7,6 +7,7 @@ redirect_from: - /articles/managing-access-to-your-user-accounts-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md similarity index 89% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md index adfabb003a..72c2a7feb7 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md @@ -3,6 +3,8 @@ title: Managing accessibility settings intro: 'You can disable character key shortcuts on {% data variables.product.prodname_dotcom %} in your accessibility settings.' versions: feature: keyboard-shortcut-accessibility-setting +redirect_from: + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings --- ## About accessibility settings diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md similarity index 95% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md index 9a5856fa81..4972c68d6a 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md @@ -1,5 +1,5 @@ --- -title: ユーザアカウントのセキュリティと分析設定を管理する +title: Managing security and analysis settings for your personal account intro: '{% data variables.product.prodname_dotcom %} 上のプロジェクトのコードをセキュリティ保護し分析する機能を管理できます。' versions: fpt: '*' @@ -10,6 +10,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account shortTitle: セキュリティと分析の管理 --- diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md similarity index 100% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md 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-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md similarity index 82% rename from 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 rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md index 91f4859490..9ac320db89 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-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md @@ -9,6 +9,8 @@ versions: topics: - Accounts shortTitle: Managing your tab size +redirect_from: + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference --- 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. 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-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md similarity index 68% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md index b862302ca9..0fae15d3c0 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-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md @@ -11,6 +11,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings shortTitle: Manage theme settings --- @@ -18,7 +19,7 @@ shortTitle: Manage theme settings You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes. +{% ifversion fpt or ghes > 3.2 or ghae or ghec %}If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% endif %}{% ifversion fpt or ghae or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes. {% endif %} @@ -31,10 +32,10 @@ You may want to use a dark theme to reduce power consumption on certain devices, 1. 使いたいテーマをクリックしてください。 - If you chose a single theme, click a theme. - {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} + {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} - If you chose to follow your system settings, click a day theme and a night theme. - {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} + {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} {% ifversion fpt or ghec %} - If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %} diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md similarity index 77% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md index 66cfec5983..2a406483de 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md @@ -1,5 +1,5 @@ --- -title: 複数のユーザアカウントをマージする +title: Merging multiple personal accounts intro: 業務用と個人用に別々のアカウントを持っている場合は、アカウントをマージできます。 redirect_from: - /articles/can-i-merge-two-accounts @@ -7,6 +7,7 @@ redirect_from: - /articles/merging-multiple-user-accounts - /github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts versions: fpt: '*' ghec: '*' @@ -19,7 +20,7 @@ shortTitle: Merge multiple personal accounts {% ifversion ghec %} -**Tip:** {% data variables.product.prodname_emus %} allow an enterprise to provision unique personal accounts for its members through an identity provider (IdP). For more information, see "[About Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)." For other use cases, we recommend using only one personal account to manage both personal and professional repositories. +**Tip:** {% data variables.product.prodname_emus %} allow an enterprise to provision unique personal accounts for its members through an identity provider (IdP). 詳しい情報については「[Enterpriseが管理しているユーザ](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)」を参照してください。 For other use cases, we recommend using only one personal account to manage both personal and professional repositories. {% else %} @@ -39,7 +40,7 @@ shortTitle: Merge multiple personal accounts 1. 削除するアカウントから、残しておくアカウントに[リポジトリを委譲](/articles/how-to-transfer-a-repository)します。 Issue、プルリクエスト、ウィキも移譲されます。 リポジトリが、残しておくアカウントに存在することを確認します。 2. 移動したリポジトリにクローンがある場合は、その[リモート URL を更新](/github/getting-started-with-github/managing-remote-repositories) します。 -3. 使わなくなる[アカウントを削除](/articles/deleting-your-user-account)します。 +3. 使わなくなる[アカウントを削除](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account)します。 4. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. 詳細は「[コントリビューションがプロフィールに表示されないのはなぜですか？](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)」を参照してください。 ## 参考リンク diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md similarity index 97% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md index 7c611a4533..1e02205d74 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md @@ -1,10 +1,11 @@ --- -title: Permission levels for a user account repository +title: Permission levels for a personal account repository intro: 'A repository owned by a personal account has two permission levels: the repository owner and collaborators.' redirect_from: - /articles/permission-levels-for-a-user-account-repository - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository versions: fpt: '*' ghes: '*' @@ -12,7 +13,7 @@ versions: ghec: '*' topics: - Accounts -shortTitle: Permission user repositories +shortTitle: Repository permissions --- ## About permissions levels for a personal account repository @@ -43,7 +44,7 @@ The repository owner has full control of the repository. In addition to the acti | Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}{% ifversion fpt or ghes > 3.1 or ghec or ghae %} | Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |{% endif %} | Customize the repository's social media preview | "[Customizing your repository's social media preview](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | -| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| Create a template from the repository | "[Creating a template repository](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae or ghec %} | Control access to {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies | "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %} | Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | | Manage data use for a private repository | "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %} diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md similarity index 93% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md index bc0cb85e08..1d6ff1ee83 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md @@ -1,10 +1,11 @@ --- -title: ユーザー所有のプロジェクトボードの権限レベル +title: Permission levels for a project board owned by a personal account intro: 'A project board owned by a personal account has two permission levels: the project board owner and collaborators.' redirect_from: - /articles/permission-levels-for-user-owned-project-boards - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards versions: fpt: '*' ghes: '*' @@ -12,7 +13,7 @@ versions: ghec: '*' topics: - Accounts -shortTitle: Permission user project boards +shortTitle: プロジェクトボードの権限 --- ## 権限の概要 diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md similarity index 91% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md index 5af7a6a973..c3ce373234 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md @@ -5,6 +5,7 @@ redirect_from: - /articles/what-does-the-available-for-hire-checkbox-do - /github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do versions: fpt: '*' ghec: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md similarity index 96% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md index 4b8e934071..808ac8262a 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md @@ -5,6 +5,7 @@ redirect_from: - /articles/about-organization-membership - /github/setting-up-and-managing-your-github-user-account/about-organization-membership - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md similarity index 86% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md index 7f341ba402..b23d3eedfe 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md @@ -8,6 +8,7 @@ redirect_from: - /articles/accessing-an-organization - /github/setting-up-and-managing-your-github-user-account/accessing-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md similarity index 88% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md index ebb5c89be5..69a61a0438 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md @@ -4,6 +4,7 @@ intro: Organization のメンバーは、メンバーシップの公開/非公 redirect_from: - /articles/managing-your-membership-in-organizations - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations versions: fpt: '*' ghes: '*' 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-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md similarity index 97% rename from 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 rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md index 5859e8beb5..789ebf2bd0 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-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md @@ -9,6 +9,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders shortTitle: スケジュールされたリマインダーの管理 --- diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md similarity index 91% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md index 51a469f6c8..46f714fcf0 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md @@ -6,6 +6,7 @@ redirect_from: - /articles/publicizing-or-hiding-organization-membership - /github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md similarity index 92% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md index 29f93bd492..552110f101 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md @@ -6,6 +6,7 @@ redirect_from: - /articles/removing-yourself-from-an-organization - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md similarity index 92% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md index c399834945..9da62d3021 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md @@ -7,6 +7,7 @@ redirect_from: - /articles/requesting-organization-approval-for-oauth-apps - /github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps versions: fpt: '*' ghec: '*' diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md similarity index 97% rename from translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md rename to translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md index 3ab2e1c147..8497463603 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md @@ -7,6 +7,7 @@ redirect_from: - /articles/viewing-peoples-roles-in-an-organization - /github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization versions: fpt: '*' ghes: '*' diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md deleted file mode 100644 index e22a423999..0000000000 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Building and testing Node.js or Python -shortTitle: Build & test Node.js or Python -intro: You can create a continuous integration (CI) workflow to build and test your project. Use the language selector to show examples for your language of choice. -redirect_from: - - /actions/guides/building-and-testing-nodejs-or-python -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: tutorial -topics: - - CI ---- - - - diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index 4ac3ef0254..fd211de0ca 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -11,13 +11,11 @@ versions: ghae: '*' ghec: '*' type: tutorial -hidden: true topics: - CI - Node - JavaScript shortTitle: Build & test Node.js -hasExperimentalAlternative: true --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md index d106d62269..726763a5ae 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -11,12 +11,10 @@ versions: ghae: '*' ghec: '*' type: tutorial -hidden: true topics: - CI - Python shortTitle: Build & test Python -hasExperimentalAlternative: true --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/index.md b/translations/ja-JP/content/actions/automating-builds-and-tests/index.md index 7a40d05f77..9eac55efbe 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/index.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/index.md @@ -14,13 +14,14 @@ redirect_from: - /actions/language-and-framework-guides/github-actions-for-java - /actions/language-and-framework-guides/github-actions-for-javascript-and-typescript - /actions/language-and-framework-guides/github-actions-for-python + - /actions/guides/building-and-testing-nodejs-or-python + - /actions/automating-builds-and-tests/building-and-testing-nodejs-or-python children: - /about-continuous-integration - /building-and-testing-java-with-ant - /building-and-testing-java-with-gradle - /building-and-testing-java-with-maven - /building-and-testing-net - - /building-and-testing-nodejs-or-python - /building-and-testing-nodejs - /building-and-testing-powershell - /building-and-testing-python 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 ffd131d0b3..33e887c14b 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 @@ -223,7 +223,7 @@ runs: ### `runs.steps` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Required** The steps that you plan to run in this action. These can be either `run` steps or `uses` steps. {% else %} **Required** The steps that you plan to run in this action. @@ -231,7 +231,7 @@ runs: #### `runs.steps[*].run` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Optional** The command you want to run. これは、インラインでも、アクションリポジトリ内のスクリプトでもかまいません。 {% else %} **必須** 実行するコマンド。 これは、インラインでも、アクションリポジトリ内のスクリプトでもかまいません。 @@ -261,7 +261,7 @@ runs: #### `runs.steps[*].shell` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Optional** The shell where you want to run the command. [こちら](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)にリストされている任意のシェルを使用できます。 Required if `run` is set. {% else %} **必須** コマンドを実行するシェル。 [こちら](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)にリストされている任意のシェルを使用できます。 Required if `run` is set. @@ -314,7 +314,7 @@ steps: **オプション** コマンドを実行する作業ディレクトリを指定します。 -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} #### `runs.steps[*].uses` **Optional** Selects an action to run as part of a step in your job. アクションとは、再利用可能なコードの単位です。 ワークフロー、パブリックリポジトリ、または[公開されているDockerコンテナイメージ](https://hub.docker.com/)と同じリポジトリで定義されているアクションを使用できます。 diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md index 09883bc82e..92e3bd365c 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md @@ -134,4 +134,4 @@ jobs: * オリジナルのスターターワークフローについては、{% data variables.product.prodname_actions %} `starter-workflows`リポジトリ中の[`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml)を参照してください。 * Webアプリケーションのデプロイに使われたアクションは、公式のAzure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy)アクションです。 * For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository. -* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using VS Code with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice). +* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using {% data variables.product.prodname_vscode %} with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice). 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 c1e1ea2515..3c82ac9aa4 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 @@ -69,7 +69,7 @@ You can use any machine as a self-hosted runner as long at it meets these requir * 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. -{% ifversion fpt or ghes > 3.2 or ghec or ghae-issue-4462 %} +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## Autoscaling your self-hosted runners You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." 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 502e37383f..143e04db79 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 @@ -5,7 +5,7 @@ versions: fpt: '*' ghec: '*' ghes: '>3.2' - ghae: issue-4462 + ghae: '*' type: overview --- diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md index a4681f72fc..fbaa74f98f 100644 --- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -208,7 +208,8 @@ Travis CI から移行する場合は、{% data variables.product.prodname_actio ### {% data variables.product.prodname_actions %} で様々な言語を使用する {% data variables.product.prodname_actions %} でさまざまな言語を使用する場合、ジョブにステップを作成して言語の依存関係を設定できます。 特定の言語での作業の詳細については、それぞれのガイドを参照してください。 - - [Building and testing Node.js or Python](/actions/guides/building-and-testing-nodejs-or-python) + - [Node.js のビルドとテスト](/actions/guides/building-and-testing-nodejs) + - [Python のビルドとテスト](/actions/guides/building-and-testing-python) - [PowerShell のビルドとテスト](/actions/guides/building-and-testing-powershell) - [MavenでのJavaのビルドとテスト](/actions/guides/building-and-testing-java-with-maven) - [GradleでのJavaのビルドとテスト](/actions/guides/building-and-testing-java-with-gradle) 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 bd26e07b04..a26c9bd195 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 @@ -24,7 +24,7 @@ Workflow triggers are events that cause a workflow to run. For more information Some events have multiple activity types. For these events, you can specify which activity types will trigger a workflow run. For more information about what each activity type means, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)." Note that not all webhook events trigger workflows. -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4968 %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae %} ### `branch_protection_rule` | webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | @@ -1051,7 +1051,7 @@ on: {% endnote %} -Runs your workflow when release activity in your repository occurs. For information about the release APIs, see "[Release](/graphql/reference/objects#release)" in the GraphQL API documentation or "[Releases](/rest/reference/repos#releases)" in the REST API documentation. +Runs your workflow when release activity in your repository occurs. For information about the release APIs, see "[Release](/graphql/reference/objects#release)" in the GraphQL API documentation or "[Releases](/rest/reference/releases)" in the REST API documentation. たとえば、リリースが `published` だったときにワークフローを実行する例は、次のとおりです。 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 4657d2edc3..83f9e9745c 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 @@ -99,18 +99,18 @@ core.setOutput('SELECTED_COLOR', 'green'); 以下の表は、ワークフロー内で使えるツールキット関数を示しています。 -| ツールキット関数 | 等価なワークフローのコマンド | -| --------------------- | --------------------------------------------------------------------- | -| `core.addPath` | Accessible using environment file `GITHUB_PATH` | -| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +| ツールキット関数 | 等価なワークフローのコマンド | +| --------------------- | ---------------------------------------------------------- | +| `core.addPath` | Accessible using environment file `GITHUB_PATH` | +| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `core.notice` | `notice` {% endif %} -| `core.error` | `error` | -| `core.endGroup` | `endgroup` | -| `core.exportVariable` | Accessible using environment file `GITHUB_ENV` | -| `core.getInput` | 環境変数の`INPUT_{NAME}`を使ってアクセス可能 | -| `core.getState` | 環境変数の`STATE_{NAME}`を使ってアクセス可能 | -| `core.isDebug` | 環境変数の`RUNNER_DEBUG`を使ってアクセス可能 | +| `core.error` | `error` | +| `core.endGroup` | `endgroup` | +| `core.exportVariable` | Accessible using environment file `GITHUB_ENV` | +| `core.getInput` | 環境変数の`INPUT_{NAME}`を使ってアクセス可能 | +| `core.getState` | 環境変数の`STATE_{NAME}`を使ってアクセス可能 | +| `core.isDebug` | 環境変数の`RUNNER_DEBUG`を使ってアクセス可能 | {%- if actions-job-summaries %} | `core.summary` | Accessible using environment variable `GITHUB_STEP_SUMMARY` | {%- endif %} @@ -170,7 +170,7 @@ Write-Output "::debug::Set the Octocat variable" {% endpowershell %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ## Setting a notice message diff --git a/translations/ja-JP/content/admin/code-security/index.md b/translations/ja-JP/content/admin/code-security/index.md index ae196fb959..970c4013fb 100644 --- a/translations/ja-JP/content/admin/code-security/index.md +++ b/translations/ja-JP/content/admin/code-security/index.md @@ -1,11 +1,11 @@ --- title: Managing code security for your enterprise shortTitle: Manage code security -intro: "You can build security into your developers' workflow with features that keep secrets and vulnerabilities out of your codebase, and that maintain your software supply chain." +intro: 'You can build security into your developers'' workflow with features that keep secrets and vulnerabilities out of your codebase, and that maintain your software supply chain.' versions: ghes: '*' ghec: '*' - ghae: issue-4864 + ghae: '*' topics: - Enterprise children: diff --git a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md index 55f6a3e42e..83eaa9f805 100644 --- a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md @@ -1,11 +1,11 @@ --- title: About supply chain security for your enterprise intro: You can enable features that help your developers understand and update the dependencies their code relies on. -shortTitle: About supply chain security +shortTitle: サプライチェーンのセキュリティについて permissions: '' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise diff --git a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md index 4373e5a5e5..d117312656 100644 --- a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md @@ -4,7 +4,7 @@ shortTitle: サプライチェーンのセキュリティ intro: 'You can visualize, maintain, and secure the dependencies in your developers'' software supply chain.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' topics: - Enterprise children: diff --git a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md index 11620acda6..dbd92d70c4 100644 --- a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md @@ -5,7 +5,7 @@ shortTitle: View vulnerability data permissions: 'Site administrators can view vulnerability data on {% data variables.product.product_location %}.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md index 082bd40e29..54d17c56d4 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -10,9 +10,9 @@ topics: - GitHub Connect --- -## {% data variables.product.prodname_github_connect %} について +## About {% data variables.product.prodname_github_connect %} -{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae-issue-4864 %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}. +{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}. {% data variables.product.prodname_github_connect %} does not open {% data variables.product.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)." @@ -26,22 +26,22 @@ After enabling {% data variables.product.prodname_github_connect %}, you will be After you configure the connection between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %} for your enterprise. -| 機能 | 説明 | 詳細情報 | -| ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %} -| Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae-issue-4864 %} -| {% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} -| {% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% if server-statistics %} -| {% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} -| Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.product.product_location %}. | "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" | -| Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.product.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.product.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" | +Feature | Description | More information | +------- | ----------- | ---------------- |{% ifversion ghes %} +Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} +{% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} +{% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% if server-statistics %} +{% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} +Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.product.product_location %}. | "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" +Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.product.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.product.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" -## Data transmission for {% data variables.product.prodname_github_connect %} +## Data transmission for {% data variables.product.prodname_github_connect %} When you enable {% data variables.product.prodname_github_connect %} or specific {% data variables.product.prodname_github_connect %} features, a record on {% data variables.product.prodname_ghe_cloud %} stores the following information about the connection. {% ifversion ghes %} -- {% data variables.product.prodname_ghe_server %} ライセンスの公開鍵の部分 -- {% data variables.product.prodname_ghe_server %} ライセンスのハッシュ -- {% data variables.product.prodname_ghe_server %} ライセンスの顧客名 +- The public key portion of your {% data variables.product.prodname_ghe_server %} license +- A hash of your {% data variables.product.prodname_ghe_server %} license +- The customer name on your {% data variables.product.prodname_ghe_server %} license - The version of {% data variables.product.product_location_enterprise %}{% endif %} - The hostname of {% data variables.product.product_location %} - The organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} that's connected to {% data variables.product.product_location %} @@ -62,16 +62,16 @@ When you enable {% data variables.product.prodname_github_connect %} or specific Additional data is transmitted if you enable individual features of {% data variables.product.prodname_github_connect %}. -| 機能 | Data | Which way does the data flow? | Where is the data used? | -| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |{% ifversion ghes %} -| Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %} -| {% data variables.product.prodname_dependabot_alerts %} | Vulnerability alerts | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %} -| {% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository

If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} -| {% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% if server-statistics %} -| {% data variables.product.prodname_server_statistics %} | Aggregate {% data variables.product.prodname_ghe_server %} usage metrics
For the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %} -| Unified search | Search terms, search results | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} -| Unified contributions | Contribution counts | From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} +Feature | Data | Which way does the data flow? | Where is the data used? | +------- | ---- | --------- | ------ |{% ifversion ghes %} +Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %} +{% data variables.product.prodname_dependabot_alerts %} | Vulnerability alerts | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %} +{% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository

If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} +{% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% if server-statistics %} +{% data variables.product.prodname_server_statistics %} | Aggregate {% data variables.product.prodname_ghe_server %} usage metrics
For the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %} +Unified search | Search terms, search results | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} | +Unified contributions | Contribution counts | From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} | -## 参考リンク +## Further reading - "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md index 2fe23408f4..0b56b43237 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -15,7 +15,7 @@ redirect_from: permissions: 'Enterprise owners can enable {% data variables.product.prodname_dependabot %}.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise 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 bbd29e52aa..3335f4cc4d 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 @@ -673,6 +673,12 @@ This utility manually repackages a repository network to optimize pack storage. You can add the optional `--prune` argument to remove unreachable Git objects that aren't referenced from a branch, tag, or any other ref. This is particularly useful for immediately removing [previously expunged sensitive information](/enterprise/user/articles/remove-sensitive-data/). +{% warning %} + +**Warning**: Before using the `--prune` argument to remove unreachable Git objects, put {% data variables.product.product_location %} into maintenance mode, or ensure the repository is offline. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)." + +{% endwarning %} + ```shell ghe-repo-gc username/reponame ``` diff --git a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md index 1a1088e00d..a5666382bf 100644 --- a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md +++ b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md @@ -33,12 +33,13 @@ Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will ins ## Configuring a repository cache -1. During the beta, you must enable the feature flag for repository caching on your primary {% data variables.product.prodname_ghe_server %} appliance. +{% ifversion ghes = 3.3 %} +1. On your primary {% data variables.product.prodname_ghe_server %} appliance, enable the feature flag for repository caching. ``` $ ghe-config cluster.cache-enabled true ``` - +{%- endif %} 1. 新しい {% data variables.product.prodname_ghe_server %} アプライアンスを希望するプラットフォームにセットアップします。 This appliance will be your repository cache. 詳細は「[{% data variables.product.prodname_ghe_server %}インスタンスをセットアップする](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。 {% data reusables.enterprise_installation.replica-steps %} 1. Connect to the repository cache's IP address using SSH. @@ -46,7 +47,13 @@ Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will ins ```shell $ ssh -p 122 admin@REPLICA IP ``` +{%- ifversion ghes = 3.3 %} +1. On your cache replica, enable the feature flag for repository caching. + ``` + $ ghe-config cluster.cache-enabled true + ``` +{%- endif %} {% data reusables.enterprise_installation.generate-replication-key-pair %} {% data reusables.enterprise_installation.add-ssh-key-to-primary %} 1. To verify the connection to the primary and enable replica mode for the repository cache, run `ghe-repl-setup` again. diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index 97e1185a51..fe6eedf9c6 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -32,7 +32,7 @@ This guide shows you how to apply a centralized management approach to self-host 1. Deploy a self-hosted runner for your enterprise 1. Create a group to manage access to the runners available to your enterprise 1. Optionally, further restrict the repositories that can use the runner -{%- ifversion ghec or ghae-issue-4462 or ghes > 3.2 %} +{%- ifversion ghec or ghae or ghes > 3.2 %} 1. Optionally, build custom tooling to automatically scale your self-hosted runners {% endif %} @@ -122,7 +122,7 @@ Optionally, organization owners can further restrict the access policy of the ru 詳しい情報については、「[グループを使用したセルフホストランナーへのアクセスの管理](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。 -{% ifversion ghec or ghae-issue-4462 or ghes > 3.2 %} +{% ifversion ghec or ghae or ghes > 3.2 %} ## 5. Automatically scale your self-hosted runners diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index f539aeca8d..7ea2bb0b09 100644 --- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -46,7 +46,7 @@ Before enabling access to all actions from {% data variables.product.prodname_do ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) 1. {% data reusables.actions.enterprise-limit-actions-use %} -{% ifversion ghes > 3.2 or ghae-issue-4815 %} +{% ifversion ghes > 3.2 or ghae %} ## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md index 1af5a98dfd..3f5f872968 100644 --- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md +++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md @@ -33,7 +33,7 @@ If your machine has access to both systems at the same time, you can do the sync The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories. -{% ifversion ghes > 3.2 or ghae-issue-4815 %} +{% ifversion ghes > 3.2 or ghae %} {% note %} **Note:** The `actions-sync` tool is intended for use in systems where {% data variables.product.prodname_github_connect %} is not enabled. If you run the tool on a system with {% data variables.product.prodname_github_connect %} enabled, you may see the error `The repository has been retired and cannot be reused`. This indicates that a workflow has used that action directly on {% data variables.product.prodname_dotcom_the_website %} and the namespace is retired on {% data variables.product.product_location %}. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index 97e81a3546..5d4d770631 100644 --- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -47,7 +47,7 @@ Once {% data variables.product.prodname_github_connect %} is configured, you can 1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`. 1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}. - {% ifversion ghes > 3.2 or ghae-issue-4815 %} + {% ifversion ghes > 3.2 or ghae %} {% note %} **Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.product.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index 6dbde9bee4..666c95f14a 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -188,7 +188,7 @@ topics: | `config_entry.update` | A configuration setting was edited. These events are only visible in the site admin audit log. The type of events recorded relate to:
- Enterprise settings and policies
- Organization and repository permissions and settings
- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings. | {%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} ### `dependabot_alerts` カテゴリアクション | アクション | 説明 | @@ -226,7 +226,7 @@ topics: | `dependabot_security_updates_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. | {%- endif %} -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} ### `dependency_graph` カテゴリアクション | アクション | 説明 | @@ -620,7 +620,7 @@ topics: {%- ifversion fpt or ghec %} | `org.oauth_app_access_approved` | An owner [granted organization access to an {% data variables.product.prodname_oauth_app %}](/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization). | `org.oauth_app_access_denied` | An owner [disabled a previously approved {% data variables.product.prodname_oauth_app %}'s access](/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to an organization. | `org.oauth_app_access_requested` | An organization member requested that an owner grant an {% data variables.product.prodname_oauth_app %} access to an organization. {%- endif %} -| `org.recreate` | An organization was restored. | `org.register_self_hosted_runner` | A new self-hosted runner was registered. 詳しい情報については、「[Organization へのセルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)」を参照してください。 | `org.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was removed. | `org.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was removed from an organization. | `org.remove_billing_manager` | An owner removed a billing manager from an organization. |{% ifversion fpt or ghec %}For more information, see "[Removing a billing manager from your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization)"{% endif %}{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and a billing manager didn't use 2FA or disabled 2FA.{% endif %}| | `org.remove_member` | An [owner removed a member from an organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disabled 2FA{% endif %}. Also an [organization member removed themselves](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization) from an organization. | `org.remove_outside_collaborator` | An owner removed an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an outside collaborator didn't use 2FA or disabled 2FA{% endif %}. | `org.remove_self_hosted_runner` | A self-hosted runner was removed. 詳しい情報については、「[Organization からランナーを削除する](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)」を参照してください。 | `org.rename` | An organization was renamed. | `org.restore_member` | An organization member was restored. For more information, see "[Reinstating a former member of your organization](/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization)." +| `org.recreate` | An organization was restored. | `org.register_self_hosted_runner` | A new self-hosted runner was registered. 詳しい情報については、「[Organization へのセルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)」を参照してください。 | `org.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was removed. | `org.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was removed from an organization. | `org.remove_billing_manager` | An owner removed a billing manager from an organization. |{% ifversion fpt or ghec %}For more information, see "[Removing a billing manager from your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization)"{% endif %}{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and a billing manager didn't use 2FA or disabled 2FA.{% endif %}| | `org.remove_member` | An [owner removed a member from an organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disabled 2FA{% endif %}. Also an [organization member removed themselves](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization) from an organization. | `org.remove_outside_collaborator` | An owner removed an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an outside collaborator didn't use 2FA or disabled 2FA{% endif %}. | `org.remove_self_hosted_runner` | A self-hosted runner was removed. 詳しい情報については、「[Organization からランナーを削除する](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)」を参照してください。 | `org.rename` | An organization was renamed. | `org.restore_member` | An organization member was restored. For more information, see "[Reinstating a former member of your organization](/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization)." {%- ifversion ghec %} | `org.revoke_external_identity` | An organization owner revoked a member's linked identity. 詳細は、「[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)」を参照してください。 | `org.revoke_sso_session` | An organization owner revoked a member's SAML session. 詳細は、「[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 %} @@ -862,7 +862,7 @@ topics: | ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `pull_request.close` | A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." | | `pull_request.converted_to_draft` | A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)." | -| `pull_request.create` | A pull request was created. For more information, see "[Creating a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." | +| `pull_request.create` | A pull request was created. 詳しい情報については[プルリクエストの作成](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)を参照してください。 | | `pull_request.create_review_request` | A review was requested on a pull request. 詳しい情報については、「[プルリクエストレビューについて](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)」を参照してください。 | | `pull_request.in_progress` | A pull request was marked as in progress. | | `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch. | @@ -1014,7 +1014,7 @@ topics: | `repository_visibility_change.disable` | The ability for enterprise members to update a repository's visibility was disabled. Members are unable to change repository visibilities in an organization, or all organizations in an enterprise. | | `repository_visibility_change.enable` | The ability for enterprise members to update a repository's visibility was enabled. Members are able to change repository visibilities in an organization, or all organizations in an enterprise. | -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} ### `repository_vulnerability_alert` カテゴリアクション | アクション | 説明 | 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 12de91d23e..356faf8cfb 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 @@ -66,7 +66,7 @@ Enterprise 内のすべての Organization に対して {% data variables.produc 1. "Policies（ポリシー）"の下で、{% data reusables.actions.policy-label-for-select-actions-workflows %}を選択し、必要なアクション{% if actions-workflow-policy %}と再利用可能なワークフロー{% endif %}をリストに追加してください。 {% if actions-workflow-policy %} ![許可リストへのアクションと再利用可能なワークフローの追加](/assets/images/help/organizations/enterprise-actions-policy-allow-list-with-workflows.png) - {%- elsif ghes or ghae-issue-5094 %} + {%- elsif ghes or ghae %} ![許可リストへのアクションの追加](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) {%- elsif ghae %} ![許可リストへのアクションの追加](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) @@ -134,13 +134,13 @@ By default, when you create a new enterprise, `GITHUB_TOKEN` only has read acces {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. +1. [Workflow permissions]の下で、`GITHUB_TOKEN`にすべてのスコープに対する読み書きアクセスを持たせたいか、あるいは`contents`スコープに対する読み取りアクセスだけを持たせたいかを選択してください。 ![Set GITHUB_TOKEN permissions for this enterprise](/assets/images/help/settings/actions-workflow-permissions-enterprise{% if allow-actions-to-approve-pr-with-ent-repo %}-with-pr-approval{% endif %}.png) 1. **Save（保存）**をクリックして、設定を適用してください。 {% if allow-actions-to-approve-pr-with-ent-repo %} -### Preventing {% data variables.product.prodname_actions %} from creating or approving pull requests +### {% data variables.product.prodname_actions %}がPull Requestの作成もしくは承認をできないようにする {% data reusables.actions.workflow-pr-approval-permissions-intro %} diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md index 6385db0b13..d756500616 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md @@ -68,7 +68,15 @@ You can view more information about the person's access to your enterprise, such {% ifversion ghec %} ## Viewing pending invitations -You can see all the pending invitations to become administrators, members, or outside collaborators in your enterprise. You can filter the list in useful ways, such as by organization. ユーザ名または表示名を検索して、特定の人を見つけることが可能です。 +You can see all the pending invitations to become members, administrators, or outside collaborators in your enterprise. You can filter the list in useful ways, such as by organization. ユーザ名または表示名を検索して、特定の人を見つけることが可能です。 + +In the list of pending members, for any individual account, you can cancel all invitations to join organizations owned by your enterprise. This does not cancel any invitations for that same person to become an enterprise administrator or outside collaborator. + +{% note %} + +**Note:** If an invitation was provisioned via SCIM, you must cancel the invitation via your identity provider (IdP) instead of on {% data variables.product.prodname_dotcom %}. + +{% endnote %} If you use {% data variables.product.prodname_vss_ghe %}, the list of pending invitations includes all {% data variables.product.prodname_vs %} subscribers that haven't joined any of your organizations on {% data variables.product.prodname_dotcom %}, even if the subscriber does not have a pending invitation to join an organization. For more information about how to get {% data variables.product.prodname_vs %} subscribers access to {% data variables.product.prodname_enterprise %}, see "[Setting up {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)." @@ -77,7 +85,9 @@ If you use {% data variables.product.prodname_vss_ghe %}, the list of pending in 1. Under "People", click **Pending invitations**. ![Screenshot of the "Pending invitations" tab in the sidebar](/assets/images/help/enterprises/pending-invitations-tab.png) +1. Optionally, to cancel all invitations for an account to join organizations owned by your enterprise, to the right of the account, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Cancel invitation**. + ![Screenshot of the "Cancel invitation" button](/assets/images/help/enterprises/cancel-enterprise-member-invitation.png) 1. Optionally, to view pending invitations for enterprise administrators or outside collaborators, under "Pending members", click **Administrators** or **Outside collaborators**. ![Screenshot of the "Members", "Administrators", and "Outside collaborators" tabs](/assets/images/help/enterprises/pending-invitations-type-tabs.png) @@ -85,7 +95,7 @@ If you use {% data variables.product.prodname_vss_ghe %}, the list of pending in ## Viewing suspended members in an {% data variables.product.prodname_emu_enterprise %} -If your enterprise uses {% data variables.product.prodname_emus %}, you can also view suspended users. Suspended users are members who have been deprovisioned after being unassigned from the {% data variables.product.prodname_emu_idp_application %} application or deleted from the identity provider. For more information, see "[About Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)." +If your enterprise uses {% data variables.product.prodname_emus %}, you can also view suspended users. Suspended users are members who have been deprovisioned after being unassigned from the {% data variables.product.prodname_emu_idp_application %} application or deleted from the identity provider. 詳しい情報については「[Enterpriseが管理しているユーザ](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)」を参照してください。 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index b0c87d6303..75df940d02 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -16,7 +16,7 @@ shortTitle: Authentication to GitHub --- ## About authentication to {% data variables.product.prodname_dotcom %} -To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. +To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. You can access your resources in {% data variables.product.product_name %} in a variety of ways: in the browser, via {% data variables.product.prodname_desktop %} or another desktop application, with the API, or via the command line. Each way of accessing {% data variables.product.product_name %} supports different modes of authentication. {%- ifversion not fpt %} @@ -27,35 +27,47 @@ You can access your resources in {% data variables.product.product_name %} in a ## Authenticating in your browser -You can authenticate to {% data variables.product.product_name %} in your browser {% ifversion ghae %}using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."{% else %}in different ways. +{% ifversion ghae %} + +You can authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)." + +{% else %} {% ifversion fpt or ghec %} -- If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} - If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also be required to enable two-factor authentication. +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} + +If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also use two-factor authentication and SAML single sign-on, which can be required by organization and enterprise owners. + +{% else %} + +You can authenticate to {% data variables.product.product_name %} in your browser in a number of ways. + {% endif %} - **Username and password only** - You'll create a password when you create your account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)."{% ifversion fpt or ghec %} - If you have not enabled 2FA, {% data variables.product.product_name %} will ask for additional verification when you first sign in from an unrecognized device, such as a new browser profile, a browser where the cookies have been deleted, or a new computer. - - After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the GitHub Mobile application installed, you'll receive a notification there instead.{% endif %} + + After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the {% data variables.product.prodname_mobile %} application installed, you'll receive a notification there instead. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."{% endif %} - **Two-factor authentication (2FA)** (recommended) - If you enable 2FA, after you successfully enter your username and password, we'll also prompt you to provide a code that's generated by a time-based one time password (TOTP) application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)." - - In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% endif %}{% ifversion ghes %} -- **Identity provider (IdP) authentication** - - Your site administrator may configure {% data variables.product.product_location %} to use authentication with an IdP instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)." + - In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% ifversion ghes %} +- **External authentication** + - Your site administrator may configure {% data variables.product.product_location %} to use external authentication instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)."{% endif %}{% ifversion fpt or ghec %} +- **SAML single sign-on** + - Before you can access resources owned by an organization or enterprise account that uses SAML single sign-on, you may need to also authenticate through an IdP. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} + {% endif %} ## Authenticating with {% data variables.product.prodname_desktop %} - You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." ## Authenticating with the API You can authenticate with the API in different ways. -- **Personal access tokens** +- **Personal access tokens** - In limited situations, such as testing, you can use a personal access token to access the API. Using a personal access token enables you to revoke access at any time. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." - **Web application flow** - For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)." @@ -68,7 +80,7 @@ You can access repositories on {% data variables.product.product_name %} from th ### HTTPS -You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. +You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a personal access token or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). 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 8c4e01f2ed..84f1366ddc 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 @@ -44,7 +44,7 @@ A token with no assigned scopes can only access public information. トークン {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.personal_access_tokens %} {% data reusables.user-settings.generate_new_token %} -5. トークンにわかりやすい名前を付けます。 ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %} +5. トークンにわかりやすい名前を付けます。 ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae or ghec %} 6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker. ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %} 7. このトークンに付与するスコープ、すなわち権限を選択します。 トークンを使用してコマンドラインからリポジトリにアクセスするには、[**repo**] を選択します。 {% ifversion fpt or ghes or ghec %} @@ -80,5 +80,5 @@ Instead of manually entering your PAT for every HTTPS Git operation, you can cac ## 参考リンク -- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} - "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md index 9ae5385fd1..70a32b468d 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md @@ -25,9 +25,9 @@ The `git filter-repo` tool and the BFG Repo-Cleaner rewrite your repository's hi {% warning %} -This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. ただし、こうしたコミットも、リポジトリのクローンやフォークからは、{% data variables.product.product_name %} でキャッシュされているビューの SHA-1 ハッシュによって直接、また参照元のプルリクエストによって、到達できる可能性があることに注意することが重要です。 You cannot remove sensitive data from other users' clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}. +**Warning**: This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. However, those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}. -**Warning: Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! キーをコミットした場合は、新たに生成してください。 Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. Consider these limitations in your decision to rewrite your repository's history. +**Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! キーをコミットした場合は、新たに生成してください。 Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. Consider these limitations in your decision to rewrite your repository's history. {% endwarning %} @@ -152,7 +152,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil After using either the BFG tool or `git filter-repo` to remove the sensitive data and pushing your changes to {% data variables.product.product_name %}, you must take a few more steps to fully remove the data from {% data variables.product.product_name %}. -1. {% data variables.contact.contact_support %} に連絡し、{% data variables.product.product_name %} 上で、キャッシュされているビューと、プルリクエストでの機密データへの参照を削除するよう依頼します。 Please provide the name of the repository and/or a link to the commit you need removed. +1. {% data variables.contact.contact_support %} に連絡し、{% data variables.product.product_name %} 上で、キャッシュされているビューと、プルリクエストでの機密データへの参照を削除するよう依頼します。 Please provide the name of the repository and/or a link to the commit you need removed.{% ifversion ghes %} For more information about how site administrators can remove unreachable Git objects, see "[Command line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repo-gc)."{% endif %} 2. コラボレータには、 作成したブランチを古い (汚染された) リポジトリ履歴から[リベース](https://git-scm.com/book/en/Git-Branching-Rebasing)する (マージ*しない*) よう伝えます。 マージコミットを 1 回でも行うと、パージで問題が発生したばかりの汚染された履歴の一部または全部が再導入されてしまいます。 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 7997cdc755..8d2642b763 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 @@ -28,15 +28,11 @@ The security log lists all actions performed within the last 90 days. 1. ユーザ設定サイドバーで [**Security log**] をクリックします。 ![セキュリティログのタブ](/assets/images/help/settings/audit-log-tab.png) {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} ## セキュリティログを検索する {% data reusables.audit_log.audit-log-search %} ### 実行されたアクションに基づく検索 -{% else %} -## セキュリティログでのイベントを理解する -{% endif %} セキュリティログにリストされているイベントは、アクションによってトリガーされます。 アクションは次のカテゴリに分類されます。 @@ -109,10 +105,10 @@ The security log lists all actions performed within the last 90 days. ### `oauth_authorization` category actions -| アクション | 説明 | -| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps). | -| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %} +| アクション | 説明 | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps). | +| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %} {% ifversion fpt or ghec %} @@ -178,25 +174,25 @@ The security log lists all actions performed within the last 90 days. {% 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` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `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` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `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` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +| アクション | 説明 | +| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `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` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `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` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | {% endif %} {% ifversion fpt or ghec %} diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md index 0f1543d813..16ff6d99c0 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md @@ -14,7 +14,7 @@ redirect_from: - /github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation --- -When a token {% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}has expired or {% endif %} has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token. +When a token {% ifversion fpt or ghae or ghes > 3.2 or ghec %}has expired or {% endif %} has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token. This article explains the possible reasons your {% data variables.product.product_name %} token might be revoked or expire. @@ -24,7 +24,7 @@ This article explains the possible reasons your {% data variables.product.produc {% endnote %} -{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## Token revoked after reaching its expiration date When you create a personal access token, we recommend that you set an expiration for your token. Upon reaching your token's expiration date, the token is automatically revoked. 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)」を参照してください。 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 e1fbc4ab74..e7d54494fe 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 @@ -58,7 +58,7 @@ See "[Reviewing your authorized integrations](/articles/reviewing-your-authorize {% ifversion not ghae %} -If you have reset your account password and would also like to trigger a sign-out from the GitHub Mobile app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. For additional information, see "[Reviewing your authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)." +If you have reset your account password and would also like to trigger a sign-out from the {% data variables.product.prodname_mobile %} app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. This will sign out all instances of the {% data variables.product.prodname_mobile %} app associated with your account. For additional information, see "[Reviewing your authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)." {% endif %} diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md index e62617f34b..e80b4823ce 100644 --- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md +++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md @@ -22,7 +22,7 @@ shortTitle: Change 2FA delivery method {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security %} -3. [SMS delivery] の隣にある [**Edit**] をクリックします。 ![SMS 配信オプションの編集](/assets/images/help/2fa/edit-sms-delivery-option.png) +3. Next to "Primary two-factor method", click **Change**. ![Edit primary delivery options](/assets/images/help/2fa/edit-primary-delivery-option.png) 4. [Delivery options] の下にある [**Reconfigure two-factor authentication**] をクリックします。 ![2FA 配信オプションの切り替え](/assets/images/help/2fa/2fa-switching-methods.png) 5. 2 要素認証を TOTP モバイルアプリケーションで設定するかテキストメッセージで設定するかを決めます。 詳しい情報については「[2 要素認証の設定](/articles/configuring-two-factor-authentication)」を参照してください。 - TOTP モバイルアプリケーションで 2 要素認証を設定するには、[**Set up using an app**] をクリックします。 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 8f7438dd1e..1d0e9ef817 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 @@ -48,7 +48,7 @@ Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_e リポジトリが使用するストレージは、{% data variables.product.prodname_actions %}の成果物と{% data variables.product.prodname_registry %}の消費の合計のストレージです。 ストレージのコストは、アカウントが所有するすべてのリポジトリの合計の使用量です。 {% data variables.product.prodname_registry %}の価格に関する詳細な情報については、「[{% data variables.product.prodname_registry %}の支払いについて](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)」を参照してください。 - アカウントによる利用がこれらの制限を超え、消費の限度を0米ドル以上に設定しているなら、月あたりストレージのGBごとに0.25米ドル、そして{% data variables.product.prodname_dotcom %}ホストランナーが使用するオペレーティングシステムに応じた分の使用量ごとに支払うことになります。 {% data variables.product.prodname_dotcom %}は、各ジョブが使用する分をもっとも近い分に丸めます。 + If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %}は、各ジョブが使用する分をもっとも近い分に丸めます。 {% note %} diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/ja-JP/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md index d9247cd964..1bbe77f653 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md +++ b/translations/ja-JP/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md @@ -49,9 +49,9 @@ All data transferred out, when triggered by {% data variables.product.prodname_a Storage usage is shared with build artifacts produced by {% data variables.product.prodname_actions %} for repositories owned by your account. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." -{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.25 USD per GB of storage and $0.50 USD per GB of data transfer. +{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and $0.50 USD per GB of data transfer. -For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.25 USD per GB or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD. +For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.008 USD per GB per day or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD. {% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %} diff --git a/translations/ja-JP/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/ja-JP/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md index 15c126e263..49cf14c22f 100644 --- a/translations/ja-JP/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md +++ b/translations/ja-JP/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md @@ -59,7 +59,7 @@ One person may be able to complete the tasks because the person has all of the r **Tips**: - While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_location %} matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license. - - If the subscriber accepts the invitation to the organization with an existing personal account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their personal account on {% data variables.product.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)." + - If the subscriber accepts the invitation to the organization with an existing personal account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their personal account on {% data variables.product.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)." - If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository. {% endtip %} 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 cccde8bdec..a462055e5a 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 @@ -73,7 +73,7 @@ By default, the {% data variables.product.prodname_codeql_workflow %} uses the ` If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Additionally, when an `on:push` scan returns results that can be mapped to an open pull request, these alerts will automatically appear on the pull request in the same places as other pull request alerts. The alerts are identified by comparing the existing analysis of the head of the branch to the analysis for the target branch. For more information on {% data variables.product.prodname_code_scanning %} alerts in pull requests, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." {% endif %} @@ -85,7 +85,7 @@ For more information about the `pull_request` event, see "[Events that trigger w If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." {% endif %} diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index 7649b34387..990c6e03c7 100644 --- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -155,9 +155,9 @@ The names of the {% data variables.product.prodname_code_scanning %} analysis ch ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png) -When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. +When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. -{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png) The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request. @@ -167,13 +167,13 @@ For example, in the screenshot above, {% data variables.product.prodname_code_sc ![Missing analysis for commit message](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png) {% endif %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ### Reasons for the "Analysis not found" message {% else %} ### Reasons for the "Missing analysis" message {% endif %} -After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. +After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include: 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 0facaadb22..66507b8e68 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 @@ -28,7 +28,7 @@ topics: ## About {% data variables.product.prodname_code_scanning %} results on pull requests In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, these are reported as check results in the pull request. The alerts are also shown as annotations in the **Files changed** tab of the pull request. If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} In repositories where {% data variables.product.prodname_code_scanning %} is configured to scan each time code is pushed, {% data variables.product.prodname_code_scanning %} will also map the results to any open pull requests and add the alerts as annotations in the same places as other pull request checks. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." {% endif %} @@ -42,7 +42,7 @@ There are many options for configuring {% data variables.product.prodname_code_s For all configurations of {% data variables.product.prodname_code_scanning %}, the check that contains the results of {% data variables.product.prodname_code_scanning %} is: **{% data variables.product.prodname_code_scanning_capc %} results**. The results for each analysis tool used are shown separately. Any new alerts caused by changes in the pull request are shown as annotations. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)." +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)." ![{% data variables.product.prodname_code_scanning_capc %} results check on a pull request](/assets/images/help/repository/code-scanning-results-check.png) {% endif %} diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index 233364f4bf..b73490579e 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -10,7 +10,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md index 86404653d8..0694e287c8 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md @@ -5,7 +5,7 @@ shortTitle: Dependabotアラートの設定 versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md index 25dfe7bb32..4cfb0647e3 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -31,7 +31,7 @@ topics: {% ifversion fpt or ghec %}Organization のオーナーの場合は、ワンクリックで Organization 内のすべてのリポジトリの {% data variables.product.prodname_dependabot_alerts %} を有効または無効にできます。 新しく作成されたリポジトリに対して、脆弱性のある依存関係の検出を有効にするか無効にするかを設定することもできます。 詳しい情報については、「[Organization のセキュリティおよび分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)」を参照してください。 {% endif %} -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} デフォルトでは、EnterpriseのオーナーがEnterpriseにおいて通知のためのメールを設定していれば、あなたはメールで{% data variables.product.prodname_dependabot_alerts %}を受け取ることになります。 Enterpriseオーナーは、通知なしで{% data variables.product.prodname_dependabot_alerts %}を有効化することもできます。 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_dependabot %}の有効化](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)」を参照してください。 diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md index b57517edf7..4bbf2a61ca 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md @@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md index 6063d726f1..f3ac7bdeee 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md @@ -11,7 +11,7 @@ shortTitle: Dependabotアラートの表示 versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -55,7 +55,7 @@ topics: {% note %} -**ノート:** ベータリリースの間、この機能は2022年4月14日*以降*に生成された新規のPythonアドバイザリと、過去のPythonのアドバイザリの一部に対してのみ有効です。 GitHubは、さらなる過去のPythonアドバイザリにさかのぼってデータを加えていっています。これは、随時追加されていっています。 脆弱性のある呼び出しは、{% data variables.product.prodname_dependabot_alerts %}ページ上でのみハイライトされます。 +**ノート:** ベータリリースの間、この機能は2022年4月14日*以降*に生成された新規のPythonアドバイザリと、過去のPythonのアドバイザリの一部に対してのみ有効です。 {% data variables.product.prodname_dotcom %} is working to backfill data across additional historical Python advisories, which are added on a rolling basis. 脆弱性のある呼び出しは、{% data variables.product.prodname_dependabot_alerts %}ページ上でのみハイライトされます。 {% endnote %} @@ -65,7 +65,7 @@ topics: 脆弱性のある呼び出しが検出されたアラートについては、アラートの詳細ページに追加情報が表示されます。 -- 関数が使われている場所、もしくは複数の呼び出しがある場合には最初の呼び出しがあるコードブロック。 +- One or more code blocks showing where the function is used. - 関数自体をリストしているアノテーション。関数が呼ばれている行へのリンク付きで。 !["Vulnerable call"ラベルの付いたアラートのアラート詳細ページを表示しているスクリーンショット](/assets/images/help/repository/review-calls-to-vulnerable-functions.png) diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md index a79c611287..fc16885db1 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md @@ -61,7 +61,7 @@ If security updates are not enabled for your repository and you don't know why, You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below). -You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your personal account or organization. For more information, see "[Managing security and analysis settings for your personal 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)." +You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your personal account or organization. For more information, see "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data variables.product.prodname_dependabot_security_updates %} require specific repository settings. For more information, see "[Supported repositories](#supported-repositories)." diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md index 7a437d9060..152a7623fc 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md @@ -30,7 +30,7 @@ shortTitle: Dependabotバージョンアップデート {% data variables.product.prodname_dependabot %} は、依存関係を維持する手間を省きます。 これを使用して、リポジトリが依存するパッケージおよびアプリケーションの最新リリースに自動的に対応できるようにすることができます。 -You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_configuration file into your repository. 設定ファイルは、リポジトリに保存されているマニフェストまたは他のパッケージ定義ファイルの場所を指定します。 {% data variables.product.prodname_dependabot %} はこの情報を使用して、古いパッケージとアプリケーションをチェックします。 {% data variables.product.prodname_dependabot %} は、依存関係のセマンティックバージョニング（[semver](https://semver.org/)）を調べて、そのバージョンへの更新の必要性を判断することにより、依存関係の新しいバージョンの有無を決定します。 特定のパッケージマネージャーでは、{% data variables.product.prodname_dependabot_version_updates %} もベンダをサポートしています。 ベンダ (またはキャッシュ) された依存関係は、マニフェストで参照されるのではなく、リポジトリ内の特定のディレクトリにチェックインされる依存関係です。 パッケージサーバーが利用できない場合でも、ビルド時にベンダ依存関係を利用できます。 {% data variables.product.prodname_dependabot_version_updates %} は、ベンダの依存関係をチェックして新しいバージョンを確認し、必要に応じて更新するように設定できます。 +You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_ configuration file into your repository. 設定ファイルは、リポジトリに保存されているマニフェストまたは他のパッケージ定義ファイルの場所を指定します。 {% data variables.product.prodname_dependabot %} はこの情報を使用して、古いパッケージとアプリケーションをチェックします。 {% data variables.product.prodname_dependabot %} は、依存関係のセマンティックバージョニング（[semver](https://semver.org/)）を調べて、そのバージョンへの更新の必要性を判断することにより、依存関係の新しいバージョンの有無を決定します。 特定のパッケージマネージャーでは、{% data variables.product.prodname_dependabot_version_updates %} もベンダをサポートしています。 ベンダ (またはキャッシュ) された依存関係は、マニフェストで参照されるのではなく、リポジトリ内の特定のディレクトリにチェックインされる依存関係です。 パッケージサーバーが利用できない場合でも、ビルド時にベンダ依存関係を利用できます。 {% data variables.product.prodname_dependabot_version_updates %} は、ベンダの依存関係をチェックして新しいバージョンを確認し、必要に応じて更新するように設定できます。 {% data variables.product.prodname_dependabot %} が古い依存関係を特定すると、プルリクエストを発行して、マニフェストを依存関係の最新バージョンに更新します。 ベンダーの依存関係の場合、{% data variables.product.prodname_dependabot %} はプルリクエストを生成して、古い依存関係を新しいバージョンに直接置き換えます。 テストに合格したことを確認し、プルリクエストの概要に含まれている変更履歴とリリースノートを確認して、マージします。 詳しい情報については「[{% data variables.product.prodname_dependabot %}のバージョンアップデートの設定](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)」を参照してください。 diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md index 435286c7e8..24a83f654c 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md @@ -322,7 +322,7 @@ updates: `ignore` オプションを使用して、更新する依存関係をカスタマイズできます。 `ignore` オプションは、次のオプションに対応しています。 -- `dependency-name`: 名前が一致する依存関係の更新を無視するために使用し、必要に応じて `*` を使用して 0 文字以上の文字と一致させます。 Javaの依存関係については、`dependency-name`属性のフォーマットは`groupId:artifactId`です（たとえば`org.kohsuke:github-api`）。 {% if dependabot-grouped-dependencies %} To prevent {% data variables.product.prodname_dependabot %} from automatically updating TypeScript type definitions from DefinitelyTyped, use `@types/*`.{% endif %} +- `dependency-name`: 名前が一致する依存関係の更新を無視するために使用し、必要に応じて `*` を使用して 0 文字以上の文字と一致させます。 Javaの依存関係については、`dependency-name`属性のフォーマットは`groupId:artifactId`です（たとえば`org.kohsuke:github-api`）。 {% if dependabot-grouped-dependencies %} {% data variables.product.prodname_dependabot %} がDefinitelyTypedからTypeScriptの型定義を自動的に更新しないようにするには、`@types/*`を使ってください。{% endif %} - `versions`: 特定のバージョンまたはバージョンの範囲を無視するために使用します。 範囲を定義する場合は、パッケージマネージャーの標準パターンを使用します（例: npm の場合は `^1.0.0`、Bundler の場合は `~> 2.0`）。 - `update-types` - バージョン更新におけるsemverの`major`、`minor`、`patch`更新といった更新の種類を無視するために使います。（たとえば`version-update:semver-patch`でパッチアップデートが無視されます）。 これを`code>dependency-name: "*"`と組み合わせて、特定の`update-types`をすべての依存関係で無視できます。 現時点では、サポートされているオプションは`version-update:semver-major`、`version-update:semver-minor`、`version-update:semver-patch`のみです。 セキュリティの更新はこの設定には影響されません。 diff --git a/translations/ja-JP/content/code-security/dependabot/index.md b/translations/ja-JP/content/code-security/dependabot/index.md index cb1f4984f9..2cfeef9d87 100644 --- a/translations/ja-JP/content/code-security/dependabot/index.md +++ b/translations/ja-JP/content/code-security/dependabot/index.md @@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index 722d2e48bd..86519f787b 100644 --- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -36,7 +36,7 @@ topics: * {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new vulnerability record is added, it scans all existing repositories and generates an alert for each vulnerable repository. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." * {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)." - {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% ifversion ghes or ghae-issue-4864 %} and synchronized to {% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)." + {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% ifversion ghes or ghae %} and synchronized to {% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)." ## Do {% data variables.product.prodname_dependabot_alerts %} only relate to vulnerable dependencies in manifests and lockfiles? 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 21c6e0e3f7..c32115569b 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 @@ -20,7 +20,7 @@ topics: The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Available for all repositories {% endif %} ### Security policy @@ -41,7 +41,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% endif %} -{% ifversion ghes < 3.3 or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae %} ### {% data variables.product.prodname_dependabot_alerts %} {% data reusables.dependabot.dependabot-alerts-beta %} @@ -55,7 +55,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ### Dependency graph The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository. @@ -100,13 +100,13 @@ Available only with a license for {% data variables.product.prodname_GH_advanced Automatically detect tokens or credentials that have been checked into a repository. You can view alerts for any secrets that {% data variables.product.company_short %} finds in your code, so that you know which tokens or credentials to treat as compromised. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ### Dependency review 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 or ghae-issue-4554 %} +{% ifversion ghec or ghes > 3.1 or ghae %} ### Security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams {% ifversion ghec %} 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 ebb6dbe2c8..dd6785e84c 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 @@ -33,7 +33,7 @@ You can create a default security policy that will display in any of your organi {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph {% 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. @@ -51,7 +51,7 @@ You can create a default security policy that will display in any of your organi For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Managing dependency review @@ -138,7 +138,7 @@ 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 fpt or ghes > 3.1 or ghec or ghae-issue-4554 %}{% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae-issue-4554 %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %} +{% ifversion fpt or ghes > 3.1 or ghec or ghae %}{% ifversion ghes > 3.1 or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %} {% ifversion ghec %} diff --git a/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md b/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md index 6ee9dc430b..8b9288bdea 100644 --- a/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md +++ b/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md @@ -44,7 +44,7 @@ From the main page of your repository, click **{% octicon "gear" aria-label="The For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)." -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing the dependency graph {% ifversion fpt or ghec %} @@ -61,7 +61,7 @@ For more information, see "[Exploring the dependencies of a repository](/code-se {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} {% data variables.product.prodname_dependabot_alerts %} are generated when {% data variables.product.prodname_dotcom %} identifies a dependency in the dependency graph with a vulnerability. {% ifversion fpt or ghec %}You can enable {% data variables.product.prodname_dependabot_alerts %} for any repository.{% endif %} @@ -75,11 +75,11 @@ For more information, see "[Exploring the dependencies of a repository](/code-se {% data reusables.dependabot.dependabot-alerts-beta %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[Managing security and analysis settings for your personal account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account){% endif %}." +For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account){% endif %}." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Managing dependency review Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." diff --git a/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md index 4c1bc2e183..9376b0455a 100644 --- a/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md +++ b/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md @@ -143,8 +143,8 @@ aAAAe9 {% if secret-scanning-enterprise-dry-runs %} **ノート:** -- At the enterprise level, only the creator of a custom pattern can edit the pattern, and use it in a dry run. -- Enterprise owners can only make use of dry runs on repositories that they have access to, and enterprise owners do not necessarily have access to all the organizations or repositories within the enterprise. +- Enterpriseレベルでは、カスタムパターンを編集でき、dry runで使えるのはカスタムパターンの作者だけです。 +- Enterpriseオーナーは、アクセスできるリポジトリ上でのみdry runを利用できますが、必ずしもEnterprise内のすべてのOrganizationやリポジトリにアクセスできるわけではありません。 {% else %} **ノート:** dry-runの機能は無いので、カスタムパターンをEnterprise全体で定義する前に、1つのリポジトリ内でテストすることをおすすめします。 そうすれば、過剰な偽陽性の{% data variables.product.prodname_secret_scanning %}アラートを発生させることを防げます。 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 468aed1cfe..0a965e2e3e 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 @@ -1,13 +1,13 @@ --- title: About the security overview intro: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in one place: the Security Overview page.' -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' redirect_from: - /code-security/security-overview/exploring-security-alerts versions: fpt: '*' - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' type: how_to @@ -22,7 +22,7 @@ topics: shortTitle: About security overview --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} @@ -69,7 +69,7 @@ At the organization-level, the security overview displays aggregate and reposito {% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} ### About the enterprise-level security overview -At the enterprise-level, the security overview displays aggregate and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts or view all {% data variables.product.prodname_secret_scanning %} alerts from across your enterprise. +At the enterprise-level, the security overview displays aggregate and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise. Organization owners and security managers for organizations in your enterprise also have limited access to the enterprise-level security overview. They can only view repositories and alerts for the organizations that they have full access to. @@ -80,4 +80,4 @@ At the enterprise-level, the security overview displays aggregate and repository ### About the team-level security overview At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. 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)." -{% endif %} \ No newline at end of file +{% endif %} 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 6bf56ee52a..7022acece4 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 @@ -1,10 +1,10 @@ --- title: セキュリティの概要でのアラートのフィルタリング intro: 特定カテゴリのアラートを表示させるためのフィルタの利用 -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' versions: - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' type: how_to @@ -17,7 +17,7 @@ topics: shortTitle: アラートのフィルタリング --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} diff --git a/translations/ja-JP/content/code-security/security-overview/index.md b/translations/ja-JP/content/code-security/security-overview/index.md index 06fbccfd1c..f6a3477301 100644 --- a/translations/ja-JP/content/code-security/security-overview/index.md +++ b/translations/ja-JP/content/code-security/security-overview/index.md @@ -5,7 +5,7 @@ intro: 一カ所でOrganization内のセキュリティアラートを表示、 product: '{% data reusables.gated-features.security-center %}' versions: fpt: '*' - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' topics: 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 1608092c5d..6a99b307f8 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 @@ -1,7 +1,7 @@ --- title: セキュリティの概要の表示 intro: セキュリティの概要で利用できる様々なビューへのアクセス -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' versions: ghae: issue-5503 @@ -17,7 +17,7 @@ topics: shortTitle: セキュリティの概要の表示 --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} @@ -28,7 +28,8 @@ shortTitle: セキュリティの概要の表示 1. アラートの種類に対する集約された情報を見るには、**Show more（さらに表示）**をクリックしてください。 ![さらに表示ボタン](/assets/images/help/organizations/security-overview-show-more-button.png) {% data reusables.organizations.filter-security-overview %} {% if security-overview-views %} -1. あるいは、左のサイドバーを使ってセキュリティ機能ごとに情報をフィルタリングすることもできます。 それぞれのページで、各機能に固有のフィルタを使って検索を微調整できます。 ![Code scanning固有のページのスクリーンショット](/assets/images/help/organizations/security-overview-code-scanning-alerts.png) +{% data reusables.organizations.security-overview-feature-specific-page %} + ![Code scanning固有のページのスクリーンショット](/assets/images/help/organizations/security-overview-code-scanning-alerts.png) ## Organizationに渡るアラートの表示 @@ -42,6 +43,9 @@ shortTitle: セキュリティの概要の表示 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} 1. ひだりのサイドバーで{% octicon "shield" aria-label="The shield icon" %}**Code Security（コードセキュリティ）**をクリックしてください。 +{% if security-overview-feature-specific-alert-page %} +{% data reusables.organizations.security-overview-feature-specific-page %} +{% endif %} {% endif %} ## リポジトリのアラートの表示 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/index.md b/translations/ja-JP/content/code-security/supply-chain-security/index.md index 93a4d082a9..817b3f524c 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/index.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/index.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot 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 44eb046834..95e730d359 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 @@ -6,7 +6,7 @@ shortTitle: 依存関係のレビュー versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md index 0518b8bf9f..d6310a80a6 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -129,7 +129,7 @@ Public repositories: - **Dependency graph**—enabled by default and cannot be disabled. - **Dependency review**—enabled by default and cannot be disabled. - **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. {% data variables.product.prodname_dotcom %} detects vulnerable dependencies and displays information in 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 %}. - You can also enable or disable 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](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/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-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." + You can also enable or disable 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](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." Private repositories: - **Dependency graph**—not enabled by default. The feature can be enabled by repository administrators. For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)." @@ -139,7 +139,7 @@ Private repositories: - **Dependency review**—available in private repositories owned by organizations provided you have a license for {% data variables.product.prodname_GH_advanced_security %} and the dependency graph enabled. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" and "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)." {% endif %} - **{% data variables.product.prodname_dependabot_alerts %}**—not enabled 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. - You can also enable or disable 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](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/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-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." + You can also enable or disable 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](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." Any repository type: - **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)." 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 409595d281..1b04851134 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 @@ -7,7 +7,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md index 516be09209..e9ea74821d 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md @@ -5,7 +5,7 @@ shortTitle: 依存関係レビューの設定 versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -35,7 +35,7 @@ topics: {% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %} 1. "{% data variables.product.prodname_GH_advanced_security %}"が有効化されていない場合、その隣の**Enable（有効化）**をクリックしてください。 !["Enable" ボタンが強調されたGitHub Advanced Security機能のスクリーンショット](/assets/images/help/security/enable-ghas-private-repo.png) -{% elsif ghes or ghae %} +{% elsif ghes %} 依存関係レビューは、依存関係グラフが{% data variables.product.product_location %}で有効化されており、Organizationもしくはリポジトリで{% data variables.product.prodname_advanced_security %}が有効化されている場合に利用できます。 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_GH_advanced_security %}の有効化](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)」を参照してください。 ### 依存関係グラフが有効化されているかの確認 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md index c6643f0264..6f7f78ff80 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md @@ -6,7 +6,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -25,7 +25,7 @@ shortTitle: 依存関係グラフの設定 {% ifversion fpt or ghec %} ## 依存関係グラフの設定について {% endif %} {% ifversion fpt or ghec %}依存関係グラフを生成するには、{% data variables.product.product_name %} がリポジトリの依存関係のマニフェストおよびロックファイルに読み取りアクセスできる必要があります。 依存関係グラフは、パブリックリポジトリに対しては常に自動的に生成され、プライベートリポジトリに対しては有効化を選択することができます。 依存関係グラフの表示に関する詳しい情報については「[リポジトリの依存関係の調査](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)」を参照してください。{% endif %} -{% ifversion ghes or ghae %} ## 依存関係グラフの有効化 +{% ifversion ghes %} ## 依存関係グラフの有効化 {% data reusables.dependabot.ghes-ghae-enabling-dependency-graph %}{% endif %}{% ifversion fpt or ghec %} ### プライベートリポジトリの依存関係グラフを有効化および無効化する diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index bd87958a33..e5a6efe119 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -12,7 +12,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md index 17e72a032a..0b18f55b86 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md @@ -3,7 +3,7 @@ title: ソフトウェアサプライチェーンの理解 versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependency graph diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md index 6de1b7a25d..0fe9cbaf0e 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md @@ -5,7 +5,7 @@ shortTitle: Troubleshoot dependency graph versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -59,4 +59,4 @@ Yes, the dependency graph has two categories of limits: - "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)" - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" - "[Troubleshooting the detection of vulnerable dependencies](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %} -- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} \ No newline at end of file +- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md index d734f11209..ba8c543f31 100644 --- a/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md @@ -42,7 +42,7 @@ You can check the current service status on the [Status Dashboard](https://www.g ## オプション 4: ローカルのコンテナ化された環境にリモートコンテナとDockerを使用する -リポジトリに `devcontainer.json` がある場合は、Visual Studio Code の [Remote-Containers 機能拡張](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume)を使用して、リポジトリのローカル開発コンテナをビルドしてアタッチすることを検討してください。 このオプションのセットアップ時間は、ローカル仕様と開発コンテナセットアップの複雑さによって異なります。 +If your repository has a `devcontainer.json`, consider using the [Remote-Containers extension](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) in {% data variables.product.prodname_vscode %} to build and attach to a local development container for your repository. このオプションのセットアップ時間は、ローカル仕様と開発コンテナセットアップの複雑さによって異なります。 {% note %} diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/security-in-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/security-in-codespaces.md index c03f01b2f4..276065cd0b 100644 --- a/translations/ja-JP/content/codespaces/codespaces-reference/security-in-codespaces.md +++ b/translations/ja-JP/content/codespaces/codespaces-reference/security-in-codespaces.md @@ -34,7 +34,7 @@ Each codespace has its own isolated virtual network. We use firewalls to block i ### 認証 -You can connect to a codespace using a web browser or from Visual Studio Code. If you connect from Visual Studio Code, you are prompted to authenticate with {% data variables.product.product_name %}. +You can connect to a codespace using a web browser or from {% data variables.product.prodname_vscode %}. If you connect from {% data variables.product.prodname_vscode_shortname %}, you are prompted to authenticate with {% data variables.product.product_name %}. Every time a codespace is created or restarted, it's assigned a new {% data variables.product.company_short %} token with an automatic expiry period. This period allows you to work in the codespace without needing to reauthenticate during a typical working day, but reduces the chance that you will leave a connection open when you stop using the codespace. @@ -84,7 +84,7 @@ Always use encrypted secrets when you want to use sensitive information (such as The secret values are copied to environment variables whenever the codespace is resumed or created, so if you update a secret value while the codespace is running, you’ll need to suspend and resume to pick up the updated value. For more information on secrets, see: -- "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" +- 「[codespacesのための暗号化されたシークレットの管理](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)」 - "[Managing encrypted secrets for your repository and organization for Codespaces](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces)" ### Working with other people's contributions and repositories @@ -109,4 +109,4 @@ Certain development features can potentially add risk to your environment. For e #### Using extensions -Any additional {% data variables.product.prodname_vscode %} extensions that you've installed can potentially introduce more risk. To help mitigate this risk, ensure that the you only install trusted extensions, and that they are always kept up to date. +Any additional {% data variables.product.prodname_vscode_shortname %} extensions that you've installed can potentially introduce more risk. To help mitigate this risk, ensure that the you only install trusted extensions, and that they are always kept up to date. diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md index 3cbdd0a477..25bcca0b2b 100644 --- a/translations/ja-JP/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md +++ b/translations/ja-JP/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md @@ -17,7 +17,7 @@ redirect_from: ## {% data variables.product.prodname_copilot %}を使用する -[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), an AI pair programmer, can be used in any codespace. To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). +[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), an AI pair programmer, can be used in any codespace. To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). To include {% data variables.product.prodname_copilot_short %}, or other extensions, in all of your codespaces, enable Settings Sync. 詳しい情報については、「[アカウントの {% data variables.product.prodname_codespaces %} をパーソナライズする](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)」を参照してください。 Additionally, to include {% data variables.product.prodname_copilot_short %} in a given project for all users, you can specify `GitHub.copilot` as an extension in your `devcontainer.json` file. For information about configuring a `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)." diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md index c7624fba73..297bcfdf10 100644 --- a/translations/ja-JP/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md +++ b/translations/ja-JP/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md @@ -15,13 +15,13 @@ redirect_from: - /codespaces/codespaces-reference/using-the-command-palette-in-codespaces --- -## About the {% data variables.product.prodname_vscode %} Command Palette +## {% data variables.product.prodname_vscode_command_palette %} について -コマンドパレットは、Codespaces で使用できる {% data variables.product.prodname_vscode %} の中心的な機能の1つです。 The {% data variables.product.prodname_vscode_command_palette %} allows you to access many commands for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode %}. For more information on using the {% data variables.product.prodname_vscode_command_palette %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the Visual Studio Code documentation. +コマンドパレットは、Codespaces で使用できる {% data variables.product.prodname_vscode %} の中心的な機能の1つです。 The {% data variables.product.prodname_vscode_command_palette %} allows you to access many commands for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information on using the {% data variables.product.prodname_vscode_command_palette_shortname %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the {% data variables.product.prodname_vscode_shortname %} documentation. -## Accessing the {% data variables.product.prodname_vscode_command_palette %} +## Accessing the {% data variables.product.prodname_vscode_command_palette_shortname %} -You can access the {% data variables.product.prodname_vscode_command_palette %} in a number of ways. +You can access the {% data variables.product.prodname_vscode_command_palette_shortname %} in a number of ways. - Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux). @@ -33,7 +33,7 @@ You can access the {% data variables.product.prodname_vscode_command_palette %} ## {% data variables.product.prodname_github_codespaces %} のコマンド -To see all commands related to {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "Codespaces". +To see all commands related to {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "Codespaces". ![Codespaces に関連するすべてのコマンドのリスト](/assets/images/help/codespaces/codespaces-command-palette.png) @@ -41,13 +41,13 @@ To see all commands related to {% data variables.product.prodname_github_codespa If you add a new secret or change the machine type, you'll have to stop and restart the codespace for it to apply your changes. -To suspend or stop your codespace's container, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "stop". [**Codespaces: Stop Current Codespace**] を選択します。 +To suspend or stop your codespace's container, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "stop". [**Codespaces: Stop Current Codespace**] を選択します。 ![Codespace を停止するコマンド](/assets/images/help/codespaces/codespaces-stop.png) ### テンプレートから開発コンテナを追加する -To add a dev container from a template, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "dev container". [**Codespaces: Add Development Container Configuration Files...**] を選択します。 +To add a dev container from a template, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "dev container". [**Codespaces: Add Development Container Configuration Files...**] を選択します。 ![開発コンテナを追加するコマンド](/assets/images/help/codespaces/add-prebuilt-container-command.png) @@ -55,14 +55,14 @@ To add a dev container from a template, [access the {% data variables.product.pr 開発コンテナを追加するか、設定ファイル（`devcontainer.json` および `Dockerfile`）のいずれかを編集する場合、変更を適用するために codespace を再構築する必要があります。 -To rebuild your container, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "rebuild". **Codespaces: Rebuild Container（Codespaces: コンテナをリビルド）**を選択してください。 +To rebuild your container, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "rebuild". **Codespaces: Rebuild Container（Codespaces: コンテナをリビルド）**を選択してください。 ![Codespace を再構築するコマンド](/assets/images/help/codespaces/codespaces-rebuild.png) ### Codespace のログ -You can use the {% data variables.product.prodname_vscode_command_palette %} to access the codespace creation logs, or you can use it export all logs. +You can use the {% data variables.product.prodname_vscode_command_palette_shortname %} to access the codespace creation logs, or you can use it export all logs. -To retrieve the logs for Codespaces, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "log". [**Codespaces: Export Logs**] を選択して Codespaces に関連するすべてのログをエクスポートするか、[**Codespaces: View Creation Logs**] を選択して設定に関連するログを表示します。 +To retrieve the logs for Codespaces, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "log". [**Codespaces: Export Logs**] を選択して Codespaces に関連するすべてのログをエクスポートするか、[**Codespaces: View Creation Logs**] を選択して設定に関連するログを表示します。 ![ログにアクセスするコマンド](/assets/images/help/codespaces/codespaces-logs.png) diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md index ff9a91d290..cddb002a8b 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -35,7 +35,7 @@ For more information on what happens when you create a codespace, see "[Deep Div For more information on the lifecycle of a codespace, see "[Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)." -If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the Visual Studio Code documentation. +If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.codespaces.use-visual-studio-features %} diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md index 7f7addf27b..2f68961c34 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md @@ -33,7 +33,7 @@ shortTitle: Develop in a codespace 4. パネル: 出力とデバッグ情報、および統合ターミナルのデフォルトの場所を確認できます。 5. ステータスバー: このエリアには、codespace とプロジェクトに関する有用な情報が表示されます。 たとえば、ブランチ名、設定されたポートなどです。 -{% data variables.product.prodname_vscode %} の使用の詳細については、{% data variables.product.prodname_vscode %} ドキュメントの[ユーザインターフェースガイド](https://code.visualstudio.com/docs/getstarted/userinterface)を参照してください。 +{% data variables.product.prodname_vscode_shortname %} の使用の詳細については、{% data variables.product.prodname_vscode_shortname %} ドキュメントの[ユーザインターフェースガイド](https://code.visualstudio.com/docs/getstarted/userinterface)を参照してください。 {% data reusables.codespaces.connect-to-codespace-from-vscode %} @@ -54,7 +54,7 @@ shortTitle: Develop in a codespace ### Using the {% data variables.product.prodname_vscode_command_palette %} -The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)." +The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette_shortname %} in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)." ## 既存の codespace に移動する diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md index 59eb5ed129..3b81563de2 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md @@ -20,17 +20,17 @@ shortTitle: Visual Studio Code ## About {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %} -You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. To use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}, you need to install the {% data variables.product.prodname_github_codespaces %} extension. For more information on setting up Codespaces in {% data variables.product.prodname_vscode %}, see "[Prerequisites](#prerequisites)." +You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. To use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode_shortname %}, you need to install the {% data variables.product.prodname_github_codespaces %} extension. For more information on setting up Codespaces in {% data variables.product.prodname_vscode_shortname %}, see "[Prerequisites](#prerequisites)." -By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." +By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode_shortname %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." -If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." +If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode_shortname %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." ## Prerequisites -To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. +To develop in a codespace directly in {% data variables.product.prodname_vscode_shortname %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode_shortname %} October 2020 Release 1.51 or later. -Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode %} documentation. +Use the {% data variables.product.prodname_vscode_marketplace %} to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% mac %} @@ -40,8 +40,8 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. -1. Sign in to {% data variables.product.product_name %} to approve the extension. +2. To authorize {% data variables.product.prodname_vscode_shortname %} to access your account on {% data variables.product.product_name %}, click **Allow**. +3. Sign in to {% data variables.product.product_name %} to approve the extension. {% endmac %} @@ -56,28 +56,28 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. +1. To authorize {% data variables.product.prodname_vscode_shortname %} to access your account on {% data variables.product.product_name %}, click **Allow**. 1. Sign in to {% data variables.product.product_name %} to approve the extension. {% endwindows %} -## Creating a codespace in {% data variables.product.prodname_vscode %} +## Creating a codespace in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.creating-a-codespace-in-vscode %} -## Opening a codespace in {% data variables.product.prodname_vscode %} +## Opening a codespace in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 1. Under "Codespaces", click the codespace you want to develop in. 1. Click the Connect to Codespace icon. - ![The Connect to Codespace icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) + ![The Connect to Codespace icon in {% data variables.product.prodname_vscode_shortname %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) -## Changing the machine type in {% data variables.product.prodname_vscode %} +## Changing the machine type in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.codespaces-machine-types %} You can change the machine type of your codespace at any time. -1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`). +1. In {% data variables.product.prodname_vscode_shortname %}, open the Command Palette (`shift command P` / `shift control P`). 1. Search for and select "Codespaces: Change Machine Type." ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png) @@ -100,13 +100,13 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts. -## Deleting a codespace in {% data variables.product.prodname_vscode %} +## Deleting a codespace in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.deleting-a-codespace-in-vscode %} -## Switching to the Insiders build of {% data variables.product.prodname_vscode %} +## Switching to the Insiders build of {% data variables.product.prodname_vscode_shortname %} -You can use the [Insiders Build of Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_codespaces %}. +You can use the [Insiders Build of {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_codespaces %}. 1. In bottom left of your {% data variables.product.prodname_codespaces %} window, select **{% octicon "gear" aria-label="The settings icon" %} Settings**. 2. From the list, select "Switch to Insiders Version". diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md index d660632178..161e505d05 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md @@ -19,7 +19,7 @@ shortTitle: ソースコントロール 必要なすべての Git アクションを codespace 内で直接実行できます。 たとえば、リモートリポジトリから変更をフェッチしたり、ブランチを切り替えたり、新しいブランチを作成したり、変更をコミットしてプッシュしたり、プルリクエストを作成したりすることができます。 Codespace 内の統合ターミナルを使用して Git コマンドを入力するか、アイコンとメニューオプションをクリックして最も一般的な Git タスクをすべて完了することができます。 このガイドでは、ソースコントロールにグラフィカルユーザインターフェースを使用する方法について説明します。 -{% data variables.product.prodname_github_codespaces %} 内のソースコントロールは、{% data variables.product.prodname_vscode %} と同じワークフローを使用します。 詳しい情報については、{% data variables.product.prodname_vscode %} のドキュメント「[VS Code でバージョン管理を使用する](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)」を参照してください。 +{% data variables.product.prodname_github_codespaces %} 内のソースコントロールは、{% data variables.product.prodname_vscode %} と同じワークフローを使用します。 For more information, see the {% data variables.product.prodname_vscode_shortname %} documentation "[Using Version Control in {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)." {% data variables.product.prodname_github_codespaces %} を使用してファイルを更新するための一般的なワークフローは次のとおりです。 diff --git a/translations/ja-JP/content/codespaces/getting-started/deep-dive.md b/translations/ja-JP/content/codespaces/getting-started/deep-dive.md index e5daf1cdd9..875c41abac 100644 --- a/translations/ja-JP/content/codespaces/getting-started/deep-dive.md +++ b/translations/ja-JP/content/codespaces/getting-started/deep-dive.md @@ -46,13 +46,13 @@ Since your repository is cloned onto the host VM before the container is created ### Step 3: Connecting to the codespace -When your container has been created and any other initialization has run, you'll be connected to your codespace. You can connect to it through the web or via [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed. +When your container has been created and any other initialization has run, you'll be connected to your codespace. You can connect to it through the web or via [{% data variables.product.prodname_vscode_shortname %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed. ### Step 4: Post-creation setup Once you are connected to your codespace, your automated setup may continue to build based on the configuration you specified in your `devcontainer.json` file. You may see `postCreateCommand` and `postAttachCommand` run. -If you want to use Git hooks in your codespace, set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the Visual Studio Code documentation. +If you want to use Git hooks in your codespace, set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. If you have a public dotfiles repository for {% data variables.product.prodname_codespaces %}, you can enable it for use with new codespaces. When enabled, your dotfiles will be cloned to the container and the install script will be invoked. 詳しい情報については、「[アカウントの {% data variables.product.prodname_codespaces %} をパーソナライズする](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)」を参照してください。 @@ -67,7 +67,7 @@ As you develop in your codespace, it will save any changes to your files every f {% note %} -**Note:** Changes in a codespace in {% data variables.product.prodname_vscode %} are not saved automatically, unless you have enabled [Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). +**Note:** Changes in a codespace in {% data variables.product.prodname_vscode_shortname %} are not saved automatically, unless you have enabled [Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). {% endnote %} ### Closing or stopping your codespace @@ -93,7 +93,7 @@ Running your application when you first land in your codespace can make for a fa ## Committing and pushing your changes -Git is available by default in your codespace and so you can rely on your existing Git workflow. You can work with Git in your codespace either via the Terminal or by using [Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" +Git is available by default in your codespace and so you can rely on your existing Git workflow. You can work with Git in your codespace either via the Terminal or by using [{% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" ![Running git status in Codespaces Terminal](/assets/images/help/codespaces/git-status.png) @@ -107,9 +107,9 @@ You can create a codespace from any branch, commit, or pull request in your proj ## Personalizing your codespace with extensions -Using {% data variables.product.prodname_vscode %} in your codespace gives you access to the {% data variables.product.prodname_vscode %} Marketplace so that you can add any extensions you need. For information on how extensions run in {% data variables.product.prodname_codespaces %}, see [Supporting Remote Development and GitHub Codespaces](https://code.visualstudio.com/api/advanced-topics/remote-extensions) in the {% data variables.product.prodname_vscode %} docs. +Using {% data variables.product.prodname_vscode_shortname %} in your codespace gives you access to the {% data variables.product.prodname_vscode_marketplace %} so that you can add any extensions you need. For information on how extensions run in {% data variables.product.prodname_codespaces %}, see [Supporting Remote Development and GitHub Codespaces](https://code.visualstudio.com/api/advanced-topics/remote-extensions) in the {% data variables.product.prodname_vscode_shortname %} docs. -If you already use {% data variables.product.prodname_vscode %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to automatically sync extensions, settings, themes, and keyboard shortcuts between your local instance and any {% data variables.product.prodname_codespaces %} you create. +If you already use {% data variables.product.prodname_vscode_shortname %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to automatically sync extensions, settings, themes, and keyboard shortcuts between your local instance and any {% data variables.product.prodname_codespaces %} you create. ## 参考リンク diff --git a/translations/ja-JP/content/codespaces/getting-started/quickstart.md b/translations/ja-JP/content/codespaces/getting-started/quickstart.md index 4f548774ba..05fd14d9ef 100644 --- a/translations/ja-JP/content/codespaces/getting-started/quickstart.md +++ b/translations/ja-JP/content/codespaces/getting-started/quickstart.md @@ -72,7 +72,7 @@ Now that you've made a few changes, you can use the integrated terminal or the s ## Personalizing with an extension -codespace 内で、Visual Studio Code Marketplace にアクセスできます。 For this example, you'll install an extension that alters the theme, but you can install any extension that is useful for your workflow. +Within a codespace, you have access to the {% data variables.product.prodname_vscode_marketplace %}. For this example, you'll install an extension that alters the theme, but you can install any extension that is useful for your workflow. 1. 左サイトバーで、[Extensions] アイコンをクリックします。 @@ -84,7 +84,7 @@ codespace 内で、Visual Studio Code Marketplace にアクセスできます。 ![fairyfloss のテーマを選択](/assets/images/help/codespaces/fairyfloss.png) -4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to any other codespaces you open and any instances of Visual Studio Code that are signed into your GitHub account. +4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to any other codespaces you open and any instances of {% data variables.product.prodname_vscode %} that are signed into your GitHub account. ## 次のステップ 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 69c15e89ae..f9cd3847c3 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 @@ -41,7 +41,7 @@ You can limit the choice of machine types that are available for repositories ow ## Deleting unused codespaces -Your users can delete their codespaces in https://github.com/codespaces and from within Visual Studio Code. To reduce the size of a codespace, users can manually delete files using the terminal or from within Visual Studio Code. +Your users can delete their codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, users can manually delete files using the terminal or from within {% data variables.product.prodname_vscode_shortname %}. {% note %} 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 da98f032a7..5b46656b64 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 @@ -74,4 +74,4 @@ Organization 内のシークレットに適用されているアクセスポリ ## 参考リンク -- "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)" +- 「[codespacesのための暗号化されたシークレットの管理](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)」 diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md index e5850f61ac..3366306e7e 100644 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md @@ -25,7 +25,7 @@ When permissions are listed in the `devcontainer.json` file, you will be prompte To create codespaces with custom permissions defined, you must use one of the following: * The {% data variables.product.prodname_dotcom %} web UI * [{% data variables.product.prodname_dotcom %} CLI](https://github.com/cli/cli/releases/latest) 2.5.2 or later -* [{% data variables.product.prodname_github_codespaces %} Visual Studio Code extension](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 or later +* [{% data variables.product.prodname_github_codespaces %} {% data variables.product.prodname_vscode %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 or later ## Setting additional repository permissions diff --git a/translations/ja-JP/content/codespaces/overview.md b/translations/ja-JP/content/codespaces/overview.md index 4035c78475..a9057f7df9 100644 --- a/translations/ja-JP/content/codespaces/overview.md +++ b/translations/ja-JP/content/codespaces/overview.md @@ -34,7 +34,7 @@ To customize the runtimes and tools in your codespace, you can create one or mor If you don't add a dev container configuration, {% data variables.product.prodname_codespaces %} will clone your repository into an environment with the default codespace image that includes many tools, languages, and runtime environments. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". -You can also personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and VS Code extensions. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)". +You can also personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and {% data variables.product.prodname_vscode_shortname %} extensions. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)". ## {% data variables.product.prodname_codespaces %}の支払いについて diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md index ec56098853..cda5e1ada5 100644 --- a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md +++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md @@ -94,7 +94,7 @@ Prebuilds do not use any user-level secrets while building your environment, bec ## Configuring time-consuming tasks to be included in the prebuild -You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild template creation. For more information, see the Visual Studio Code documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)." +You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild template creation. For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)." `onCreateCommand` is run only once, when the prebuild template is created, whereas `updateContentCommand` is run at template creation and at subsequent template updates. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild template update. diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md index fccf4fbc85..6a7e630c94 100644 --- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md +++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md @@ -110,7 +110,7 @@ To use a Dockerfile as part of a dev container configuration, reference it in yo } ``` -For more information about using a Dockerfile in a dev container configuration, see the {% data variables.product.prodname_vscode %} documentation "[Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)." +For more information about using a Dockerfile in a dev container configuration, see the {% data variables.product.prodname_vscode_shortname %} documentation "[Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)." ## Using the default dev container configuration @@ -122,7 +122,7 @@ The default configuration is a good option if you're working on a small project ## Using a predefined dev container configuration -You can choose from a list of predefined configurations to create a dev container configuration for your repository. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed. +You can choose from a list of predefined configurations to create a dev container configuration for your repository. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode_shortname %} settings, and {% data variables.product.prodname_vscode_shortname %} extensions that should be installed. 追加の拡張性が必要な場合は、事前定義済みの設定を使用することをお勧めします。 You can also start with a predefined configuration and amend it as needed for your project. @@ -192,9 +192,9 @@ If `.devcontainer/devcontainer.json` or `.devcontainer.json` exists, it will be ### Editing the devcontainer.json file -You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %} +You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode_shortname %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %} -The `devcontainer.json` file is written using the JSONC format. This allows you to include comments within the configuration file. For more information, see "[Editing JSON with Visual Studio Code](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode %} documentation. +The `devcontainer.json` file is written using the JSONC format. This allows you to include comments within the configuration file. For more information, see "[Editing JSON with {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% note %} @@ -202,11 +202,11 @@ The `devcontainer.json` file is written using the JSONC format. This allows you {% endnote %} -### Editor settings for Visual Studio Code +### Editor settings for {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.vscode-settings-order %} -2 つの場所で {% data variables.product.prodname_vscode %} のデフォルトのエディタ設定を定義できます。 +You can define default editor settings for {% data variables.product.prodname_vscode_shortname %} in two places. * Editor settings defined in the `.vscode/settings.json` file in your repository are applied as _Workspace_-scoped settings in the codespace. * Editor settings defined in the `settings` key in the `devcontainer.json` file are applied as _Remote [Codespaces]_-scoped settings in the codespace. diff --git a/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md b/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md index cae88e71b0..ead68c3571 100644 --- a/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md +++ b/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md @@ -27,7 +27,7 @@ The {% data variables.product.prodname_serverless %} introduces a lightweight ed The {% data variables.product.prodname_serverless %} is available to everyone for free on {% data variables.product.prodname_dotcom_the_website %}. -The {% data variables.product.prodname_serverless %} provides many of the benefits of {% data variables.product.prodname_vscode %}, such as search, syntax highlighting, and a source control view. You can also use Settings Sync to share your own {% data variables.product.prodname_vscode %} settings with the editor. For more information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode %} documentation. +The {% data variables.product.prodname_serverless %} provides many of the benefits of {% data variables.product.prodname_vscode %}, such as search, syntax highlighting, and a source control view. You can also use Settings Sync to share your own {% data variables.product.prodname_vscode_shortname %} settings with the editor. For more information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation. The {% data variables.product.prodname_serverless %} runs entirely in your browser’s sandbox. The editor doesn’t clone the repository, but instead uses the [GitHub Repositories extension](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) to carry out most of the functionality that you will use. Your work is saved in the browser’s local storage until you commit it. You should commit your changes regularly to ensure that they're always accessible. @@ -49,7 +49,7 @@ Both the {% data variables.product.prodname_serverless %} and {% data variables. | **Start up** | The {% data variables.product.prodname_serverless %} opens instantly with a key-press and you can start using it right away, without having to wait for additional configuration or installation. | When you create or resume a codespace, the codespace is assigned a VM and the container is configured based on the contents of a `devcontainer.json` file. This set up may take a few minutes to create the environment. For more information, see "[Creating a Codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." | | **Compute** | There is no associated compute, so you won’t be able to build and run your code or use the integrated terminal. | With {% data variables.product.prodname_codespaces %}, you get the power of dedicated VM on which you can run and debug your application. | | **Terminal access** | なし. | {% data variables.product.prodname_codespaces %} provides a common set of tools by default, meaning that you can use the Terminal exactly as you would in your local environment. | -| **Extensions** | Only a subset of extensions that can run in the web will appear in the Extensions View and can be installed. For more information, see "[Using extensions](#using-extensions)." | With Codespaces, you can use most extensions from the Visual Studio Code Marketplace. | +| **Extensions** | Only a subset of extensions that can run in the web will appear in the Extensions View and can be installed. For more information, see "[Using extensions](#using-extensions)." | With Codespaces, you can use most extensions from the {% data variables.product.prodname_vscode_marketplace %}. | ### Continue working on {% data variables.product.prodname_codespaces %} @@ -61,9 +61,9 @@ To continue your work in a codespace, click **Continue Working on…** and selec ## Using source control -When you use the {% data variables.product.prodname_serverless %}, all actions are managed through the Source Control View, which is located in the Activity Bar on the left hand side. For more information on the Source Control View, see "[Version Control](https://code.visualstudio.com/docs/editor/versioncontrol)" in the {% data variables.product.prodname_vscode %} documentation. +When you use the {% data variables.product.prodname_serverless %}, all actions are managed through the Source Control View, which is located in the Activity Bar on the left hand side. For more information on the Source Control View, see "[Version Control](https://code.visualstudio.com/docs/editor/versioncontrol)" in the {% data variables.product.prodname_vscode_shortname %} documentation. -Because the web-based editor uses the GitHub Repositories extension to power its functionality, you can switch branches without needing to stash changes. For more information, see "[GitHub Repositories](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" in the {% data variables.product.prodname_vscode %} documentation. +Because the web-based editor uses the GitHub Repositories extension to power its functionality, you can switch branches without needing to stash changes. For more information, see "[GitHub Repositories](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" in the {% data variables.product.prodname_vscode_shortname %} documentation. ### 新規ブランチの作成 @@ -88,9 +88,9 @@ You can use the {% data variables.product.prodname_serverless %} to work with an ## Using extensions -The {% data variables.product.prodname_serverless %} supports {% data variables.product.prodname_vscode %} extensions that have been specifically created or updated to run in the web. These extensions are known as "web extensions". To learn how you can create a web extension or update your existing extension to work for the web, see "[Web extensions](https://code.visualstudio.com/api/extension-guides/web-extensions)" in the {% data variables.product.prodname_vscode %} documentation. +The {% data variables.product.prodname_serverless %} supports {% data variables.product.prodname_vscode_shortname %} extensions that have been specifically created or updated to run in the web. These extensions are known as "web extensions". To learn how you can create a web extension or update your existing extension to work for the web, see "[Web extensions](https://code.visualstudio.com/api/extension-guides/web-extensions)" in the {% data variables.product.prodname_vscode_shortname %} documentation. -Extensions that can run in the {% data variables.product.prodname_serverless %} will appear in the Extensions View and can be installed. If you use Settings Sync, any compatible extensions are also installed automatically. For information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode %} documentation. +Extensions that can run in the {% data variables.product.prodname_serverless %} will appear in the Extensions View and can be installed. If you use Settings Sync, any compatible extensions are also installed automatically. For information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation. ## トラブルシューティング @@ -104,5 +104,5 @@ If you have issues opening the {% data variables.product.prodname_serverless %}, ### Known limitations - The {% data variables.product.prodname_serverless %} is currently supported in Chrome (and various other Chromium-based browsers), Edge, Firefox, and Safari. We recommend that you use the latest versions of these browsers. -- Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "[Known limitations and adaptations](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" section of the {% data variables.product.prodname_vscode %} documentation. +- Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "[Known limitations and adaptations](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" section of the {% data variables.product.prodname_vscode_shortname %} documentation. - `.` may not work to open the {% data variables.product.prodname_serverless %} according to your local keyboard layout. In that case, you can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} by changing the URL from `github.com` to `github.dev`. diff --git a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md index b70b7b9ac2..25194c1493 100644 --- a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md +++ b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -22,11 +22,11 @@ When you create a codespace, you can choose the type of the virtual machine you ![A list of available machine types](/assets/images/help/codespaces/choose-custom-machine-type.png) -If you have your {% data variables.product.prodname_codespaces %} editor preference set to "Visual Studio Code for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used. +If you have your {% data variables.product.prodname_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used. ![The 'prebuilt codespace found' message](/assets/images/help/codespaces/prebuilt-codespace-found.png) -Similarly, if your editor preference is "Visual Studio Code" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for Codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)." +Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for Codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)." After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal: diff --git a/translations/ja-JP/content/communities/moderating-comments-and-conversations/index.md b/translations/ja-JP/content/communities/moderating-comments-and-conversations/index.md index f713efedbb..40e12d3ccb 100644 --- a/translations/ja-JP/content/communities/moderating-comments-and-conversations/index.md +++ b/translations/ja-JP/content/communities/moderating-comments-and-conversations/index.md @@ -16,7 +16,7 @@ children: - /managing-disruptive-comments - /locking-conversations - /limiting-interactions-in-your-repository - - /limiting-interactions-for-your-user-account + - /limiting-interactions-for-your-personal-account - /limiting-interactions-in-your-organization - /tracking-changes-in-a-comment - /managing-how-contributors-report-abuse-in-your-organizations-repository 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-personal-account.md similarity index 93% rename from translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md rename to translations/ja-JP/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md index ec0990dd7e..d4f32f6c40 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-personal-account.md @@ -1,5 +1,5 @@ --- -title: ユーザアカウントの操作を制限する +title: Limiting interactions for your personal account intro: You can temporarily enforce a period of limited activity for certain users in all public repositories owned by your personal account. versions: fpt: '*' @@ -7,6 +7,7 @@ versions: permissions: Anyone can limit interactions for their own personal account. redirect_from: - /github/building-a-strong-community/limiting-interactions-for-your-user-account + - /communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account topics: - Community shortTitle: アカウントのインタラクションの制限 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 72f7b603bc..ae723ab490 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 @@ -22,7 +22,7 @@ shortTitle: リポジトリ内でのインタラクションの制限 {% data reusables.community.types-of-interaction-limits %} -You can also enable activity limitations on all repositories owned by your personal account or an organization. ユーザ全体または Organization 全体の制限が有効になっている場合、そのアカウントが所有する個々のリポジトリのアクティビティを制限することはできません。 For more information, see "[Limiting interactions for your personal account](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account)" and "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)." +You can also enable activity limitations on all repositories owned by your personal account or an organization. ユーザ全体または Organization 全体の制限が有効になっている場合、そのアカウントが所有する個々のリポジトリのアクティビティを制限することはできません。 For more information, see "[Limiting interactions for your personal account](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account)" and "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)." ## リポジトリでのインタラクションを制限する diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md index 61015343ad..b7cdc018d3 100644 --- a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md +++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md @@ -36,9 +36,7 @@ Issue テンプレートは、コントリビューターが Issue の内容を Issue フォームでは、{% data variables.product.prodname_dotcom %} フォームスキーマを使用して、Web フォームフィールドを持つテンプレートを作成できます。 コントリビューターが Issue フォームを使用して Issue をオープンすると、フォーム入力は標準のマークダウン Issue コメントに変換されます。 さまざまな入力タイプを指定し、必要に応じて入力を設定して、コントリビューターがリポジトリで実行可能な Issue をオープンすることができるようにすることができます。 詳しい情報については、「[リポジトリの Issue テンプレートを設定する](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)」および「[Issue フォームの構文](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)」を参照してください。 {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} {% data reusables.repositories.issue-template-config %}詳しい情報については、「[リポジトリ用に Issue テンプレートを設定する](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser)」を参照してください。 -{% endif %} Issue テンプレートは、リポジトリのデフォルトブランチ中の隠しディレクトリ `.github/ISSUE_TEMPLATE` に保存されます。 テンプレートを他のブランチで作成した場合、それをコラボレーターが使うことはできません。 Issue テンプレートのファイル名では大文字と小文字は区別されず、*.md* 拡張子が必要です。{% ifversion fpt or ghec %} Issue フォームで作成された Issue テンプレートには、*.yml* 拡張子が必要です。{% endif %} {% data reusables.repositories.valid-community-issues %} diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md index 7d360b105a..14173e6d51 100644 --- a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md +++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md @@ -21,12 +21,8 @@ shortTitle: 設定 {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} - ## Issue テンプレートを作成する -{% endif %} - {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 3. [Features] セクションの [Issues] の下で、[**Set up templates**] をクリックします。 ![[Start template setup] ボタン](/assets/images/help/repository/set-up-templates.png) @@ -62,7 +58,6 @@ Issueフォームのレンダリングバージョンは次のとおりです。 {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} ## テンプレート選択画面を設定する {% data reusables.repositories.issue-template-config %} @@ -99,7 +94,6 @@ contact_links: {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -{% endif %} ## 参考リンク diff --git a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md index 947bf93f71..3a839ddddb 100644 --- a/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md +++ b/translations/ja-JP/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md @@ -17,7 +17,7 @@ shortTitle: Configure default editor - [Atom](https://atom.io/) - [MacVim](https://macvim-dev.github.io/macvim/) -- [Visual Studio Code](https://code.visualstudio.com/) +- [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) - [Visual Studio Codium](https://vscodium.com/) - [Sublime Text](https://www.sublimetext.com/) - [BBEdit](http://www.barebones.com/products/bbedit/) @@ -44,7 +44,7 @@ shortTitle: Configure default editor {% windows %} - [Atom](https://atom.io/) -- [Visual Studio Code](https://code.visualstudio.com/) +- [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) - [Visual Studio Codium](https://vscodium.com/) - [Sublime Text](https://www.sublimetext.com/) - [ColdFusion Builder](https://www.adobe.com/products/coldfusion-builder.html) 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 329289c1f7..9916fa1ad5 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 @@ -89,7 +89,7 @@ webhook を保護するためにシークレットが必要なアプリケーシ | [`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/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 %} +| [`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 or ghec %} | `vulnerability_alerts` | Grants access to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in a repository. See "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" to learn more. `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 0bc31e054b..7b20e25cbf 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 @@ -239,8 +239,8 @@ While most of your API インタラクションのほとんどは、サーバー * [デプロイメントの一覧表示](/rest/reference/deployments#list-deployments) * [デプロイメントの作成](/rest/reference/deployments#create-a-deployment) -* [Get a deployment](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %} -* [デプロイメントの削除](/rest/reference/deployments#delete-a-deployment){% endif %} +* [Get a deployment](/rest/reference/deployments#get-a-deployment) +* [Delete a deployment](/rest/reference/deployments#delete-a-deployment) #### イベント @@ -422,14 +422,12 @@ While most of your API インタラクションのほとんどは、サーバー * [Organizationのためのpre-receiveフックの強制の削除](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} #### OrganizationのTeamのプロジェクト * [Teamプロジェクトの一覧表示](/rest/reference/teams#list-team-projects) * [プロジェクトのTeamの権限のチェック](/rest/reference/teams#check-team-permissions-for-a-project) * [Teamのプロジェクト権限の追加あるいは更新](/rest/reference/teams#add-or-update-team-project-permissions) * [Teamからのプロジェクトの削除](/rest/reference/teams#remove-a-project-from-a-team) -{% endif %} #### OrganizationのTeamリポジトリ @@ -575,7 +573,7 @@ While most of your API インタラクションのほとんどは、サーバー #### リアクション -{% ifversion fpt or ghes or ghae or ghec %}* [リアクションの削除](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [リアクションの削除](/rest/reference/reactions#delete-a-reaction){% endif %} +* [Delete a reaction](/rest/reference/reactions) * [コミットコメントへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-a-commit-comment) * [コミットコメントへのリアクションの作成](/rest/reference/reactions#create-reaction-for-a-commit-comment) * [Issueへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-an-issue) @@ -587,13 +585,13 @@ While most of your API インタラクションのほとんどは、サーバー * [Teamディスカッションコメントへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) * [Teamディスカッションコメントへのリアクションの作成](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) * [Teamディスカッションへのリアクションの一覧表示](/rest/reference/reactions#list-reactions-for-a-team-discussion) -* [Teamディスカッションへのリアクションの作成](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %} +* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion) * [コミットコメントへのリアクションの削除](/rest/reference/reactions#delete-a-commit-comment-reaction) * [Issueへのリアクションの削除](/rest/reference/reactions#delete-an-issue-reaction) * [コミットコメントへのリアクションの削除](/rest/reference/reactions#delete-an-issue-comment-reaction) * [Pull Requestのコメントへのリアクションの削除](/rest/reference/reactions#delete-a-pull-request-comment-reaction) * [Teamディスカッションへのリアクションの削除](/rest/reference/reactions#delete-team-discussion-reaction) -* [Team ディスカッションのコメントへのリアクションの削除](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} +* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction) #### リポジトリ @@ -707,11 +705,9 @@ While most of your API インタラクションのほとんどは、サーバー * [リポジトリのREADMEの取得](/rest/reference/repos#get-a-repository-readme) * [リポジトリのライセンスの取得](/rest/reference/licenses#get-the-license-for-a-repository) -{% ifversion fpt or ghes or ghae or ghec %} #### リポジトリのイベントのディスパッチ * [リポジトリディスパッチイベントの作成](/rest/reference/repos#create-a-repository-dispatch-event) -{% 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 fc1883a9d7..473b1175ea 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 @@ -338,7 +338,7 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr * "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" * "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" -* "[Device flow errors](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +* "[Device flow errors](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} * "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} ## Further reading diff --git a/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md index eec4a49f78..b2ddf4a8d6 100644 --- a/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md +++ b/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md @@ -84,7 +84,7 @@ Keep these ideas in mind when using personal access tokens: * You can perform one-off cURL requests. * You can run personal scripts. * Don't set up a script for your whole team or company to use. -* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %} +* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} * Do set an expiration for your personal access tokens, to help keep your information secure.{% endif %} ## Determining which integration to build diff --git a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md index f711c1f02b..a0fae35e8f 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md @@ -89,4 +89,4 @@ end * プレーンな `==` 演算子を使用することは**お勧めしません**。 [`secure_compare`][secure_compare] のようなメソッドは、「一定時間」の文字列比較を実行します。これは、通常の等式演算子に対する特定のタイミング攻撃を軽減するのに役立ちます。 -[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare +[secure_compare]: https://rubydoc.info/github/rack/rack/main/Rack/Utils:secure_compare diff --git a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 070c805e26..ba0df5ca7c 100644 --- a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -353,10 +353,10 @@ webhook イベントは、登録したドメインの特異性に基づいてト ### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| ------------ | ------------------------------------------- | --------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} -| `action` | `string` | 実行されたアクション。 `created` を指定可。{% endif %} -| `deployment` | `オブジェクト` | The [deployment](/rest/reference/deployments#list-deployments). | +| キー | 種類 | 説明 | +| ------------ | -------- | -------------------------------------------------------- | +| `action` | `string` | 実行されたアクション。 `created `になりうる。 | +| `deployment` | `オブジェクト` | [デプロイメント](/rest/reference/deployments#list-deployments)。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -378,14 +378,14 @@ webhook イベントは、登録したドメインの特異性に基づいてト ### webhook ペイロードオブジェクト -| キー | 種類 | 説明 | -| ---------------------------------- | ------------------------------------------- | --------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} -| `action` | `string` | 実行されたアクション。 `created` を指定可。{% endif %} -| `deployment_status` | `オブジェクト` | The [deployment status](/rest/reference/deployments#list-deployment-statuses). | -| `deployment_status["state"]` | `string` | 新しい状態。 `pending`、`success`、`failure`、`error` のいずれかを指定可。 | -| `deployment_status["target_url"]` | `string` | ステータスに追加されたオプションのリンク。 | -| `deployment_status["description"]` | `string` | オプションの人間可読の説明がステータスに追加。 | -| `deployment` | `オブジェクト` | The [deployment](/rest/reference/deployments#list-deployments) that this status is associated with. | +| キー | 種類 | 説明 | +| ---------------------------------- | -------- | -------------------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション。 `created `になりうる。 | +| `deployment_status` | `オブジェクト` | [デプロイメントステータス](/rest/reference/deployments#list-deployment-statuses)。 | +| `deployment_status["state"]` | `string` | 新しい状態。 `pending`、`success`、`failure`、`error` のいずれかを指定可。 | +| `deployment_status["target_url"]` | `string` | ステータスに追加されたオプションのリンク。 | +| `deployment_status["description"]` | `string` | オプションの人間可読の説明がステータスに追加。 | +| `deployment` | `オブジェクト` | このステータスが関連付けられている [デプロイメント](/rest/reference/deployments#list-deployments)。 | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1154,7 +1154,6 @@ GitHub Marketplace の購入に関連するアクティビティ。 {% data reus {{ webhookPayloadsForCurrentVersion.release.published }} -{% ifversion fpt or ghes or ghae or ghec %} ## repository_dispatch このイベントは、{% data variables.product.prodname_github_app %} が「[リポジトリディスパッチイベントの作成](/rest/reference/repos#create-a-repository-dispatch-event)」エンドポイントに `POST` リクエストを送信したときに発生します。 @@ -1166,7 +1165,6 @@ GitHub Marketplace の購入に関連するアクティビティ。 {% data reus ### webhook ペイロードの例 {{ webhookPayloadsForCurrentVersion.repository_dispatch }} -{% endif %} ## リポジトリ @@ -1490,7 +1488,7 @@ The security advisory dataset also powers the GitHub {% data variables.product.p {{ webhookPayloadsForCurrentVersion.workflow_dispatch }} {% endif %} -{% ifversion fpt or ghes > 3.2 or ghec or ghae-issue-4462 %} +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## workflow_job diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md index 3e56b15403..95f3bf4e06 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md @@ -1,39 +1,39 @@ --- title: About using Visual Studio Code with GitHub Classroom shortTitle: About using Visual Studio Code -intro: 'You can configure Visual Studio Code as the preferred editor for assignments in {% data variables.product.prodname_classroom %}.' +intro: 'You can configure {% data variables.product.prodname_vscode %} as the preferred editor for assignments in {% data variables.product.prodname_classroom %}.' versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/about-using-vs-code-with-github-classroom --- -## About Visual Studio Code +## {% data variables.product.prodname_vscode %}について -Visual Studio Code is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. With the [GitHub Classroom extension for Visual Studio Code](https://aka.ms/classroom-vscode-ext), students can easily browse, edit, submit, collaborate, and test their Classroom Assignments. For more information about IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)." +{% data variables.product.prodname_vscode %} is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. With the [GitHub Classroom extension for {% data variables.product.prodname_vscode_shortname %}](https://aka.ms/classroom-vscode-ext), students can easily browse, edit, submit, collaborate, and test their Classroom Assignments. For more information about IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)." ### Your student's editor of choice -The GitHub Classroom integration with Visual Studio Code provides students with an extension pack which contains: +The GitHub Classroom integration with {% data variables.product.prodname_vscode_shortname %} provides students with an extension pack which contains: 1. [GitHub Classroom Extension](https://aka.ms/classroom-vscode-ext) with custom abstractions that make it easy for students to navigate getting started. 2. [Visual Studio Live Share Extension](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare-pack) integrating into a student view for easy access to teaching assistants and classmates for help and collaboration. 3. [GitHub Pull Request Extension](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) allowing students to see feedback from their instructors within the editor. -### How to launch the assignment in Visual Studio Code -When creating an assignment, Visual Studio Code can be added as the preferred editor for an assignment. For more details, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)." +### How to launch the assignment in {% data variables.product.prodname_vscode_shortname %} +When creating an assignment, {% data variables.product.prodname_vscode_shortname %} can be added as the preferred editor for an assignment. For more details, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)." -This will include an "Open in Visual Studio Code" badge in all student repositories. This badge handles installing Visual Studio Code, the Classroom extension pack, and opening to the active assignment with one click. +This will include an "Open in {% data variables.product.prodname_vscode_shortname %}" badge in all student repositories. This badge handles installing {% data variables.product.prodname_vscode_shortname %}, the Classroom extension pack, and opening to the active assignment with one click. {% note %} -**Note:** The student must have Git installed on their computer to push code from Visual Studio Code to their repository. This is not automatically installed when clicking the **Open in Visual Studio Code** button. The student can download Git from [here](https://git-scm.com/downloads). +**Note:** The student must have Git installed on their computer to push code from {% data variables.product.prodname_vscode_shortname %} to their repository. This is not automatically installed when clicking the **Open in {% data variables.product.prodname_vscode_shortname %}** button. The student can download Git from [here](https://git-scm.com/downloads). {% endnote %} ### How to use GitHub Classroom extension pack The GitHub Classroom extension has two major components: the 'Classrooms' view and the 'Active Assignment' view. -When the student launches the extension for the first time, they are automatically navigated to the Explorer tab in Visual Studio Code, where they can see the "Active Assignment" view alongside the tree-view of files in the repository. +When the student launches the extension for the first time, they are automatically navigated to the Explorer tab in {% data variables.product.prodname_vscode_shortname %}, where they can see the "Active Assignment" view alongside the tree-view of files in the repository. ![GitHub Classroom Active Assignment View](/assets/images/help/classroom/vs-code-active-assignment.png) diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md index b623657437..0e61e57eb7 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md @@ -24,7 +24,7 @@ After a student accepts an assignment with an IDE, the README file in the studen | :- | :- | | {% data variables.product.prodname_github_codespaces %} | "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)" | | Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | -| Visual Studio Code | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace | +| {% data variables.product.prodname_vscode %} | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace | We know cloud IDE integrations are important to your classroom and are working to bring more options. 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 index c053ec150b..723a5600c9 100644 --- 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 @@ -14,7 +14,7 @@ shortTitle: Extensions & integrations ## エディタツール -Atom、Unity、Visual Studio などのサードパーティのエディタツール内で {% data variables.product.product_name %} リポジトリに接続できます。 +You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and {% data variables.product.prodname_vs %}. ### {% data variables.product.product_name %} for Atom @@ -24,13 +24,13 @@ Atom、Unity、Visual Studio などのサードパーティのエディタツー {% 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 {% data variables.product.prodname_vs %} -{% 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)を参照してください。 +With the {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} extension, you can work in {% data variables.product.product_name %} repositories without leaving {% data variables.product.prodname_vs %}. For more information, see the official {% data variables.product.prodname_vs %} extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs). -### {% data variables.product.prodname_dotcom %} for Visual Studio Code +### {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} -{% 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)を参照してください。 +With the {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} extension, you can review and manage {% data variables.product.product_name %} pull requests in {% data variables.product.prodname_vscode_shortname %}. For more information, see the official {% data variables.product.prodname_vscode_shortname %} extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github). ## プロジェクト管理ツール diff --git a/translations/ja-JP/content/get-started/exploring-projects-on-github/following-organizations.md b/translations/ja-JP/content/get-started/exploring-projects-on-github/following-organizations.md index 0ecad65bc7..8599a83369 100644 --- a/translations/ja-JP/content/get-started/exploring-projects-on-github/following-organizations.md +++ b/translations/ja-JP/content/get-started/exploring-projects-on-github/following-organizations.md @@ -15,7 +15,7 @@ topics: ## About followers on {% data variables.product.product_name %} -When you follow organizations, you'll see their public activity on your personal dashboard. 詳細は「[パーソナルダッシュボードについて](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)」を参照してください。 +When you follow organizations, you'll see their public activity on your personal dashboard. 詳細は「[パーソナルダッシュボードについて](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)」を参照してください。 You can unfollow an organization if you do not wish to see their {% ifversion fpt or ghec %}public{% endif %} activity on {% data variables.product.product_name %}. diff --git a/translations/ja-JP/content/get-started/exploring-projects-on-github/following-people.md b/translations/ja-JP/content/get-started/exploring-projects-on-github/following-people.md index 36cad648f0..5dca93b5d1 100644 --- a/translations/ja-JP/content/get-started/exploring-projects-on-github/following-people.md +++ b/translations/ja-JP/content/get-started/exploring-projects-on-github/following-people.md @@ -17,7 +17,7 @@ topics: ## About followers on {% data variables.product.product_name %} -When you follow people, you'll see their public activity on your personal dashboard.{% ifversion fpt or ghec %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you.{% endif %} For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)." +When you follow people, you'll see their public activity on your personal dashboard.{% ifversion fpt or ghec %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you.{% endif %} For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)." You can unfollow someone if you do not wish to see their public activity on {% data variables.product.product_name %}. diff --git a/translations/ja-JP/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md b/translations/ja-JP/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md index cccad934c8..c787a3af40 100644 --- a/translations/ja-JP/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md +++ b/translations/ja-JP/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md @@ -26,7 +26,7 @@ You can search, sort, and filter your starred repositories and topics on your {% Star を付けることで、リポジトリやトピックが後で見つけやすくなります。 {% data variables.explore.your_stars_page %} にアクセスすると、Star 付きのリポジトリとトピックを確認することができます。 {% ifversion fpt or ghec %} -リポジトリとトピックに Star を付けることで、{% data variables.product.product_name %} 上で類似のプロジェクトを見つけることができます。 When you star repositories or topics, {% data variables.product.product_name %} may recommend related content on your personal dashboard. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)" and "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)." +リポジトリとトピックに Star を付けることで、{% data variables.product.product_name %} 上で類似のプロジェクトを見つけることができます。 When you star repositories or topics, {% data variables.product.product_name %} may recommend related content on your personal dashboard. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)" and "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)." {% endif %} リポジトリに Star を付けるということは、リポジトリメンテナに対してその作業についての感謝を示すことでもあります。 {% data variables.product.prodname_dotcom %} のリポジトリランキングの多くは、リポジトリに付けられた Star の数を考慮しています。 また、[Explore](https://github.com/explore) は、リポジトリに付けられた Star の数に基づいて、人気のあるリポジトリを表示しています。 diff --git a/translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md index b6f29e9423..e7ad7cc18e 100644 --- a/translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md +++ b/translations/ja-JP/content/get-started/getting-started-with-git/about-remote-repositories.md @@ -81,14 +81,10 @@ SSH URL を使用して、`git clone`、`git fetch`、`git pull` または `git {% endtip %} -{% ifversion fpt or ghes or ghae or ghec %} - ## {% data variables.product.prodname_cli %} を使ってクローンを作成する {% data variables.product.prodname_cli %} をインストールして、ターミナルで {% data variables.product.product_name %} ワークフローを使用することもできます。 詳しい情報については、「[{% data variables.product.prodname_cli %} について](/github-cli/github-cli/about-github-cli)」を参照してください。 -{% endif %} - {% ifversion not ghae %} ## Subversion を使って複製する 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 5d4cec10c0..873a909638 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 @@ -28,9 +28,9 @@ shortTitle: Associate text editors $ git config --global core.editor "atom --wait" ``` -## エディタとして Visual Studio Code を使う +## Using {% data variables.product.prodname_vscode %} as your editor -1. [Visual Studio Code](https://code.visualstudio.com/) (VS Code) をインストールします。 詳細は、VS Code のドキュメンテーションで「[Visual Studio Code の設定](https://code.visualstudio.com/Docs/setup/setup-overview)」を参照してください。 +1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.command_line.open_the_multi_os_terminal %} 3. 以下のコマンドを入力してください: ```shell @@ -68,9 +68,9 @@ shortTitle: Associate text editors $ git config --global core.editor "atom --wait" ``` -## エディタとして Visual Studio Code を使う +## Using {% data variables.product.prodname_vscode %} as your editor -1. [Visual Studio Code](https://code.visualstudio.com/) (VS Code) をインストールします。 詳細は、VS Code のドキュメンテーションで「[Visual Studio Code の設定](https://code.visualstudio.com/Docs/setup/setup-overview)」を参照してください。 +1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.command_line.open_the_multi_os_terminal %} 3. 以下のコマンドを入力してください: ```shell @@ -107,9 +107,9 @@ shortTitle: Associate text editors $ git config --global core.editor "atom --wait" ``` -## エディタとして Visual Studio Code を使う +## Using {% data variables.product.prodname_vscode %} as your editor -1. [Visual Studio Code](https://code.visualstudio.com/) (VS Code) をインストールします。 詳細は、VS Code のドキュメンテーションで「[Visual Studio Code の設定](https://code.visualstudio.com/Docs/setup/setup-overview)」を参照してください。 +1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.command_line.open_the_multi_os_terminal %} 3. 以下のコマンドを入力してください: ```shell 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 7616cc276e..8eaea418ac 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 @@ -30,7 +30,7 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th - **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository.{% if secret-scanning-push-protection %} If push protection is enabled, also detects secrets when they are pushed to your repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)" and "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."{% else %} For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)."{% endif %} -{% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4864 %} +{% ifversion fpt or ghes > 3.1 or ghec or ghae %} - **Dependency review** - 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 %} @@ -113,4 +113,4 @@ For more information on starter workflows, see "[Setting up {% data variables.pr - "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)" {% endif %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/ja-JP/content/get-started/learning-about-github/about-versions-of-github-docs.md b/translations/ja-JP/content/get-started/learning-about-github/about-versions-of-github-docs.md index 76ba9ab22e..7a247af157 100644 --- a/translations/ja-JP/content/get-started/learning-about-github/about-versions-of-github-docs.md +++ b/translations/ja-JP/content/get-started/learning-about-github/about-versions-of-github-docs.md @@ -37,7 +37,7 @@ In a wide browser window, there is no text that immediately follows the {% data On {% data variables.product.prodname_dotcom_the_website %}, each account has its own plan. Each personal account has an associated plan that provides access to certain features, and each organization has a different associated plan. If your personal account is a member of an organization on {% data variables.product.prodname_dotcom_the_website %}, you may have access to different features when you use resources owned by that organization than when you use resources owned by your personal account. 詳しい情報については、「[{% data variables.product.prodname_dotcom %}アカウントの種類](/get-started/learning-about-github/types-of-github-accounts)」を参照してください。" -If you don't know whether an organization uses {% data variables.product.prodname_ghe_cloud %}, ask an organization owner. For more information, see "[Viewing people's roles in an organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)." +If you don't know whether an organization uses {% data variables.product.prodname_ghe_cloud %}, ask an organization owner. For more information, see "[Viewing people's roles in an organization](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)." ### {% data variables.product.prodname_ghe_server %} diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md index 4549a19de7..32343e3474 100644 --- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -75,7 +75,7 @@ For more information about how to authenticate to {% data variables.product.prod | ------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Browse to {% data variables.product.prodname_dotcom_the_website %} | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests. | This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally. | | {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} は、コマンドライン上でテキストコマンドを使うのではなく、ビジュアルインターフェースを使って、あなたの {% data variables.product.prodname_dotcom_the_website %} ワークフローを拡張し簡略化します。 For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}. | -| IDE or text editor | You can set a default text editor, like [Atom](https://atom.io/) or [Visual Studio Code](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. | +| IDE or text editor | You can set a default text editor, like [Atom](https://atom.io/) or [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. | | Command line, with or without {% data variables.product.prodname_cli %} | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."

{% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line. | | {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)." | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. | ### 4. Writing on {% data variables.product.product_name %} diff --git a/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md b/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md index 73f5cb509b..7f7636461a 100644 --- a/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md +++ b/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md @@ -117,7 +117,6 @@ This example shows the {% data variables.product.prodname_discussions %} welcome This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository. {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} ### Scenarios for team discussions - I have a question that's not necessarily related to specific files in the repository. @@ -140,8 +139,6 @@ The `octocat` team member posted a team discussion, informing the team of variou - There is a blog post describing how the teams use {% data variables.product.prodname_actions %} to produce their docs. - Material about the April All Hands is now available for all team members to view. -{% endif %} - ## 次のステップ These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs. 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 62d48fa654..c975ff4a3d 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 @@ -153,7 +153,7 @@ These commands are available from all scopes. | `New organization` | Create a new organization. 詳しい情報については、「[新しい Organization をゼロから作成する](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)」を参照してください。 | | `新規プロジェクト` | Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)." | | `New repository` | Create a new repository from scratch. 詳しい情報については「[新しいリポジトリの作成](/repositories/creating-and-managing-repositories/creating-a-new-repository)」を参照してください。 | -| `Switch theme to ` | Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." | +| `Switch theme to ` | Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)." | ### Organization commands diff --git a/translations/ja-JP/content/get-started/using-github/github-mobile.md b/translations/ja-JP/content/get-started/using-github/github-mobile.md index e99da062ad..fe88929e61 100644 --- a/translations/ja-JP/content/get-started/using-github/github-mobile.md +++ b/translations/ja-JP/content/get-started/using-github/github-mobile.md @@ -25,10 +25,13 @@ With {% data variables.product.prodname_mobile %} you can: - Read, review, and collaborate on issues and pull requests - Search for, browse, and interact with users, repositories, and organizations - Receive a push notification when someone mentions your username -{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication{% endif %} +{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication +- Verify your sign in attempts on unrecognized devices{% endif %} For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)." +{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)." {% endif %} + ## Installing {% data variables.product.prodname_mobile %} To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% data variables.product.prodname_mobile %}](https://github.com/mobile). 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 1d70990043..40d24049cd 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 @@ -20,7 +20,7 @@ versions: Typing ? on {% data variables.product.prodname_dotcom %} brings up a dialog box that lists the keyboard shortcuts available for that page. マウスを使用して移動しなくても、これらのキーボードショートカットを使用して、サイト全体でアクションを実行できます。 {% if keyboard-shortcut-accessibility-setting %} -You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see "[Managing accessibility settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings)."{% endif %} +You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see "[Managing accessibility settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings)."{% endif %} 以下は利用可能なキーボードショートカットのリストです: {% if command-palette %} @@ -28,11 +28,11 @@ 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 | 通知に移動します。 詳しい情報については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」を参照してください。 | +| Esc | ユーザ、Issue、またはプルリクエストのホバーカードにフォーカスすると、ホバーカードが閉じ、ホバーカードが含まれている要素に再フォーカスします | {% if command-palette %} @@ -106,7 +106,6 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a {% endif %} | R | 返信で選択したテキストを引用します。 For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." | - ## Issue およびプルリクエストのリスト | キーボードショートカット | 説明 | @@ -135,16 +134,15 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a ## プルリクエストの変更 -| キーボードショートカット | 説明 | -| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 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 %} +| キーボードショートカット | 説明 | +| ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 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**. | +| 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)」を参照してください。 | ## プロジェクトボード @@ -200,21 +198,14 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a {% endif %} ## 通知 -{% ifversion fpt or ghes or ghae or ghec %} + | キーボードショートカット | 説明 | | ----------------------------- | ------------ | | E | 完了済としてマークします | | Shift+U | 未読としてマークします | -| Shift+I | 既読としてマークします | +| Shift+I | 既読としてマーク | | Shift+M | サブスクライブ解除します | -{% else %} - -| キーボードショートカット | 説明 | -| -------------------------------------------- | ------------ | -| E or I or Y | 既読としてマークします | -| Shift+M | スレッドをミュートします | -{% endif %} ## ネットワークグラフ diff --git a/translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md index 00a5333f72..ce5486664c 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ b/translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md @@ -60,7 +60,6 @@ Gist supports mapping GeoJSON files. These maps are displayed in embedded gists, Follow the steps below to create a gist. -{% ifversion fpt or ghes or ghae or ghec %} {% note %} You can also create a gist using the {% data variables.product.prodname_cli %}. For more information, see "[`gh gist create`](https://cli.github.com/manual/gh_gist_create)" in the {% data variables.product.prodname_cli %} documentation. @@ -68,7 +67,6 @@ You can also create a gist using the {% data variables.product.prodname_cli %}. Alternatively, you can drag and drop a text file from your desktop directly into the editor. {% endnote %} -{% endif %} 1. Sign in to {% data variables.product.product_name %}. 2. Navigate to your {% data variables.gists.gist_homepage %}. diff --git a/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index 348416cb75..47e061b388 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -29,7 +29,6 @@ When you use two or more headings, GitHub automatically generates a table of con ![Screenshot highlighting the table of contents icon](/assets/images/help/repository/headings_toc.png) - ## スタイル付きテキスト コメントフィールドと `.md` ファイルでは、太字、斜体、または取り消し線のテキストで強調を示すことができます。 @@ -235,7 +234,7 @@ If a task list item description begins with a parenthesis, you'll need to escape ## 人や Team のメンション -{% data variables.product.product_name %}上の人あるいは [Team](/articles/setting-up-teams/) は、@ に加えてユーザ名もしくは Team 名を入力することでメンションできます。 これにより通知がトリガーされ、会話に注意が向けられます。 コメントを編集してユーザ名や Team 名をメンションすれば、人々に通知を受信してもらえます。 通知の詳細は、{% 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 %}」を参照してください。 +{% data variables.product.product_name %}上の人あるいは [Team](/articles/setting-up-teams/) は、@ に加えてユーザ名もしくは Team 名を入力することでメンションできます。 これにより通知がトリガーされ、会話に注意が向けられます。 コメントを編集してユーザ名や Team 名をメンションすれば、人々に通知を受信してもらえます。 通知に関する詳しい情報については「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」を参照してください。 {% note %} @@ -296,7 +295,7 @@ For more information about building a {% data variables.product.prodname_github_ テキスト行の間に空白行を残すことで、新しいパラグラフを作成できます。 -{% ifversion fpt or ghae-issue-5180 or ghes > 3.2 or ghec %} +{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## Footnotes You can add footnotes to your content by using this bracket syntax: 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 1893824f58..095ed3c125 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 @@ -15,7 +15,7 @@ topics: ## 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`. +To link a pull request to an issue to show that a fix is in progress and to 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`. * close * closes diff --git a/translations/ja-JP/content/github/copilot/about-github-copilot-telemetry.md b/translations/ja-JP/content/github/copilot/about-github-copilot-telemetry.md index 7139ed503e..631a9815a4 100644 --- a/translations/ja-JP/content/github/copilot/about-github-copilot-telemetry.md +++ b/translations/ja-JP/content/github/copilot/about-github-copilot-telemetry.md @@ -9,7 +9,7 @@ versions: ## What data is collected -Data collected is described in the "[{% data variables.product.prodname_copilot %} Telemetry Terms](/github/copilot/github-copilot-telemetry-terms)." In addition, the {% data variables.product.prodname_copilot %} extension/plugin collects activity from the user's Integrated Development Environment (IDE), tied to a timestamp, and metadata collected by the extension/plugin telemetry package. When used with Visual Studio Code, IntelliJ, NeoVIM, or other IDEs, {% data variables.product.prodname_copilot %} collects the standard metadata provided by those IDEs. +Data collected is described in the "[{% data variables.product.prodname_copilot %} Telemetry Terms](/github/copilot/github-copilot-telemetry-terms)." In addition, the {% data variables.product.prodname_copilot %} extension/plugin collects activity from the user's Integrated Development Environment (IDE), tied to a timestamp, and metadata collected by the extension/plugin telemetry package. When used with {% data variables.product.prodname_vscode %}, IntelliJ, NeoVIM, or other IDEs, {% data variables.product.prodname_copilot %} collects the standard metadata provided by those IDEs. ## How the data is used by {% data variables.product.company_short %} diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md index 37d11d2806..300f1beadf 100644 --- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md +++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md @@ -30,8 +30,8 @@ shortTitle: ボード上のカードのフィルタ - `status:pending`、`status:success`、または `status:failure` を使用して、カードをチェックステータスでフィルタリングする - `type:issue`、`type:pr`、または `type:note` を使用して、カードをタイプでフィルタリングする - `is:open`、`is:closed`、または `is:merged`と、`is:issue`、`is:pr`、または `is:note` とを使用して、カードをステータスとタイプでフィルタリングする -- `linked:pr`を使用してクローズしているリファレンスによってプルリクエストにリンクされている Issue でカードをフィルタリングする{% ifversion fpt or ghes or ghae or ghec %} -- `repo:ORGANIZATION/REPOSITORY` を使用して、Organization 全体のプロジェクトボード内のリポジトリでカードをフィルタリングする{% endif %} +- Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr` +- `repo:ORGANIZATION/REPOSITORY` を使用して、Organization 全体のプロジェクトボード内のリポジトリでカードをフィルタリングする 1. フィルタリングしたいカードが含まれるプロジェクトボードに移動します。 2. プロジェクトのカード列の上で、[Filter cards] 検索バーをクリックして検索クエリを入力し、カードをフィルタリングします。 ![カードのフィルタリング検索バー](/assets/images/help/projects/filter-card-search-bar.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 0165363e5f..3caa420549 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 @@ -22,7 +22,7 @@ topics: Issueを使って、開発が行われる{% data variables.product.company_short %}上での作業を追跡できます。 他のIssueもしくはPull Request内のIssueにメンションすると、そのIssueのタイムラインにはクロスリファレンスが反映され、関連する作業を追跡できるようになります。 作業が進行中であることを示すために、Pull RequestにIssueをリンクできます。 Pull Requestがマージされると、リンクされたIssueは自動的にクローズされます。 -For more information on keywords, see "[Linking a pull request to an issue](issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)." +キーワードに関する詳しい情報については「[Pull RequestのIssueへのリンク](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)」を参照してください。 ## 素早いIssueの作成 @@ -36,7 +36,7 @@ Issueは様々な方法で作成できるので、ワークフローで最も便 ## 最新情報の確認 -Issueの最新のコメントの情報を得ておきたい場合には、Issueをサブスクライブして最新のコメントに関する通知を受け取ることができます。 サブスクライブした Issue の最新の更新へのリンクを素早く見つけるには、ダッシュボードにアクセスしてください。 詳しい情報については{% 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 %}及び「[個人ダッシュボードについて](/articles/about-your-personal-dashboard)」を参照してください。 +Issueの最新のコメントの情報を得ておきたい場合には、Issueをサブスクライブして最新のコメントに関する通知を受け取ることができます。 サブスクライブした Issue の最新の更新へのリンクを素早く見つけるには、ダッシュボードにアクセスしてください。 For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[About your personal dashboard](/articles/about-your-personal-dashboard)." ## コミュニティの管理 diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md index cfb29011bc..bfb120007f 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md @@ -19,7 +19,9 @@ shortTitle: Issue及びPRのアサイン ## Issue およびPull Requestをアサインされた人について -自身、該当する Issue またはプルリクエストにコメントした任意の人、リポジトリへの書き込み権限がある任意の人、およびリポジトリの読み取り権限がある Organization メンバーを含めて、最大 10 人まで各 Issue またはプルリクエストにアサインできます。 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/articles/access-permissions-on-github)」を参照してください。 +自身、該当する Issue またはPull Requestにコメントした任意の人、リポジトリへの書き込み権限がある任意の人、およびリポジトリの読み取り権限がある Organization メンバーを含めて、複数人を各 Issue またはPull Requestにアサインできます。 詳細は「[{% data variables.product.prodname_dotcom %} 上のアクセス権限](/articles/access-permissions-on-github)」を参照してください。 + +パブリックリポジトリのIssue及びPull Request、そして有料アカウントのプライベートリポジトリでは、最大10人を割り当てできます。 無料プランのプライベートリポジトリでは、IssueあるいはPull Requestごとに1人に制限されます。 ## 個別の Issue またはPull Requestを割り当てる 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 1cc1f3df5c..d196d10033 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 @@ -173,13 +173,11 @@ Issue およびPull Requestの検索用語により、次のことができま {% endtip %} {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} Issueについては、以下も検索に利用できます。 -- クローズしているリファレンス`linked:pr`によってPull RequestにリンクされているIssueのフィルタリング -{% endif %} +- クローズしているリファレンス`linked:pr`によってプルリクエストにリンクされているIssueのフィルタリング -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` @@ -188,8 +186,8 @@ Pull Requestについては、検索を利用して以下の操作もできま - [レビュー担当者](/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 %} +- レビューを要求されたチームによるプルリクエストのフィルタリング: `state:open type:pr team-review-requested:github/atom` +- プルリクエストでクローズできるIssueにリンクされているプルリクエストのフィルタリング: `linked:issue` ## Issue およびPull Requestをソートする @@ -211,10 +209,9 @@ Pull Requestについては、検索を利用して以下の操作もできま ソートの選択を解除するには、[**Sort**] > [**Newest**] をクリックします。 - ## フィルターを共有する -一定の Issue およびPull Requestをフィルタリングする場合、ブラウザの URL は、次の表示にマッチするように自動的に更新されます。 +一定の Issue およびプルリクエストをフィルタリングする場合、ブラウザの URL は、次の表示にマッチするように自動的に更新されます。 Issue が生成した URL は、どのユーザにも送れます。そして、あなたが見ているフィルタビューと同じフィルタで表示できます。 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 411ae74f26..3b37ed1b82 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 @@ -27,7 +27,7 @@ shortTitle: IssueへのPRのリンク ## リンクされたIssueとPull Requestについて -{% ifversion fpt or ghes or ghae or ghec %}手動で、または{% endif %}Pull Requestの説明でサポートされているキーワードを使用して、IssueをPull Requestにリンクすることができます。 +You can link an issue to a pull request manually or using a supported keyword in the pull request description. Pull Requestが対処するIssueにそのPull Requestをリンクすると、コラボレータは、誰かがそのIssueに取り組んでいることを確認できます。 @@ -35,7 +35,7 @@ Pull Requestが対処するIssueにそのPull Requestをリンクすると、コ ## キーワードを使用してPull RequestをIssueにリンクする -You can link a pull request to an issue by using a supported keyword in the pull request's description or in a commit message. The pull request **must be** on the default branch. +Pull Requestの説明もしくはコミットメッセージ中でサポートされているキーワードを使い、Pull RequestをIssueへリンクできます。 Pull Requestはデフォルトブランチに**ある必要があります**。 * close * closes @@ -47,7 +47,7 @@ You can link a pull request to an issue by using a supported keyword in the pull * resolves * resolved -他のPull RequestでPull Requestのコメントを参照するためにキーワードを使用すると、Pull Requestはリンクされます。 Merging the referencing pull request also closes the referenced pull request. +他のPull RequestでPull Requestのコメントを参照するためにキーワードを使用すると、Pull Requestはリンクされます。 参照元のPull Requestをマージすると、参照先のPull Requestもクローズされます。 クローズするキーワードの構文は、IssueがPull Requestと同じリポジトリにあるかどうかによって異なります。 @@ -57,16 +57,15 @@ You can link a pull request to an issue by using a supported keyword in the pull | 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 %}手動でリンクを解除できるのは、手動でリンクされたPull Requestだけです。 キーワードを使用してリンクしたIssueのリンクを解除するには、Pull Requestの説明を編集してそのキーワードを削除する必要があります。{% endif %} +Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword. クローズするキーワードは、コミットメッセージでも使用できます。 デフォルトブランチにコミットをマージするとIssueはクローズされますが、そのコミットを含むPull Requestは、リンクされたPull Requestとしてリストされません。 -{% ifversion fpt or ghes or ghae or ghec %} ## 手動でPull RequestをIssueにリンクする -リポジトリへの書き込み権限があるユーザなら誰でも、手動でPull RequestをIssueにリンクできます。 +リポジトリへの書き込み権限があるユーザなら誰でも、手動でプルリクエストをIssueにリンクできます。 -手動で1つのPull Requestごとに最大10個のIssueをリンクできます。 IssueとPull Requestは同じリポジトリになければなりません。 +手動で1つのプルリクエストごとに最大10個のIssueをリンクできます。 Issueとプルリクエストは同じリポジトリになければなりません。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} @@ -77,7 +76,6 @@ You can link a pull request to an issue by using a supported keyword in the pull 4. 右のサイドバーで、[**Linked issues**] をクリックします。 ![右サイドバーの [Linked issues]](/assets/images/help/pull_requests/linked-issues.png) {% endif %} 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/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 25bc309b45..cdb1222e30 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 %}「[サブスクリプションを表示する](/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 %}」 +- "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching)" 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 074c7c7daa..5c9109c0e0 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 @@ -163,7 +163,7 @@ topics: 6. タイプとして**Single select（単一選択）**を指定した場合は、選択肢を入力してください。 7. タイプとして**Iteration（繰り返し）**を指定した場合は、最初の繰り返しの日付と、繰り返しの期間を入力してください。 3つの繰り返しが自動的に作成され、プロジェクトの設定ページで繰り返しを追加できます。 -You can also edit your custom fields. +カスタムフィールドを編集することもできます。 {% data reusables.projects.project-settings %} 1. **Fields（フィールド）**の下で、編集したいフィールドを選択してください。 diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md index ea8baf685e..f330154a85 100644 --- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -35,7 +35,7 @@ shortTitle: Organizationダッシュボード ニュースフィードの [All activity] セクションでは、Organization 内の他の Team やリポジトリからの更新情報を見ることができます。 -[All activity] セクションは、Organization 内のすべての最近のアクティビティを表示します。これにはあなたがサブスクライブしていないリポジトリでのアクティビティや、フォローしていない人々のアクティビティも含まれます。 詳細は、{% ifversion fpt or ghes or ghae or ghec %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}」[リポジトリの Watch と Watch 解除](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}」および「[人をフォローする](/articles/following-people)」を参照してください。 +[All activity] セクションは、Organization 内のすべての最近のアクティビティを表示します。これにはあなたがサブスクライブしていないリポジトリでのアクティビティや、フォローしていない人々のアクティビティも含まれます。 For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[Following people](/articles/following-people)." たとえば Organization のニュースフィードは Organization 内の誰かが以下のようなことをしたときに 更新情報を知らせます: - 新しいブランチを作成する diff --git a/translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md index 04845b1e72..aa01ec69db 100644 --- a/translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md +++ b/translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -32,7 +32,7 @@ When someone posts or replies to a public discussion on a team's page, members o {% tip %} -**Tip:** Depending on your notification settings, you'll receive updates by email, the web notifications page on {% data variables.product.product_name %}, or both. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications)" and "[About web notifications](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}." +**Tip:** Depending on your notification settings, you'll receive updates by email, the web notifications page on {% data variables.product.product_name %}, or both. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)." {% endtip %} @@ -40,7 +40,7 @@ By default, if your username is mentioned in a team discussion, you'll receive n To turn off notifications for team discussions, you can unsubscribe to a specific discussion post or change your notification settings to unwatch or completely ignore a specific team's discussions. You can subscribe to notifications for a specific discussion post even if you're unwatching that team's discussions. -For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Subscribing to and unsubscribing from notifications](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" and "[Nested teams](/articles/about-teams/#nested-teams)." +For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)" and "[Nested teams](/articles/about-teams/#nested-teams)." {% ifversion fpt or ghec %} 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 index 8fd6ad0d77..31574c549c 100644 --- 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 @@ -162,5 +162,5 @@ You can manage access to {% data variables.product.prodname_GH_advanced_security - "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %} - "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %} -- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae-issue-4864 %} +- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae %} - "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)"{% endif %} 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 index 40c99ceccc..401665144c 100644 --- 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 @@ -41,7 +41,7 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing. | [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. | -| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %} | [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/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.{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %} | [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." @@ -61,8 +61,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | {% endif %} | [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion ghec %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %} -| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} +| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %} +| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization. | [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps. | [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %} | [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} @@ -75,7 +75,7 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae or ghec %} | [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% if secret-scanning-audit-log-custom-patterns %} | [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %} | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %} | [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% if custom-repository-roles %} | [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %} @@ -236,7 +236,7 @@ An overview of some of the most common actions that are recorded as events in th | `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{% ifversion fpt or ghec or ghes > 3.2 or ghae %} ### `dependabot_alerts` category actions | Action | Description @@ -497,7 +497,6 @@ For more information, see "[Managing the publication of {% data variables.produc | `delete` | Triggered when a custom pattern is removed from secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)." {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} ### `organization_label` category actions | Action | Description @@ -506,8 +505,6 @@ For more information, see "[Managing the publication of {% data variables.produc | `update` | Triggered when a default label is edited. | `destroy` | Triggered when a default label is deleted. -{% endif %} - ### `oauth_application` category actions | Action | Description @@ -572,11 +569,10 @@ For more information, see "[Managing the publication of {% data variables.produc | `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch. | `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed. | `rejected_ref_update ` | Triggered when a branch update attempt is rejected. -| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.{% ifversion fpt or ghes or ghae or ghec %} +| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator. | `update_allow_force_pushes_enforcement_level ` | Triggered when force pushes are enabled or disabled for a protected branch. | `update_allow_deletions_enforcement_level ` | Triggered when branch deletion is enabled or disabled for a protected branch. | `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch. -{% endif %} {% ifversion fpt or ghes > 3.1 or ghae or ghec %} @@ -707,7 +703,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a repository. -{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% endif %}{% ifversion fpt or ghes or ghae or ghec %} ### `repository_vulnerability_alert` category actions | Action | Description diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index 1ca5404bd7..aeba62732d 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -158,25 +158,25 @@ Organizationレベルの設定の管理に加えて、Organizationのオーナ このセクションでは、{% data variables.product.prodname_advanced_security %}の機能のようなセキュリティ機能に必要なアクセス権を知ることができます。 -| リポジトリアクション | Read | Triage | Write | Maintain | Admin | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------------:|{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| リポジトリでの[脆弱性のある依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)を受信 | | | | | **X** | -| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %} +| リポジトリアクション | Read | Triage | Write | Maintain | Admin | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------:|{% ifversion fpt or ghes or ghae or ghec %} +| リポジトリでの[脆弱性のある依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)を受信 | | | | | **X** | +| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | -| [セキュリティアラートを受信する追加のユーザまたはTeamの指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| [セキュリティアドバイザリ](/code-security/security-advisories/about-github-security-advisories)の作成 | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [セキュリティアラートを受信する追加のユーザまたはTeamの指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} +| [セキュリティアドバイザリ](/code-security/security-advisories/about-github-security-advisories)の作成 | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | -| {% data variables.product.prodname_GH_advanced_security %}の機能へのアクセス管理（「[Organizationのセキュリティと分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」参照） | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} +| {% data variables.product.prodname_GH_advanced_security %}の機能へのアクセス管理（「[Organizationのセキュリティと分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」参照） | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} | -| プライベートリポジトリの[依存関係グラフの有効化](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 or ghec %} -| [依存関係のレビューを表示する](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** +| プライベートリポジトリの[依存関係グラフの有効化](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae or ghec %} +| [依存関係のレビューを表示する](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** {% endif %} -| [プルリクエストの {% data variables.product.prodname_code_scanning %} アラートを表示する](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [{% data variables.product.prodname_code_scanning %} アラートを一覧表示、却下、削除します](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | -| [リポジトリの {% data variables.product.prodname_secret_scanning %} アラートを表示する](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} +| [プルリクエストの {% data variables.product.prodname_code_scanning %} アラートを表示する](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [{% data variables.product.prodname_code_scanning %} アラートを一覧表示、却下、削除します](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | +| [リポジトリの {% data variables.product.prodname_secret_scanning %} アラートを表示する](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} | -| [{% data variables.product.prodname_secret_scanning %} アラートを解決、取り消し、再オープンする](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %} -| リポジトリで [{% data variables.product.prodname_secret_scanning %} アラートを受信する追加の人または Team を指定する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** +| [{% data variables.product.prodname_secret_scanning %} アラートを解決、取り消し、再オープンする](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} +| リポジトリで [{% data variables.product.prodname_secret_scanning %} アラートを受信する追加の人または Team を指定する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** {% endif %} [1] リポジトリの作者とメンテナは、自分のコミットのアラート情報のみを表示できます。 diff --git a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md index 67d1afa791..c8098a7e24 100644 --- a/translations/ja-JP/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md @@ -5,8 +5,6 @@ permissions: Organization owners can export member information for their organiz versions: fpt: '*' ghec: '*' - ghes: '>=3.3' - ghae: issue-5146 topics: - Organizations - Teams diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/ja-JP/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md index 6102b22499..221d74aaed 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -26,8 +26,8 @@ shortTitle: Organizationのユーザへの変換 2. [ユーザのロールをオーナーに変更](/articles/changing-a-person-s-role-to-owner)します。 3. 新しい個人アカウントに{% data variables.product.signin_link %}します。 4. 新しい個人アカウントに[各 Organization リポジトリを移譲](/articles/how-to-transfer-a-repository)します。 -5. [Organizationの名前を変更](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username)して、現在のユーザ名を利用可能にしてください。 -6. Organization の名前に[ユーザ名を変更](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username)します。 +5. [Organizationの名前を変更](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username)して、現在のユーザ名を利用可能にしてください。 +6. Organization の名前に[ユーザ名を変更](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username)します。 7. [Organization を削除](/organizations/managing-organization-settings/deleting-an-organization-account)します。 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md index 8844932635..0c9260ff2a 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md @@ -16,13 +16,13 @@ shortTitle: 可視性の変更ポリシーの設定 permissions: Organization owners can restrict repository visibility changes for an organization. --- -You can restrict who has the ability to change the visibility of repositories in your organization, such as changing a repository from private to public. For more information about repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." +リポジトリをプライベートからパブリックに変更するというような、Organization内でのリポジトリの可視性の変更を行える人を制限できます。 リポジトリの可視性に関する詳しい情報については「[リポジトリについて](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)」を参照してください。 -You can restrict the ability to change repository visibility to organization owners only, or you can allow anyone with admin access to a repository to change visibility. +リポジトリの可視性を変更できるのを Organization のオーナーのみに制限すること、または可視性の変更をリポジトリの管理者権限を所有するメンバーに許可することができます。 {% warning %} -**Warning**: If enabled, this setting allows people with admin access to choose any visibility for an existing repository, even if you do not allow that type of repository to be created. 詳しい情報については「[Organization でのリポジトリ作成の制限](/articles/restricting-repository-creation-in-your-organization)」を参照してください。 +**警告**: この設定を有効にすると、管理者権限をもつユーザは、それが作成できるタイプのリポジトリではなくても、既存のリポジトリを任意の可視性に変更できるようになります。 詳しい情報については「[Organization でのリポジトリ作成の制限](/articles/restricting-repository-creation-in-your-organization)」を参照してください。 {% endwarning %} diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md index ad9f8d0d00..907e2fbe20 100644 --- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md @@ -2,8 +2,6 @@ title: Managing security managers in your organization intro: You can give your security team the least access they need to your organization by assigning a team to the security manager role. versions: - fpt: '*' - ghes: '>=3.3' feature: security-managers topics: - Organizations @@ -30,7 +28,7 @@ Members of a team with the security manager role have only the permissions requi Additional functionality, including a security overview for the organization, is available in organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %}. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). {% endif %} -If a team has the security manager role, people with admin access to the team and a specific repository can change the team's level of access to that repository but cannot remove the access. 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){% ifversion ghes %}."{% else %} and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% endif %} +If a team has the security manager role, people with admin access to the team and a specific repository can change the team's level of access to that repository but cannot remove the access. 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){% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %}" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% else %}."{% endif %} ![Manage repository access UI with security managers](/assets/images/help/organizations/repo-access-security-managers.png) diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md index 7f2a460d2a..3332ed60fa 100644 --- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md +++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md @@ -146,7 +146,7 @@ Organizationでの{% data variables.product.prodname_github_app %}マネージ {% endif %} | OrganizationのPull Requestレビューを管理（[OrganizationでのPull Requestのレビューの管理](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)」を参照） | **X** | | | | | -{% elsif ghes > 3.2 or ghae-issue-4999 %} +{% elsif ghes > 3.2 or ghae %} | Organization のアクション | オーナー | メンバー | セキュリティマネージャー | diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/about-teams.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/about-teams.md index 052dc5b6af..a48986bd53 100644 --- a/translations/ja-JP/content/organizations/organizing-members-into-teams/about-teams.md +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/about-teams.md @@ -37,7 +37,7 @@ You can also use LDAP Sync to synchronize {% data variables.product.product_loca {% data reusables.organizations.types-of-team-visibility %} -You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)." +You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)." ## Team pages diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md index bfa0005f32..0b6c9670e4 100644 --- a/translations/ja-JP/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md @@ -31,11 +31,10 @@ permissions: Organization owners can promote team members to team maintainers. - [Teamディスカッションの削除](/articles/managing-disruptive-comments/#deleting-a-comment) - [OrganizationのメンバーのTeamへの追加](/articles/adding-organization-members-to-a-team) - [OrganizationメンバーのTeamからの削除](/articles/removing-organization-members-from-a-team) -- リポジトリへのTeamのアクセスの削除{% ifversion fpt or ghes or ghae or ghec %} -- [Teamのためのコードレビューの割り当て管理](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% ifversion fpt or ghec %} +- リポジトリへのTeamのアクセス権の削除 +- [Teamのためのコードレビューの割り当て管理](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% ifversion fpt or ghec %} - [プルリクエストのスケジュールされたリマインダーの管理](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %} - ## Organization メンバーをチームメンテナに昇格させる Organizationメンバーをチームメンテナに昇格するには、そのメンバーはTeamのメンバーになっていなければなりません。 diff --git a/translations/ja-JP/content/pages/index.md b/translations/ja-JP/content/pages/index.md index 44ce4c4065..64e5295d61 100644 --- a/translations/ja-JP/content/pages/index.md +++ b/translations/ja-JP/content/pages/index.md @@ -1,7 +1,34 @@ --- title: GitHub Pagesのドキュメンテーション shortTitle: GitHub Pages -intro: '{% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}上のリポジトリから直接Webサイトを作成できます。' +intro: 'Learn how to create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Explore website building tools like Jekyll and troubleshoot issues with your {% data variables.product.prodname_pages %} site.' +introLinks: + quickstart: /pages/quickstart + overview: /pages/getting-started-with-github-pages/about-github-pages +featuredLinks: + guides: + - /pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site + - /pages/getting-started-with-github-pages/creating-a-github-pages-site + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll{% endif %}' + - '{% ifversion ghec %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site{% endif %}' + - '{% ifversion fpt %}/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll{% endif %}' + popular: + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages{% endif %}' + - /pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll) + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages{% endif %}' + - '{% ifversion fpt or ghec %}/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https{% endif %}' + - '{% ifversion ghes or ghae %}/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll{% endif %}' + guideCards: + - /pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site + - /pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll + - /pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites +changelog: + label: pages +layout: product-landing redirect_from: - /categories/20/articles - /categories/95/articles diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md index 0cf4c53036..d18993b04b 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md @@ -1,6 +1,6 @@ --- title: プルリクエストのステージの変更 -intro: 'プルリクエストのドラフトをレビュー準備完了としてマークしたり{% ifversion fpt or ghae or ghes or ghec %}、プルリクエストをドラフトに変換したりすることができます{% endif %}。' +intro: You can mark a draft pull request as ready for review or convert a pull request to a draft. permissions: People with write permissions to a repository and pull request authors can change the stage of a pull request. product: '{% data reusables.gated-features.draft-prs %}' redirect_from: @@ -22,20 +22,16 @@ shortTitle: Change the state {% data reusables.pull_requests.mark-ready-review %} -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Tip**: You can also mark a pull request as ready for review using the {% data variables.product.prodname_cli %}. For more information, see "[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)" in the {% data variables.product.prodname_cli %} documentation. {% endtip %} -{% endif %} {% data reusables.repositories.sidebar-pr %} 2. プルリクエストのリストで、レビューの準備ができたことを示すマークを付けたいプルリクエストクリックします。 3. マージボックスで、[**Ready for review**] をクリックします。 ![[Ready for review] ボタン](/assets/images/help/pull_requests/ready-for-review-button.png) -{% ifversion fpt or ghae or ghes or ghec %} - ## プルリクエストをドラフトに変換する プルリクエストはいつでもドラフトに変換できます。 たとえば、ドラフトではなくプルリクエストを誤ってオープンした場合、または対処の必要があるプルリクエストについてのフィードバックを受け取った場合、プルリクエストをドラフトに変換して、さらなる変更が必要であることを示すことができます。 プルリクエストをレビューの準備完了として再度マークするまで、プルリクエストをマージすることはできません。 プルリクエストの通知をすでにサブスクライブしているユーザは、プルリクエストをドラフトに変換するときにサブスクライブ解除されません。 @@ -45,8 +41,6 @@ shortTitle: Change the state 3. 右側のサイドバーの [Reviewers] で、[**Convert to draft**] をクリックします。 ![[ドラフトに変換] リンク](/assets/images/help/pull_requests/convert-to-draft-link.png) 4. [**Convert to draft**] をクリックします。 ![ドラフト確認に変換](/assets/images/help/pull_requests/convert-to-draft-dialog.png) -{% endif %} - ## 参考リンク - [プルリクエストについて](/github/collaborating-with-issues-and-pull-requests/about-pull-requests) diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md index a35b477866..e34db9436f 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md @@ -21,7 +21,7 @@ Repositories belong to a personal account (a single individual owner) or an orga To assign a reviewer to a pull request, you will need write access to the repository. For more information about repository access, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." If you have write access, you can assign anyone who has read access to the repository as a reviewer. -Organization members with write access can also assign a pull request review to any person or team with read access to a repository. リクエストされたレビュー担当者または Team は、Pull Request レビューをするようあなたが依頼したという通知を受け取ります。 {% ifversion fpt or ghae or ghes or ghec %}Team にレビューをリクエストし、コードレビューの割り当てが有効になっている場合、特定のメンバーがリクエストされ、Team はレビュー担当者として削除されます。 For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} +Organization members with write access can also assign a pull request review to any person or team with read access to a repository. リクエストされたレビュー担当者または Team は、Pull Request レビューをするようあなたが依頼したという通知を受け取ります。 If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." {% note %} diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md index 1bd4de46a8..272ea40032 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md @@ -22,7 +22,7 @@ shortTitle: About PR reviews {% if pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %} -リポジトリオーナーとコラボレーターは、特定の人物にプルリクエストのレビューをリクエストできます。 また、Organization メンバーは、リポジトリの読み取りアクセス権を持つ Team にプルリクエストのレビューをリクエストできます。 詳細は「[Pull Request レビューをリクエストする](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)」を参照してください。 {% ifversion fpt or ghae or ghes or ghec %}Teamメンバーのサブセットを指定して、Team 全体に代わって自動で割り当てることができます。 For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} +リポジトリオーナーとコラボレーターは、特定の人物にプルリクエストのレビューをリクエストできます。 また、Organization メンバーは、リポジトリの読み取りアクセス権を持つ Team にプルリクエストのレビューをリクエストできます。 詳細は「[Pull Request レビューをリクエストする](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)」を参照してください。 You can specify a subset of team members to be automatically assigned in the place of the whole team. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." レビューにより、提案された変更についての議論がなされ、その変更がリポジトリのコントリビューションのガイドラインやその他の品質標準を満たすことを保証しやすくなります。 コードの特定の種類や領域に対して、どの個人や Team をオーナーとするかを、CODEOWNERS ファイルで定義できます。 プルリクエストが、定義されたオーナーを持っているコードを変更するものである場合、オーナーである個人あるいはTeam がレビューを担当するよう、自動的にリクエストされます。 詳細は「[コードオーナーについて](/articles/about-code-owners/)」を参照してください。 diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 461a58b860..de7328d0d4 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -5,7 +5,7 @@ product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md index a58f26d3fb..e269a9dd16 100644 --- a/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md +++ b/translations/ja-JP/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md @@ -31,9 +31,9 @@ compare の最も一般的な使い方は、新しいプルリクエストを開 ## タグを比較する -リリースタグを比較すると、前回のリリース以降のリポジトリへの変更が表示されます。 {% ifversion fpt or ghae or ghes or ghec %} 詳しい情報については、「[リリースを比較する](/github/administering-a-repository/comparing-releases)」を参照してください。{% endif %} +リリースタグを比較すると、前回のリリース以降のリポジトリへの変更が表示されます。 For more information, see "[Comparing releases](/github/administering-a-repository/comparing-releases)." -{% ifversion fpt or ghae or ghes or ghec %}タグを比較するには、ページ上部の `compare` ドロップダウンメニューからタグ名を選択できます。{% else %}ブランチ名を入力する代わりに、`compare` ドロップダウンメニューにタグの名前を入力します。{% endif %} +To compare tags, you can select a tag name from the `compare` drop-down menu at the top of the page. 2 つのタグ間を比較する例については、[こちらをクリック](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3)してください。 diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md index cd840c5c08..3d66e04fec 100644 --- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md +++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md @@ -27,8 +27,7 @@ shortTitle: About merge methods {% data reusables.pull_requests.default_merge_option %} -{% ifversion fpt or ghae or ghes or ghec %} -デフォルトのマージ方法では、マージコミットが作成されます。 直線状のコミット履歴を強制して、保護されたブランチにマージコミットをプッシュできないようにすることができます。 詳しい情報については、「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-linear-history)」を参照してください。{% endif %} +デフォルトのマージ方法では、マージコミットが作成されます。 直線状のコミット履歴を強制して、保護されたブランチにマージコミットをプッシュできないようにすることができます。 詳しい情報については、「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-linear-history)」を参照してください。 ## マージコミットのsquash diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md index 61af217fe8..7917efae05 100644 --- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md +++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md @@ -63,9 +63,9 @@ For more information about each of the available branch protection settings, see - コードを変更するコミットがブランチにプッシュされたときにプルリクエストの承認レビューを却下する場合は、[**Dismiss stale pull request approvals when new commits are pushed**] を選択します。 ![新たなコミットがチェックボックスにプッシュされた際に古いプルリクエストの承認を却下するチェックボックス](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) - 指定されたオーナーのコードにプルリクエストが影響する場合に、コードオーナーからのレビューを必須にする場合は、[**Require review from Code Owners**] を選択します。 詳細は「[コードオーナーについて](/github/creating-cloning-and-archiving-repositories/about-code-owners)」を参照してください。 ![コードオーナーのレビューを必要とする](/assets/images/help/repository/PR-review-required-code-owner.png) {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5611 %} - - Optionally, to allow specific people or teams to push code to the branch without creating pull requests when they're required, select **Allow specific actors to bypass required pull requests**. Then, search for and select the people or teams who should be allowed to skip creating a pull request. ![Allow specific actors to bypass pull request requirements checkbox](/assets/images/help/repository/PR-bypass-requirements.png) + - Optionally, to allow specific actors to push code to the branch without creating pull requests when they're required, select **Allow specified actors to bypass required pull requests**. Then, search for and select the actors who should be allowed to skip creating a pull request. ![Allow specific actors to bypass pull request requirements checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-bypass-requirements-with-apps.png){% else %}(/assets/images/help/repository/PR-bypass-requirements.png){% endif %} {% endif %} - - リポジトリが Organization の一部である場合、[**Restrict who can dismiss pull request reviews**] を選択します。 そして、Pull Requestレビューを却下できるユーザまたは Team を検索して選択します。 詳しい情報については[プルリクエストレビューの却下](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)を参照してください。 ![[Restrict who can dismiss pull request reviews] チェックボックス](/assets/images/help/repository/PR-review-required-dismissals.png) + - リポジトリが Organization の一部である場合、[**Restrict who can dismiss pull request reviews**] を選択します。 Then, search for and select the actors who are allowed to dismiss pull request reviews. 詳しい情報については[プルリクエストレビューの却下](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)を参照してください。 ![Restrict who can dismiss pull request reviews checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-review-required-dismissals-with-apps.png){% else %}(/assets/images/help/repository/PR-review-required-dismissals.png){% endif %} 1. 必要に応じて、ステータスチェック必須を有効化します。 詳しい情報については[ステータスチェックについて](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)を参照してください。 - [**Require status checks to pass before merging**] を選択します。 ![必須ステータスチェックのオプション](/assets/images/help/repository/required-status-checks.png) - プルリクエストを保護されたブランチの最新コードで確実にテストしたい場合は、[**Require branches to be up to date before merging**] を選択します。 ![必須ステータスのチェックボックス、ゆるい、または厳格な](/assets/images/help/repository/protecting-branch-loose-status.png) @@ -95,7 +95,7 @@ For more information about each of the available branch protection settings, see {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5624 %} Then, choose who can force push to the branch. - Select **Everyone** to allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions. - - Select **Specify who can force push** to allow only specific people or teams to force push to the branch. Then, search for and select those people or teams. ![Screenshot of the options to specify who can force push](/assets/images/help/repository/allow-force-pushes-specify-who.png) + - Select **Specify who can force push** to allow only specific actors to force push to the branch. Then, search for and select those actors. ![Screenshot of the options to specify who can force push]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png){% else %}(/assets/images/help/repository/allow-force-pushes-specify-who.png){% endif %} {% endif %} For more information about force pushes, see "[Allow force pushes](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)." diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md index 0210913bcf..8b031ae162 100644 --- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md +++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md @@ -37,14 +37,11 @@ remote: error: Required status check "ci-build" is failing {% endnote %} -{% ifversion fpt or ghae or ghes or ghec %} - ## Conflicts between head commit and test merge commit テストマージコミットと head コミットのステータスチェックの結果が競合する場合があります。 テストマージコミットにステータスがある場合、そのテストマージコミットは必ずパスする必要があります。 それ以外の場合、ヘッドコミットのステータスは、ブランチをマージする前にパスする必要があります。 テストマージコミットに関する詳しい情報については、「[プル](/rest/reference/pulls#get-a-pull-request)」を参照してください。 ![マージコミットが競合しているブランチ](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) -{% endif %} ## Handling skipped but required checks diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md index 2627f92c11..ed35fc0aa2 100644 --- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md +++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md @@ -26,17 +26,15 @@ topics: {% endtip %} -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **ヒント**: {% data variables.product.prodname_cli %} を使用してリポジトリを作成することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh repo create`](https://cli.github.com/manual/gh_repo_create)」を参照してください。 {% endtip %} -{% endif %} {% data reusables.repositories.create_new %} -2. また、既存のリポジトリのディレクトリ構造とファイルを持つリポジトリを作成するには、[**Choose a template**] ドロップダウンでテンプレートリポジトリを選択します。 あなたが所有するテンプレートリポジトリ、あなたがメンバーとして属する Organization が所有するテンプレートリポジトリ、使ったことがあるテンプレートリポジトリが表示されます。 詳細は「[テンプレートからリポジトリを作成する](/articles/creating-a-repository-from-a-template)」を参照してください。 ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %} -3. 必要に応じて、テンプレートを使用する場合、デフォルトのブランチだけでなく、テンプレートのすべてのブランチからのディレクトリ構造とファイルを含めるには、[**Include all branches**] を選択します。 ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} +2. また、既存のリポジトリのディレクトリ構造とファイルを持つリポジトリを作成するには、[**Choose a template**] ドロップダウンでテンプレートリポジトリを選択します。 あなたが所有するテンプレートリポジトリ、あなたがメンバーとして属する Organization が所有するテンプレートリポジトリ、使ったことがあるテンプレートリポジトリが表示されます。 詳細は「[テンプレートからリポジトリを作成する](/articles/creating-a-repository-from-a-template)」を参照してください。 ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png) +3. 必要に応じて、テンプレートを使用する場合、デフォルトのブランチだけでなく、テンプレートのすべてのブランチからのディレクトリ構造とファイルを含めるには、[**Include all branches**] を選択します。 ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png) 3. [Owner] ドロップダウンで、リポジトリを作成するアカウントを選択します。 ![[Owner] ドロップダウンメニュー](/assets/images/help/repository/create-repository-owner.png) {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %} diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md index 8fb810fb6d..0f341a6607 100644 --- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md +++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md @@ -19,17 +19,13 @@ shortTitle: Create from a template リポジトリに対する読み取り権限があるユーザなら誰でも、テンプレートからリポジトリを作成できます。 詳細は「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照してください。 -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **ヒント**: {% data variables.product.prodname_cli %} を使用してリポジトリをテンプレートから作成することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh repo create`](https://cli.github.com/manual/gh_repo_create)」を参照してください。 {% endtip %} -{% endif %} -{% ifversion fpt or ghae or ghes or ghec %} テンプレートリポジトリのデフォルトブランチのみからディレクトリ構造とファイルを含めるか、すべてのブランチを含めるかを選択できます。 Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches. -{% endif %} テンプレートからリポジトリを作成することは、リポジトリをフォークすることに似ていますが、以下の点で異なります: - 新しいフォークは、親リポジトリのコミット履歴すべてを含んでいますが、テンプレートから作成されたリポジトリには、最初は 1 つのコミットしかありません。 @@ -44,7 +40,7 @@ shortTitle: Create from a template 2. ファイルの一覧の上にある [**Use this template**] をクリックします。 ![[Use this template] ボタン](/assets/images/help/repository/use-this-template-button.png) {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} -{% data reusables.repositories.choose-repo-visibility %}{% ifversion fpt or ghae or ghes or ghec %} -6. 必要に応じて、デフォルトのブランチだけでなく、テンプレートのすべてのブランチのディレクトリ構造とファイルを含めるには、[**Include all branches**] を選択します。 ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} +{% data reusables.repositories.choose-repo-visibility %} +6. 必要に応じて、デフォルトのブランチだけでなく、テンプレートのすべてのブランチのディレクトリ構造とファイルを含めるには、[**Include all branches**] を選択します。 ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png) {% data reusables.repositories.select-marketplace-apps %} 8. [**Create repository from template**] をクリックします。 diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md index 5628d199e0..98a4fa8d7a 100644 --- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md +++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md @@ -1,6 +1,6 @@ --- title: テンプレートリポジトリを作成する -intro: '既存のリポジトリをテンプレートにして、自分や他の人が同じディレクトリ構造{% ifversion fpt or ghae or ghes or ghec %}、ブランチ、{% endif %}およびファイルで新しいリポジトリを生成できるようにすることができます。' +intro: 'You can make an existing repository a template, so you and others can generate new repositories with the same directory structure, branches, and files.' permissions: Anyone with admin permissions to a repository can make the repository a template. redirect_from: - /articles/creating-a-template-repository @@ -24,7 +24,7 @@ shortTitle: Create a template repo テンプレートリポジトリを作成するには、リポジトリを作成して、そのリポジトリをテンプレート化する必要があります。 リポジトリの作成に関する詳細は「[新しいリポジトリの作成](/articles/creating-a-new-repository)」を参照してください。 -After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch.{% ifversion fpt or ghae or ghes or ghec %} They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches.{% endif %} For more information, see "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)." +After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch. They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches. 詳細は「[テンプレートからリポジトリを作成する](/articles/creating-a-repository-from-a-template)」を参照してください。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 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 9f73f186dc..d73455b3d4 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 @@ -119,14 +119,14 @@ By default, when you create a new repository in your personal account, `GITHUB_T {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions-general %} -1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. +1. [Workflow permissions]の下で、`GITHUB_TOKEN`にすべてのスコープに対する読み書きアクセスを持たせたいか、あるいは`contents`スコープに対する読み取りアクセスだけを持たせたいかを選択してください。 ![Set GITHUB_TOKEN permissions for this repository](/assets/images/help/settings/actions-workflow-permissions-repository{% if allow-actions-to-approve-pr-with-ent-repo %}-with-pr-approval{% endif %}.png) 1. **Save（保存）**をクリックして、設定を適用してください。 {% if allow-actions-to-approve-pr-with-ent-repo %} -### Preventing {% data variables.product.prodname_actions %} from creating or approving pull requests +### {% data variables.product.prodname_actions %}がPull Requestの作成もしくは承認をできないようにする {% data reusables.actions.workflow-pr-approval-permissions-intro %} diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md index 0c0e388b99..1075ceca5f 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md @@ -31,7 +31,7 @@ shortTitle: Email notifications for pushes - コミットの一部として変更されたファイル群 - コミットメッセージ -リポジトリへのプッシュに対して受け取るメール通知はフィルタリングできます。 詳細は、{% ifversion fpt or ghae or ghes or ghec %}「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}「[メール通知について](/github/receiving-notifications-about-activity-on-github/about-email-notifications)」を参照してください。 プッシュのメール通知を無効にすることもできます。 詳しい情報については、「[通知の配信方法を選択する](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}」を参照してください。 +リポジトリへのプッシュに対して受け取るメール通知はフィルタリングできます。 詳しい情報については、「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)」を参照してください。 ## リポジトリへのプッシュに対するメール通知の有効化 @@ -43,10 +43,5 @@ shortTitle: Email notifications for pushes 7. [**Setup notifications**] をクリックします。 ![設定通知ボタン](/assets/images/help/settings/setup_notifications_settings.png) ## 参考リンク -{% ifversion fpt or ghae or ghes or ghec %} - 「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」 -{% else %} -- 「[通知について](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)」 -- [通知の配信方法を選択する](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications) -- 「[メール通知について](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)」 -- 「[Web 通知について](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)」{% endif %} + diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md index 359c66bd9d..53185e56bd 100644 --- a/translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md +++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/about-releases.md @@ -32,7 +32,7 @@ topics: リリースは [Git タグ](https://git-scm.com/book/en/Git-Basics-Tagging)に基づきます。タグは、リポジトリの履歴の特定の地点をマークするものです。 タグの日付は異なる時点で作成できるため、リリースの日付とは異なる場合があります。 既存のタグの表示に関する詳細は「[リポジトリのリリースとタグを表示する](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)」を参照してください。 -リポジトリで新しいリリースが公開されたときに通知を受け取り、リポジトリで他の更新があったときには通知を受け取らないでいることができます。 詳しい情報については、{% ifversion fpt or ghae or ghes or ghec %}「[サブスクリプションを表示する](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}「[リポジトリのリリースを Watch および Watch 解除する](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}」を参照してください。 +リポジトリで新しいリリースが公開されたときに通知を受け取り、リポジトリで他の更新があったときには通知を受け取らないでいることができます。 For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)." リポジトリへの読み取りアクセス権を持つ人はリリースを表示および比較できますが、リリースの管理はリポジトリへの書き込み権限を持つ人のみができます。 詳細は「[リポジトリのリリースを管理する](/github/administering-a-repository/managing-releases-in-a-repository)」を参照してください。 @@ -40,15 +40,19 @@ topics: You can manually create release notes while managing a release. Alternatively, you can automatically generate release notes from a default template, or customize your own release notes template. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)." {% endif %} +{% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7054 %} +When viewing the details for a release, the creation date for each release asset is shown next to the release asset. +{% endif %} + {% ifversion fpt or ghec %} -People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository)." +リポジトリへの管理者権限を持つユーザは、{% data variables.large_files.product_name_long %}（{% data variables.large_files.product_name_short %}）オブジェクトを、{% data variables.product.product_name %} がリリースごとに作成する ZIP ファイルと tarball に含めるかどうかを選択できます。 詳しい情報については、「[リポジトリのアーカイブ内の {% data variables.large_files.product_name_short %} オブジェクトを管理する](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository)」を参照してください。 リリースでセキュリティの脆弱性が修正された場合は、リポジトリにセキュリティアドバイザリを公開する必要があります。 {% data variables.product.prodname_dotcom %} は公開された各セキュリティアドバイザリを確認し、それを使用して、影響を受けるリポジトリに {% data variables.product.prodname_dependabot_alerts %} を送信できます。 詳しい情報については、「[GitHub セキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」 を参照してください。 リポジトリ内のコードに依存しているリポジトリとパッケージを確認するために、依存関係グラフの [**依存関係**] タブを表示することができますが、それによって、新しいリリースの影響を受ける可能性があります。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 {% endif %} -リリースAPIを使用して、リリースアセットがダウンロードされた回数などの情報を収集することもできます。 詳しい情報については、「[リリース](/rest/reference/repos#releases)」を参照してください。 +リリースAPIを使用して、リリースアセットがダウンロードされた回数などの情報を収集することもできます。 詳しい情報については、「[リリース](/rest/reference/releases)」を参照してください。 {% ifversion fpt or ghec %} ## ストレージと帯域幅の容量 diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md index ccbef6d1e0..5dae5b5b8e 100644 --- a/translations/ja-JP/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md +++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md @@ -17,13 +17,11 @@ topics: shortTitle: View releases & tags --- -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **ヒント**: {% data variables.product.prodname_cli %} を使用してリリースを表示することもできます。 詳しい情報については、{% data variables.product.prodname_cli %} ドキュメントの「[`gh release view`](https://cli.github.com/manual/gh_release_view)」を参照してください。 {% endtip %} -{% endif %} ## リリースを表示する diff --git a/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md index e16ade776b..ba0b521a11 100644 --- a/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md +++ b/translations/ja-JP/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md @@ -64,7 +64,7 @@ shortTitle: Connections between repositories {% data reusables.repositories.accessing-repository-graphs %} 3. 左サイトバーで [**Forks**] をクリックします。 ![[Forks] タブ](/assets/images/help/graphs/graphs-sidebar-forks-tab.png) -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## リポジトリの依存関係を表示する 依存関係グラフを使用して、リポジトリが依存するコードを調べることができます。 diff --git a/translations/ja-JP/content/rest/enterprise-admin/audit-log.md b/translations/ja-JP/content/rest/enterprise-admin/audit-log.md index fea9705230..0426ebb1e7 100644 --- a/translations/ja-JP/content/rest/enterprise-admin/audit-log.md +++ b/translations/ja-JP/content/rest/enterprise-admin/audit-log.md @@ -5,6 +5,7 @@ versions: fpt: '*' ghes: '>=3.3' ghec: '*' + ghae: '*' topics: - API miniTocMaxHeadingLevel: 3 diff --git a/translations/ja-JP/content/rest/guides/getting-started-with-the-checks-api.md b/translations/ja-JP/content/rest/guides/getting-started-with-the-checks-api.md index fd7049fcfa..2ef42357d4 100644 --- a/translations/ja-JP/content/rest/guides/getting-started-with-the-checks-api.md +++ b/translations/ja-JP/content/rest/guides/getting-started-with-the-checks-api.md @@ -41,10 +41,7 @@ GitHub Appは、単に合格/不合格の二択ではない、情報量の多い ![チェック実行のワークフロー](/assets/images/check_runs.png) -{% ifversion fpt or ghes or ghae or ghec %} -チェック実行が15日以上にわたり不完全な状態である場合は、チェック実行の`conclusion`が`stale`になり、に状態が -{% data variables.product.prodname_dotcom %}に{% octicon "issue-reopened" aria-label="The issue-reopened icon" %}でstaleと表示されます。 {% data variables.product.prodname_dotcom %}のみが、チェック実行を`stale`としてマークできます。 チェック実行で出る可能性がある結果についての詳細は、 [`conclusion`パラメータ](/rest/reference/checks#create-a-check-run--parameters)を参照してください。 -{% endif %} +チェック実行が15日以上にわたり不完全な状態である場合は、チェック実行の`conclusion`が`stale`になり、{% data variables.product.prodname_dotcom %}に状態が{% octicon "issue-reopened" aria-label="The issue-reopened icon" %}と表示されます。 {% data variables.product.prodname_dotcom %}のみが、チェック実行を`stale`としてマークできます。 チェック実行で出る可能性がある結果についての詳細は、 [`conclusion`パラメータ](/rest/reference/checks#create-a-check-run--parameters)を参照してください。 [`check_suite`](/webhooks/event-payloads/#check_suite) webhookを受け取ったら、チェックが完了していなくてもすぐにチェック実行を作成できます。 チェック実行の`status`は、`queued`、`in_progress`、または`completed`の値で更新でき、より詳細を明らかにして`output`を更新できます。 チェック実行にはタイムスタンプ、詳細情報が記載された外部サイトへのリンク、コードの特定の行に対するアノテーション、および実行した分析についての情報を含めることができます。 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 4791afc212..726026840e 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 @@ -148,7 +148,7 @@ When authenticating, you should see your rate limit bumped to 5,000 requests an You can easily [create a **personal access token**][personal token] using your [Personal access tokens settings page][tokens settings]: -{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} {% warning %} To help keep your information secure, we highly recommend setting an expiration for your personal access tokens. @@ -164,7 +164,7 @@ To help keep your information secure, we highly recommend setting an expiration ![Personal Token selection](/assets/images/help/personal_token_ghae.png) {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} API requests using an expiring personal access token will return that token's expiration date via the `GitHub-Authentication-Token-Expiration` header. You can use the header in your scripts to provide a warning message when the token is close to its expiration date. {% endif %} 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 81ebce6f9d..05837720ec 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 @@ -120,7 +120,7 @@ curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/ {% ifversion fpt or ghec %} -[認証されていないレート制限の詳細](#increasing-the-unauthenticated-rate-limit-for-oauth-applications)をお読みください。 +Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-apps). {% endif %} 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 6d9862e799..2d136676fb 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 @@ -87,7 +87,6 @@ shortTitle: Understand search syntax スペースなど、いくつかの英数字以外の記号は、引用符で囲ったコード検索クエリから省かれるので、結果が予想外のものになる場合があります。 -{% ifversion fpt or ghes or ghae or ghec %} ## ユーザ名によるクエリ 検索クエリに、`user`、`actor`、`assignee`などユーザ名を必要とする修飾子が含まれる場合は、任意の {% data variables.product.product_name %} ユーザ名を使用して特定の個人を指定するか、`@me`を使用して現在のユーザを指定することができます。 @@ -98,4 +97,3 @@ shortTitle: Understand search syntax | `QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) は、結果を表示している個人に割り当てられた Issue に一致します。 | `@me` は必ず修飾子とともに使用し、`@me main.workflow` のように検索用語としては使用できません。 -{% endif %} 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 e2948cda1a..970bb55b17 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 @@ -55,15 +55,12 @@ shortTitle: Search issues & PRs {% data reusables.pull_requests.large-search-workaround %} - | 修飾子 | サンプル | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) は、@defunkt が保有するリポジトリからの「ubuntu」という単語がある Issue にマッチします。 | | org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) は、GitHub Organization が保有するリポジトリの Issue にマッチします。 | | repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) は、2012 年 3 月より前に作成された @mozilla の shumway プロジェクトからの Issue にマッチします。 | - - ## オープンかクローズかで検索 `state` 修飾子または `is` 修飾子を使って、オープンかクローズかで、Issue およびプルリクエストをフィルタリングできます。 @@ -133,17 +130,15 @@ shortTitle: Search issues & PRs | involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** は、@defunkt または @jlord が関与している Issue にマッチします。 | | | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues)は、本文に「bootstrap」という単語を含まず、@mdo が関与している Issue にマッチします。 | -{% ifversion fpt or ghes or ghae or ghec %} ## リンクされた Issue とプルリクエストを検索する 結果を絞り込んで、クローズしているリファレンスによってプルリクエストにリンクされている、またはプルリクエストによってクローズされる可能性がある Issue にリンクされている Issue のみを表示することができます。 -| 修飾子 | サンプル | -| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) は、`desktop/desktop` リポジトリの中で、クローズしているリファレンスによってプルリクエストにリンクされている Issue に一致します。 | -| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) は、 `desktop/desktop` リポジトリの中で、プルリクエストによってクローズされた可能性がある Issue にリンクされていた、クローズされたプルリクエストに一致します。 | -| `-linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) は、`desktop/desktop` リポジトリの中で、クローズしているリファレンスによってプルリクエストにリンクされていない Issue に一致します。 | -| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) は、 `desktop/desktop` リポジトリの中で、プルリクエストによってクローズされる可能性がある Issue にリンクされていないオープンのプルリクエストに一致します。 -{% endif %} +| 修飾子 | サンプル | +| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) は、`desktop/desktop` リポジトリの中で、クローズしているリファレンスによってプルリクエストにリンクされている Issue に一致します。 | +| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) は、 `desktop/desktop` リポジトリの中で、プルリクエストによってクローズされた可能性がある Issue にリンクされていた、クローズされたプルリクエストに一致します。 | +| `-linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) は、`desktop/desktop` リポジトリの中で、クローズしているリファレンスによってプルリクエストにリンクされていない Issue に一致します。 | +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) は、 `desktop/desktop` リポジトリの中で、プルリクエストによってクローズされる可能性がある Issue にリンクされていないオープンのプルリクエストに一致します。 | ## ラベルで検索 @@ -212,7 +207,7 @@ shortTitle: Search issues & PRs ## コメントの数で検索 -コメントの数で検索するには、[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)とともに `comments` 修飾子を使います。 +You can use the `comments` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to search by the number of comments. | 修飾子 | サンプル | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -221,7 +216,7 @@ shortTitle: Search issues & PRs ## インタラクションの数で検索 -`interactions` 修飾子と[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)を使って、Issue や プルリクエストをインタラクションの数でフィルタリングできます。 インタラクションの数とは、1 つの Issue またはプルリクエストにあるリアクションおよびコメントの数のことです。 +You can filter issues and pull requests by the number of interactions with the `interactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). インタラクションの数とは、1 つの Issue またはプルリクエストにあるリアクションおよびコメントの数のことです。 | 修飾子 | サンプル | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | @@ -230,7 +225,7 @@ shortTitle: Search issues & PRs ## リアクションの数で検索 -`reactions` 修飾子と[不等号や範囲の修飾子](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)を使って、Issue や プルリクエストをリアクションの数でフィルタリングできます。 +You can filter issues and pull requests by the number of reactions using the `reactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). | 修飾子 | サンプル | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | @@ -238,24 +233,27 @@ shortTitle: Search issues & PRs | | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) は、リアクションの数が 500 から 1,000 までの範囲の Issue にマッチします。 | ## ドラフトプルリクエストを検索 -ドラフトプルリクエストをフィルタリングすることができます。 詳しい情報については[プルリクエストについて](/articles/about-pull-requests#draft-pull-requests)を参照してください。 +ドラフトプルリクエストをフィルタリングすることができます。 For more information, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)." -| Qualifier | Example | ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) はドラフトプルリクエストに一致します。 | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) は、レビューの準備ができたプルリクエストに一致します。{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) はドラフトプルリクエストに一致します。{% endif %} +| 修飾子 | サンプル | +| ------------- | ------------------------------------------------------------------------------------------------------------- | +| `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) matches draft pull requests. | +| `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) matches pull requests that are ready for review. | ## プルリクエストレビューのステータスおよびレビュー担当者で検索 -レビュー担当者およびレビューリクエストを受けた人で、[レビューステータス](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_、_required_、_approved_、または _changes requested_) でプルリクエストをフィルタリングできます。 +You can filter pull requests based on their [review status](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_, _required_, _approved_, or _changes requested_), by reviewer, and by requested reviewer. -| 修飾子 | サンプル | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) は、レビューされていないプルリクエストにマッチします。 | -| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) は、マージ前にレビューが必要なプルリクエストにマッチします。 | -| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) は、レビュー担当者が承認したプルリクエストにマッチします。 | -| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) は、レビュー担当者が変更を求めたプルリクエストにマッチします。 | -| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) は、特定の人がレビューしたプルリクエストにマッチします。 | -| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) は、特定の人にレビューがリクエストされているプルリクエストにマッチします。 リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。 If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} +| 修飾子 | サンプル | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) matches pull requests that have not been reviewed. | +| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) matches pull requests that require a review before they can be merged. | +| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) matches pull requests that a reviewer has approved. | +| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) matches pull requests in which a reviewer has asked for changes. | +| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) matches pull requests reviewed by a particular person. | +| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。 If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} | user-review-requested:@me | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review.{% endif %} -| team-review-requested:TEAMNAME | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) は、Team `atom/design`からのレビューリクエストがあるプルリクエストにマッチします。 リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。 | +| team-review-requested:TEAMNAME | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) matches pull requests that have review requests from the team `atom/design`. リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。 | ## Issue やプルリクエストの作成時期や最終更新時期で検索 diff --git a/translations/ja-JP/content/site-policy/github-terms/github-community-guidelines.md b/translations/ja-JP/content/site-policy/github-terms/github-community-guidelines.md index 93ce080ae2..6d296bd994 100644 --- a/translations/ja-JP/content/site-policy/github-terms/github-community-guidelines.md +++ b/translations/ja-JP/content/site-policy/github-terms/github-community-guidelines.md @@ -39,7 +39,7 @@ While some disagreements can be resolved with direct, respectful communication b * **Communicate expectations** - Maintainers can set community-specific guidelines to help users understand how to interact with their projects, for example, in a repository’s README, [CONTRIBUTING file](/articles/setting-guidelines-for-repository-contributors/), or [dedicated code of conduct](/articles/adding-a-code-of-conduct-to-your-project/). You can find additional information on building communities [here](/communities). -* **Moderate Comments** - Users with [write-access privileges](/articles/repository-permission-levels-for-an-organization/) for a repository can [edit, delete, or hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) on commits, pull requests, and issues. リポジトリの読み取りアクセスがあれば、誰でもコミットの編集履歴を見ることができます。 Comment authors and people with write access to a repository can also delete sensitive information from a [comment's edit history](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment). Moderating your projects can feel like a big task if there is a lot of activity, but you can [add collaborators](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) to assist you in managing your community. +* **Moderate Comments** - Users with [write-access privileges](/articles/repository-permission-levels-for-an-organization/) for a repository can [edit, delete, or hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) on commits, pull requests, and issues. リポジトリの読み取りアクセスがあれば、誰でもコミットの編集履歴を見ることができます。 Comment authors and people with write access to a repository can also delete sensitive information from a [comment's edit history](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment). Moderating your projects can feel like a big task if there is a lot of activity, but you can [add collaborators](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) to assist you in managing your community. * **Lock Conversations**  - If a discussion in an issue, pull request, or commit gets out of hand, off topic, or violates your project’s code of conduct or GitHub’s policies, owners, collaborators, and anyone else with write access can put a temporary or permanent [lock](/articles/locking-conversations/) on the conversation. diff --git a/translations/ja-JP/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md b/translations/ja-JP/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md index 5c84b46a70..ddbb50105c 100644 --- a/translations/ja-JP/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md +++ b/translations/ja-JP/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md @@ -16,8 +16,8 @@ Use of GitHub Codespaces is subject to the [GitHub Privacy Statement](/github/si Activity on github.dev is subject to [GitHub's Beta Previews terms](/github/site-policy/github-terms-of-service#j-beta-previews) -## Using Visual Studio Code +## {% data variables.product.prodname_vscode %}を使用する -GitHub Codespaces and github.dev allow for use of Visual Studio Code in the web browser. When using Visual Studio Code in the web browser, some telemetry collection is enabled by default and is [explained in detail on the Visual Studio Code website](https://code.visualstudio.com/docs/getstarted/telemetry). Users can opt out of telemetry by going to File > Preferences > Settings under the top left menu. +GitHub Codespaces and github.dev allow for use of {% data variables.product.prodname_vscode %} in the web browser. When using {% data variables.product.prodname_vscode_shortname %} in the web browser, some telemetry collection is enabled by default and is [explained in detail on the {% data variables.product.prodname_vscode_shortname %} website](https://code.visualstudio.com/docs/getstarted/telemetry). Users can opt out of telemetry by going to File > Preferences > Settings under the top left menu. -If a user chooses to opt out of telemetry capture in Visual Studio Code while inside of a codespace as outlined, this will sync the disable telemetry preference across all future web sessions in GitHub Codespaces and github.dev. +If a user chooses to opt out of telemetry capture in {% data variables.product.prodname_vscode_shortname %} while inside of a codespace as outlined, this will sync the disable telemetry preference across all future web sessions in GitHub Codespaces and github.dev. diff --git a/translations/ja-JP/content/site-policy/privacy-policies/github-privacy-statement.md b/translations/ja-JP/content/site-policy/privacy-policies/github-privacy-statement.md index ca0d69a4ae..2d8ee53f18 100644 --- a/translations/ja-JP/content/site-policy/privacy-policies/github-privacy-statement.md +++ b/translations/ja-JP/content/site-policy/privacy-policies/github-privacy-statement.md @@ -65,7 +65,7 @@ Githubではお客様の個人情報をプライバシーステートメント #### 支払情報 有料でのアカウントにサインオンする場合や、GitHub Sponsors Programを通じて送金する場合、GitHub Marketplaceでアプリケーションを購入する場合、当社は、お客様のフルネーム、住所およびクレジットカード情報またはPayPal情報を収集します。 GitHubは、お客様のクレジットカード情報またはPaypal情報を処理または保管しませんが、第三者の支払処理者はこれを行うことにご留意ください。 -[GitHub Marketplace](https://github.com/marketplace) にアプリケーションを掲載しこれを販売する場合、当社は、お客様の銀行情報を要求します。 [GitHub Sponsors Program](https://github.com/sponsors)を通じて資金を調達する場合、当社は、利用者がサービスに参加して資金を受け取るため、および法令順守のため、登録処理を通じて利用者の[追加情報](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-bank-information) を要求します。 +[GitHub Marketplace](https://github.com/marketplace) にアプリケーションを掲載しこれを販売する場合、当社は、お客様の銀行情報を要求します。 If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes. #### プロフィール情報 お客様は、フルネーム、写真を含むアバター、経歴、位置情報、会社、第三者のウェブサイトへのURLなどのお客様のアカウントプロフィールの追加情報を当社に提供するかどうかを選択できます。 この情報には、ユーザの個人情報が含まれる可能性があります。 プロフィール情報は、当社のサービスを使用する他のユーザからも閲覧ができますのでご注意ください。 diff --git a/translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md index 4918a84824..1e44b4bbff 100644 --- a/translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md +++ b/translations/ja-JP/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md @@ -19,7 +19,7 @@ topics: {% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)." -{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)." +{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)." {% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md index 0fb3ae74fb..e80ef26e64 100644 --- a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md +++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md @@ -16,7 +16,7 @@ shortTitle: Open source contributors ## Joining {% data variables.product.prodname_sponsors %} -{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)." +{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)." {% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." @@ -28,7 +28,7 @@ You can set a goal for your sponsorships. For more information, see "[Managing y ## Sponsorship tiers -{% data reusables.sponsors.tier-details %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)," "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization), and "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)." +{% data reusables.sponsors.tier-details %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)," "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization), and "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)." It's best to set up a range of different sponsorship options, including monthly and one-time tiers, to make it easy for anyone to support your work. In particular, one-time payments allow people to reward your efforts without worrying about whether their finances will support a regular payment schedule. diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md index d77af84276..ca29dba82d 100644 --- a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md +++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md @@ -11,7 +11,7 @@ versions: ghec: '*' children: - /about-github-sponsors-for-open-source-contributors - - /setting-up-github-sponsors-for-your-user-account + - /setting-up-github-sponsors-for-your-personal-account - /setting-up-github-sponsors-for-your-organization - /editing-your-profile-details-for-github-sponsors - /managing-your-sponsorship-goal diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md index b21e4e87b7..38ac9c87d4 100644 --- a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -23,7 +23,7 @@ shortTitle: Set up for organization Organizationとして{% data variables.product.prodname_sponsors %} 参加する招待を受け取ったら、以下のステップを実行すればスポンサードOrganizationになることができます。 -To join {% data variables.product.prodname_sponsors %} as an individual contributor outside an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)." +To join {% data variables.product.prodname_sponsors %} as an individual contributor outside an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)." {% data reusables.sponsors.navigate-to-github-sponsors %} {% data reusables.sponsors.view-eligible-accounts %} diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md similarity index 96% rename from translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md rename to translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md index 679e17e49b..4bf9eee2a2 100644 --- a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md @@ -1,10 +1,11 @@ --- -title: ユーザアカウントに GitHub スポンサーを設定する +title: Setting up GitHub Sponsors for your personal account intro: 'You can become a sponsored developer by joining {% data variables.product.prodname_sponsors %}, completing your sponsored developer profile, creating sponsorship tiers, submitting your bank and tax information, and enabling two-factor authentication for your account on {% data variables.product.product_location %}.' redirect_from: - /articles/becoming-a-sponsored-developer - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account + - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account versions: fpt: '*' ghec: '*' diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md index 79bd57922a..a5fcfac718 100644 --- a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md +++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md @@ -28,7 +28,7 @@ If you are a taxpayer in the United States, you must submit a [W-9](https://www. W-8 BEN and W-8 BEN-E tax forms help {% data variables.product.prodname_dotcom %} determine the beneficial owner of an amount subject to withholding. -If you are a taxpayer in any other region besides the United States, you must submit a [W-8 BEN](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf) (individual) or [W-8 BEN-E](https://www.irs.gov/forms-pubs/about-form-w-8-ben-e) (company) form before you can publish your {% data variables.product.prodname_sponsors %} profile. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-tax-information)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)." {% data variables.product.prodname_dotcom %} から適切なフォームが送信されて期限が通知され、フォームに記入して送信する十分な時間が与えられます。 +If you are a taxpayer in any other region besides the United States, you must submit a [W-8 BEN](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf) (individual) or [W-8 BEN-E](https://www.irs.gov/forms-pubs/about-form-w-8-ben-e) (company) form before you can publish your {% data variables.product.prodname_sponsors %} profile. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-tax-information)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)." {% data variables.product.prodname_dotcom %} から適切なフォームが送信されて期限が通知され、フォームに記入して送信する十分な時間が与えられます。 If you have been assigned an incorrect tax form, [contact {% data variables.product.prodname_dotcom %} Support](https://support.github.com/contact?form%5Bsubject%5D=GitHub%20Sponsors:%20tax%20form&tags=sponsors) to get reassigned the correct one for your situation. diff --git a/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md index 898e65fe0c..facad55b14 100644 --- a/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md +++ b/translations/ja-JP/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md @@ -43,7 +43,7 @@ You can choose whether to display your sponsorship publicly. One-time sponsorshi スポンサードアカウントがあなたのスポンサー層を廃止した場合、あなたが別の層を選択するか、プランをキャンセルするまで、あなたはその層にそのままとどまります。 詳細は「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照してください。 -スポンサーしたいアカウントが {% data variables.product.prodname_sponsors %} にプロフィールを持っていない場合は、アカウント参加を推奨できます。 For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." +スポンサーしたいアカウントが {% data variables.product.prodname_sponsors %} にプロフィールを持っていない場合は、アカウント参加を推奨できます。 For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." {% data reusables.sponsors.sponsorships-not-tax-deductible %} diff --git a/translations/ja-JP/data/features/integration-branch-protection-exceptions.yml b/translations/ja-JP/data/features/integration-branch-protection-exceptions.yml new file mode 100644 index 0000000000..3c6a729fb9 --- /dev/null +++ b/translations/ja-JP/data/features/integration-branch-protection-exceptions.yml @@ -0,0 +1,8 @@ +--- +#Reference: #6665 +#GitHub Apps are supported as actors in all types of exceptions to branch protections +versions: + fpt: '*' + ghec: '*' + ghes: '>= 3.6' + ghae: 'issue-6665' diff --git a/translations/ja-JP/data/features/security-managers.yml b/translations/ja-JP/data/features/security-managers.yml index 6e62d12897..77f12eb126 100644 --- a/translations/ja-JP/data/features/security-managers.yml +++ b/translations/ja-JP/data/features/security-managers.yml @@ -4,5 +4,5 @@ versions: fpt: '*' ghes: '>=3.3' - ghae: 'issue-4999' + ghae: '*' ghec: '*' diff --git a/translations/ja-JP/data/features/security-overview-feature-specific-alert-page.yml b/translations/ja-JP/data/features/security-overview-feature-specific-alert-page.yml new file mode 100644 index 0000000000..1aebf50245 --- /dev/null +++ b/translations/ja-JP/data/features/security-overview-feature-specific-alert-page.yml @@ -0,0 +1,8 @@ +--- +#Reference: #7028. +#Documentation for feature-specific page for security overview at enterprise-level. +versions: + fpt: '*' + ghec: '*' + ghes: '>3.5' + ghae: 'issue-7028' diff --git a/translations/ja-JP/data/product-examples/README.md b/translations/ja-JP/data/product-examples/README.md index 616c8043e6..aacc5dd248 100644 --- a/translations/ja-JP/data/product-examples/README.md +++ b/translations/ja-JP/data/product-examples/README.md @@ -10,7 +10,7 @@ ## 動作の仕組み -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種類の例のみをサポートしています。 +それぞれの製品のサンプルデータは、`data/product-landing-examples`内の、**製品**の名前のサブディレクトリと**example type**という名前のYMLファイル（たとえば`data/product-examples/sponsors/user-examples.yml`あるいは`data/product-examples/codespaces/code-examples.yml`）中で定義されています。 現在は、製品ごとに1種類の例のみをサポートしています。 ### バージョン管理 diff --git a/translations/ja-JP/data/product-examples/code-security/code-examples.yml b/translations/ja-JP/data/product-examples/code-security/code-examples.yml index 523fc73521..6adea39d94 100644 --- a/translations/ja-JP/data/product-examples/code-security/code-examples.yml +++ b/translations/ja-JP/data/product-examples/code-security/code-examples.yml @@ -22,7 +22,7 @@ - GitHub Actions - #Security policies - title: Microsoft security policy template + title: Microsoftセキュリティポリシーテンプレート description: セキュリティポリシーの例 href: /microsoft/repo-templates/blob/main/shared/SECURITY.md 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 ce458f931c..ca231f9681 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: - - '{% 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 %}' + - '{% octicon "alert" aria-label="The alert icon" %} **重大:** 攻撃者が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 %}' - 'パッケージが最新のセキュリティバージョンに更新されました。{% 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-21/17.yml b/translations/ja-JP/data/release-notes/enterprise-server/2-21/17.yml index a261c03bb7..60446af342 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/2-21/17.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/2-21/17.yml @@ -18,8 +18,8 @@ sections: - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 - リポジトリへのプッシュをコマンドラインで行うと、セキュリティアラートが報告されません。 - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://support.github.com/contact) for assistance: + ログのローテーションが新しいログファイルへの移行をサービスに通知するのに失敗し、古いログファイルが使われ続け、最終的にルートディスクの領域が枯渇してしまうことがあります。 + この問題を緩和し、回避するために、以下のコマンドを[管理シェル](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH)で実行するか、 [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us)に連絡して支援を求めてください。 ``` printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate 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 5a816a54cf..167d6c8fda 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: - - '{% 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 %}' + - '{% octicon "alert" aria-label="The alert icon" %} **重大:** 攻撃者が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 %}' - 'パッケージが最新のセキュリティバージョンに更新されました。{% 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-22/9.yml b/translations/ja-JP/data/release-notes/enterprise-server/2-22/9.yml index 35d7c8a615..5ffabae9c5 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/2-22/9.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/2-22/9.yml @@ -24,8 +24,8 @@ sections: - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://support.github.com/contact) for assistance: + ログのローテーションが新しいログファイルへの移行をサービスに通知するのに失敗し、古いログファイルが使われ続け、最終的にルートディスクの領域が枯渇してしまうことがあります。 + この問題を緩和し、回避するために、以下のコマンドを[管理シェル](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH)で実行するか、 [GitHub Enterprise Support](https://enterprise.githubsupport.com/hc/en-us)に連絡して支援を求めてください。 ``` printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/1.yml index 47a0b03d18..a1a2a79120 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/1.yml @@ -35,7 +35,7 @@ sections: - '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が含まれません。' - - 'When maintenance mode is enabled, some services continue to be listed as "active processes". The services identified are expected to run during maintenance mode. If you experience this issue and are unsure, contact [GitHub Enterprise Support](https://support.github.com/contact).' + - 'メンテナンスモードが有効化されているとき、サービスの中に引き続き"active processes"としてリストされるものがあります。特定されたサービスは、メンテナンスモード中にも実行されることが期待されるものです。この問題が生じており、不確実な場合は[GitHub Enterprise Support](https://support.github.com/contact)にお問い合わせください。' - '`/var/log/messages`、`/var/log/syslog`、`/var/log/user.log`への重複したロギングによって、ルートボリュームの使用率が増大します。' - 'ユーザが、すべてのチェックボックスをチェックすることなく必須のメッセージを閉じることができます。' - '[pre-receiveフックスクリプト](/admin/policies/enforcing-policy-with-pre-receive-hooks)は一時ファイルを書くことができず、そのためにスクリプトの実行が失敗することがあります。pre-receiveフックを使うユーザは、ステージング環境でスクリプトが書き込みアクセス権を必要とするかを確認するためのテストをするべきです。' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/17.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/17.yml index 06113476aa..601a4fe206 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/17.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/17.yml @@ -4,18 +4,18 @@ sections: security_fixes: - 'パッケージが最新のセキュリティバージョンに更新されました。{% comment %} https://github.com/github/enterprise2/pull/27034, https://github.com/github/enterprise2/pull/27010 {% endcomment %}' bugs: - - 'Custom pre-receive hooks could have failed due to too restrictive virtual memory or CPU time limits. {% comment %} https://github.com/github/enterprise2/pull/26971, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' - - 'Attempting to wipe all existing configuration settings with `ghe-cleanup-settings` failed to restart the Management Console service. {% comment %} https://github.com/github/enterprise2/pull/26986, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' - - 'During replication teardown via `ghe-repl-teardown` Memcached failed to be restarted. {% comment %} https://github.com/github/enterprise2/pull/26992, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' - - 'During periods of high load, users would receive HTTP 503 status codes when upstream services failed internal healthchecks. {% comment %} https://github.com/github/enterprise2/pull/27081, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' - - 'Pre-receive hook environments were forbidden from calling the cat command via BusyBox on Alpine. {% comment %} https://github.com/github/enterprise2/pull/27114, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' - - 'The external database password was logged in plaintext. {% comment %} https://github.com/github/enterprise2/pull/27172, https://github.com/github/enterprise2/pull/26413 {% endcomment %}' - - 'An erroneous `jq` error message may have been displayed when running `ghe-config-apply`. {% comment %} https://github.com/github/enterprise2/pull/27203, https://github.com/github/enterprise2/pull/26784 {% endcomment %}' - - 'Failing over from a primary Cluster datacenter to a secondary Cluster datacenter succeeds, but then failing back over to the original primary Cluster datacenter failed to promote Elasticsearch indicies. {% comment %} https://github.com/github/github/pull/193180, https://github.com/github/github/pull/192447 {% endcomment %}' - - 'The Site Admin page for repository self-hosted runners returned an HTTP 500. {% comment %} https://github.com/github/github/pull/194205 {% endcomment %}' - - 'In some cases, GitHub Enterprise Administrators attempting to view the `Dormant users` page received `502 Bad Gateway` or `504 Gateway Timeout` response. {% comment %} https://github.com/github/github/pull/194259, https://github.com/github/github/pull/193609 {% endcomment %}' + - 'カスタムのpre-receive フックが、制約の厳しすぎる仮想メモリもしくはCPU時間の制限のために失敗することがありました。{% comment %}https://github.com/github/enterprise2/pull/26971, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' + - '`ghe-cleanup-settings`で既存のすべての設定を消去しようとすると、Management Consoleサービスの再起動に失敗しました。{% comment %} https://github.com/github/enterprise2/pull/26986, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' + - '`ghe-repl-teardown` でのレプリケーションのティアダウンの間に、Memcachedが再起動に失敗しました。{% comment %} https://github.com/github/enterprise2/pull/26992, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' + - '高負荷の間、上流のサービスが内部的なヘルスチェックに失敗した際に、ユーザがHTTPステータスコード503を受信することになります。{% comment %} https://github.com/github/enterprise2/pull/27081, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' + - 'pre-receiveフック環境環境が、Alpine上のBusyBoxからcatコマンドを呼び出すことが禁じられていました。{% comment %} https://github.com/github/enterprise2/pull/27114, https://github.com/github/enterprise2/pull/27094 {% endcomment %}' + - '外部のデータベースパスワードが平文でログに記録されていました。{% comment %} https://github.com/github/enterprise2/pull/27172, https://github.com/github/enterprise2/pull/26413 {% endcomment %}' + - '`ghe-config-apply`を実行した際に、誤った`jq`のエラーメッセージが表示されることがありました。{% comment %} https://github.com/github/enterprise2/pull/27203, https://github.com/github/enterprise2/pull/26784 {% endcomment %}' + - 'プライマリのクラスタデータセンターからセカンダリのクラスタデータセンターへのフェイルオーバーは成功しますが、その後オリジナルのプライマリクラスタデータセンターへのフェイルバックがElasticsearchインデックスの昇格に失敗しました。{% comment %} https://github.com/github/github/pull/193180, https://github.com/github/github/pull/192447 {% endcomment %}' + - 'リポジトリのセルフホストランナーのサイトアドミンページがHTTP 500を返します。{% comment %} https://github.com/github/github/pull/194205 {% endcomment %}' + - '場合によって、`Dormant users` ページを閲覧しようとしたGitHub Enterpriseの管理者が`502 Bad Gateway`もしくは`504 Gateway Timeout`レスポンスを受信しました。{% comment %} https://github.com/github/github/pull/194259, https://github.com/github/github/pull/193609 {% endcomment %}' changes: - - 'More effectively delete Webhook logs that fall out of the Webhook log retention window. {% comment %} https://github.com/github/enterprise2/pull/27157 {% endcomment %}' + - 'webhookログのリテンションウィンドウから外れたwebhookログを、より効率的に削除します。{% comment %} https://github.com/github/enterprise2/pull/27157 {% endcomment %}' known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/18.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/18.yml index f05044e5b5..d89791ccd8 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/18.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/18.yml @@ -2,10 +2,10 @@ date: '2021-10-28' sections: security_fixes: - - 'Several known weak SSH public keys have been added to the deny list and can no longer be registered. In addition, versions of GitKraken known to generate weak SSH keys (7.6.x, 7.7.x and 8.0.0) have been blocked from registering new public keys.' + - 'いくつかの既知の弱いSSH公開鍵が拒否リストに追加され、登録できなくなりました。加えて、弱いSSHキーを生成することが知られているGitKrakenのバージョン（7.6.x、7.7.x、8.0.0）による新しい公開鍵の登録がブロックされました。' - 'パッケージは最新のセキュリティバージョンにアップデートされました。' bugs: - - 'Several parts of the application were unusable for users who are owners of many organizations.' + - '多くのOrganizationのオーナーであるユーザは、アプリケーションの一部を使用できませんでした。' known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/19.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/19.yml index 46b4b572e5..a5b796aa23 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/19.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/19.yml @@ -1,9 +1,8 @@ ---- date: '2021-11-09' sections: security_fixes: - A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870. - - パッケージは最新のセキュリティバージョンにアップデートされました。 + - Packages have been updated to the latest security versions. bugs: - Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration. - Unicorn worker counts might have been set incorrectly in clustering mode. @@ -15,10 +14,10 @@ sections: - Hookshot Go sent distribution type metrics that Collectd could not handle, which caused a ballooning of parsing errors. - Public repositories displayed unexpected results from {% data variables.product.prodname_secret_scanning %} with a type of `Unknown Token`. 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 フックに失敗するものが生じることがあります。 + - 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. + - When a replica node is offline in a high availability configuration, {% data variables.product.product_name %} may still route {% data variables.product.prodname_pages %} requests to the offline node, reducing the availability of {% data variables.product.prodname_pages %} for users. + - 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-0/2.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/2.yml index d0062c192b..f12401a46a 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/2.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/2.yml @@ -27,7 +27,7 @@ sections: - 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が含まれません。 - - When maintenance mode is enabled, some services continue to be listed as "active processes". The services identified are expected to run during maintenance mode. If you experience this issue and are unsure, contact [GitHub Enterprise Support](https://support.github.com/contact). + - メンテナンスモードが有効化されているとき、サービスの中に引き続き"active processes"としてリストされるものがあります。特定されたサービスは、メンテナンスモード中にも実行されることが期待されるものです。この問題が生じており、不確実な場合は[GitHub Enterprise Support](https://support.github.com/contact)にお問い合わせください。 - ノートブックに非ASCIIのUTF-8文字が含まれている場合、Web UI中でのJupyter Notebookのレンダリングが失敗することがあります。 - Web UIでのreStructuredText (RST) のレンダリングが失敗し、代わりにRSTのマークアップテキストがそのまま表示されることがあります。 - Pagesの古いビルドがクリーンアップされず、ユーザディスク(`/data/user/`)を使い切ってしまうことがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/20.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/20.yml index d825693ff6..7e440f4ab4 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/20.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/20.yml @@ -4,13 +4,13 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - Pre-receive hooks would fail due to undefined `PATH`. - - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' - - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. - - Some critical services may not have been available on backend nodes in GHES Cluster. + - pre-receiveフックが`PATH`の未定義で失敗します。 + - 'インスタンスが以前にレプリカとして設定されていた場合、`ghe-repl-setup`を実行すると`cannot create directory /data/user/elasticsearch: File exists`というエラーが返されます。' + - 大規模なクラスタ環境に置いて、一部のフロントエンドノードで認証バックエンドが利用できなくなることがあります。 + - GHESクラスタにおいて、一部の重要なサービスがバックエンドノードで利用できないことがあります。 changes: - - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. - - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. + - '`ghe-cluster-suport-bundle`でクラスタSupport Bundleを作成する際の`gzip`圧縮の追加外部レイヤーは、デフォルトでオフになりました。この外部圧縮は、ghe-cluster-suport-bundle -c`コマンドラインオプションで適用できます。' + - 体験を改善するためのモバイルアプリケーションのデータ収集についてユーザにリマインドするために、管理コンソールにテキストを追加しました。 - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09] known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 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 d2f0b70c38..0d00644d1d 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,8 +2,8 @@ date: '2021-12-13' sections: security_fixes: - - '{% 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.' + - '{% octicon "alert" aria-label="The alert icon" %} **重大** [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)として特定されたLOg4jライブラリのリモートコード実行の脆弱性は、3.3.1以前のすべてのバージョンの{% data variables.product.prodname_ghe_server %}に影響します。Log4jライブラリは、{% data variables.product.prodname_ghe_server %}インスタンス上で動作するオープンソースのサービスで使われています。この脆弱性は{% data variables.product.prodname_ghe_server %}バージョン3.0.22、3.1.14、3.2.6、3.3.1で修正されました。詳しい情報についてはGitHub Blogの[このポスト](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/)を参照してください。' + - '** 2021年12月17日更新 **: このリリースでの修正は、このリリース後に公開された[CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046)も緩和します。CVE-2021-44228とCVE-2021-45046をどちらも緩和するために、{% data variables.product.prodname_ghe_server %}に追加のアップグレードは必要ありません。' 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 index 8dec6e1579..3c965130ac 100644 --- 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 @@ -4,13 +4,13 @@ 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. + - '`nginx`が手動で再起動されるまで、MySQLのシークレットのローテーション後にPagesが利用できなくなります。' + - ISO 8601の日付でメンテナンススケジュールを設定すると、タイムゾーンがUTCに変換されないことから実際にスケジュールされる時間が一致しません。 + - '`ghe-cluster-each`を使ってホットパッチをインストールすると、バージョン番号が正しく更新されません。' + - '`cloud-config.service`に関する誤ったエラーメッセージがコンソールに出力されます。' + - CAS認証を使用し、"Reactivate suspended users"オプションが有効化されている場合、サスペンドされたユーザは自動的に際アクティベートされませんでした。 changes: - - The GitHub Connect data connection record now includes a count of the number of active and dormant users and the configured dormancy period. + - GitHub Connectのデータ接続レコードに、アクティブ及び休眠ユーザ数と、設定された休眠期間が含まれるようになりました。 known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-0/3.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-0/3.yml index 33d66f69d3..cf568f3916 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-0/3.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-0/3.yml @@ -26,14 +26,14 @@ sections: - 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が含まれません。 - - When maintenance mode is enabled, some services continue to be listed as "active processes". The services identified are expected to run during maintenance mode. If you experience this issue and are unsure, contact [GitHub Enterprise Support](https://support.github.com/contact). + - メンテナンスモードが有効化されているとき、サービスの中に引き続き"active processes"としてリストされるものがあります。特定されたサービスは、メンテナンスモード中にも実行されることが期待されるものです。この問題が生じており、不確実な場合は[GitHub Enterprise Support](https://support.github.com/contact)にお問い合わせください。 - ノートブックに非ASCIIのUTF-8文字が含まれている場合、Web UI中でのJupyter Notebookのレンダリングが失敗することがあります。 - Web UIでのreStructuredText (RST) のレンダリングが失敗し、代わりにRSTのマークアップテキストがそのまま表示されることがあります。 - Pagesの古いビルドがクリーンアップされず、ユーザディスク(`/data/user/`)を使い切ってしまうことがあります。 - Pull Requestをマージした後にブランチを削除すると、ブランチの削除は成功しているにもかかわらずエラーメッセージが表示されます。 - | - Log rotation may fail to signal services to transition to new log files, leading to older log files continuing to be used, and eventual root disk space exhaustion. - To remedy and/or prevent this issue, run the following commands in the [administrative shell](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH), or contact [GitHub Enterprise Support](https://support.github.com/) for assistance: + ログのローテーションが新しいログファイルへの移行をサービスに通知するのに失敗し、古いログファイルが使われ続け、最終的にルートディスクの領域が枯渇してしまうことがあります。 + この問題を緩和し、回避するために、以下のコマンドを[管理シェル](https://docs.github.com/en/enterprise-server/admin/configuration/accessing-the-administrative-shell-ssh) (SSH)で実行するか、 [GitHub Enterprise Support](https://support.github.com/)に連絡して支援を求めてください。 ``` printf "PATH=/usr/local/sbin:/usr/local/bin:/usr/local/share/enterprise:/usr/sbin:/usr/bin:/sbin:/bin\n29,59 * * * * root /usr/sbin/logrotate /etc/logrotate.conf\n" | sudo sponge /etc/cron.d/logrotate diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/21.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/21.yml new file mode 100644 index 0000000000..b6e1956267 --- /dev/null +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/21.yml @@ -0,0 +1,24 @@ +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - Packages have been updated to the latest security versions. + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not supported. + - Support bundles now include the row count of tables stored in MySQL. + 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 %} instance 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 {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} 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/11.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml index a4369b76c8..e0bba6aaf3 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml @@ -15,10 +15,10 @@ sections: - In a cluster environment, Git LFS operations could fail with failed internal API calls that crossed multiple web nodes. - Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges. - In some cluster topologies, webhook delivery information was not available. - - In HA configurations, tearing down a replica would fail if {% data variables.product.prodname_actions %} had previously been enabled. + - HA設定では、{% data variables.product.prodname_actions %}が以前に有効化されていた場合、レプリカの破棄が失敗します。 - Elasticsearch health checks would not allow a yellow cluster status when running migrations. - Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account. - - When using `ghe-migrator` or exporting from {% data variables.product.prodname_dotcom_the_website %}, a long-running export would fail when data was deleted mid-export. + - '`ghe-migrator`を使う場合、もしくは{% data variables.product.prodname_dotcom_the_website %}からエクスポートする場合、データがエクスポート中に削除されると実行に長時間かかるエクスポートが失敗します。' - The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job. - Links to inaccessible pages were removed. - Navigating away from a comparison of two commits in the web UI would have the diff persist in other pages. diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml index 175de423c6..d6625e0168 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml @@ -11,7 +11,7 @@ sections: - Creating an impersonation OAuth token using the Enterprise Administration REST API worked incorrectly when an integration matching the OAuth Application ID already existed. changes: - Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log. - - When attempting to cache a value larger than the maximum allowed in Memcached, an error was raised however the key was not reported. + - Memcachedで許されている最大よりも長い値をキャッシュしようとするとエラーが生じますが、キーは報告されませんでした。 - The {% data variables.product.prodname_codeql %} starter workflow no longer errors even if the default token permissions for {% data variables.product.prodname_actions %} are not used. - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions. known_issues: diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/13.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/13.yml new file mode 100644 index 0000000000..bb94ea5348 --- /dev/null +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/13.yml @@ -0,0 +1,27 @@ +--- +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - パッケージは最新のセキュリティバージョンにアップデートされました。 + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - Videos uploaded to issue comments would not be rendered properly. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. + - Support bundles now include the row count of tables stored in MySQL. + - Dependency Graph can now be enabled without vulnerability data, allowing you to see what dependencies are in use and at what versions. Enabling Dependency Graph without enabling {% data variables.product.prodname_github_connect %} will **not** provide vulnerability information. + known_issues: + - 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をクローズできませんでした。 + - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/2.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/2.yml index a4cafdab7d..22fea8de2b 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/2.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/2.yml @@ -3,12 +3,12 @@ date: '2021-10-28' sections: security_fixes: - 'It was possible for cleartext passwords to end up in certain log files.' - - 'Several known weak SSH public keys have been added to the deny list and can no longer be registered. In addition, versions of GitKraken known to generate weak SSH keys (7.6.x, 7.7.x and 8.0.0) have been blocked from registering new public keys.' + - 'いくつかの既知の弱いSSH公開鍵が拒否リストに追加され、登録できなくなりました。加えて、弱いSSHキーを生成することが知られているGitKrakenのバージョン（7.6.x、7.7.x、8.0.0）による新しい公開鍵の登録がブロックされました。' - 'パッケージは最新のセキュリティバージョンにアップデートされました。' bugs: - 'Restore might fail for enterprise server in clustering mode if orchestrator is not healthily.' - 'Codespaces links were displayed in organization settings.' - - 'Several parts of the application were unusable for users who are owners of many organizations.' + - '多くのOrganizationのオーナーであるユーザは、アプリケーションの一部を使用できませんでした。' - 'Fixed a link to https://docs.github.com.' changes: - 'Browsing and job performance optimizations for repositories with many refs.' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/3.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/3.yml index 5cab1e0db5..5c1b3f7a32 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/3.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/3.yml @@ -1,9 +1,8 @@ ---- date: '2021-11-09' sections: security_fixes: - A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870. - - パッケージは最新のセキュリティバージョンにアップデートされました。 + - Packages have been updated to the latest security versions. bugs: - Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration. - Unicorn worker counts might have been set incorrectly in clustering mode. @@ -12,7 +11,7 @@ sections: - Upgrading from {% data variables.product.prodname_ghe_server %} 2.x to 3.x failed when there were UTF8 characters in an LDAP configuration. - Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations. - The documentation link for Server Statistics was broken. - - 'When a new tag was created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload did not display a correct `head_commit` object. Now, when a new tag is created, the push webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload''s `after` commit.' + - When a new tag was created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload did not display a correct `head_commit` object. Now, when a new tag is created, the push webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload's `after` commit. - The enterprise audit log page would not display audit events for {% data variables.product.prodname_secret_scanning %}. - There was an insufficient job timeout for replica repairs. - A repository's releases page would return a 500 error when viewing releases. @@ -22,10 +21,10 @@ sections: changes: - Kafka configuration improvements have been added. When deleting repositories, package files are now immediately deleted from storage account to free up space. `DestroyDeletedPackageVersionsJob` now deletes package files from storage account for stale packages along with metadata records. 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 フックに失敗するものが生じることがあります。 + - 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. + - 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. + - 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/4.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/4.yml index 81a7d69e59..4464bde745 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/4.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/4.yml @@ -5,20 +5,20 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - Running `ghe-repl-start` or `ghe-repl-status` would sometimes return errors connecting to the database when GitHub Actions was enabled. - - Pre-receive hooks would fail due to undefined `PATH`. - - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' + - GitHub Actionsが有効化されている場合、`ghe-repl-start`もしくは`ghe-repl-status`を実行すると、データベースへの接続でエラーが返されることがあります。 + - pre-receiveフックが`PATH`の未定義で失敗します。 + - 'インスタンスが以前にレプリカとして設定されていた場合、`ghe-repl-setup`を実行すると`cannot create directory /data/user/elasticsearch: File exists`というエラーが返されます。' - 'Running `ghe-support-bundle` returned an error: `integer expression expected`.' - - 'After setting up a high availability replica, `ghe-repl-status` included an error in the output: `unexpected unclosed action in command`.' - - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. - - Some critical services may not have been available on backend nodes in GHES Cluster. + - '高可用性レプリカをセットアップした後、`ghe-repl-status`は`unexpected unclosed action in command`というエラーを出力に含めました。' + - 大規模なクラスタ環境に置いて、一部のフロントエンドノードで認証バックエンドが利用できなくなることがあります。 + - GHESクラスタにおいて、一部の重要なサービスがバックエンドノードで利用できないことがあります。 - The repository permissions to the user returned by the `/repos` API would not return the full list. - The `childTeams` connection on the `Team` object in the GraphQL schema produced incorrect results under some circumstances. - In a high availability configuration, repository maintenance always showed up as failed in stafftools, even when it succeeded. - User defined patterns would not detect secrets in files like `package.json` or `yarn.lock`. changes: - - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. - - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. + - '`ghe-cluster-suport-bundle`でクラスタSupport Bundleを作成する際の`gzip`圧縮の追加外部レイヤーは、デフォルトでオフになりました。この外部圧縮は、ghe-cluster-suport-bundle -c`コマンドラインオプションで適用できます。' + - 体験を改善するためのモバイルアプリケーションのデータ収集についてユーザにリマインドするために、管理コンソールにテキストを追加しました。 - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09] known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 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 46da63fcf0..c423911980 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,8 +2,8 @@ date: '2021-12-13' sections: security_fixes: - - '{% 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.' + - '{% octicon "alert" aria-label="The alert icon" %} **重大** [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)として特定されたLOg4jライブラリのリモートコード実行の脆弱性は、3.3.1以前のすべてのバージョンの{% data variables.product.prodname_ghe_server %}に影響します。Log4jライブラリは、{% data variables.product.prodname_ghe_server %}インスタンス上で動作するオープンソースのサービスで使われています。この脆弱性は{% data variables.product.prodname_ghe_server %}バージョン3.0.22、3.1.14、3.2.6、3.3.1で修正されました。詳しい情報についてはGitHub Blogの[このポスト](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/)を参照してください。' + - '** 2021年12月17日更新 **: このリリースでの修正は、このリリース後に公開された[CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046)も緩和します。CVE-2021-44228とCVE-2021-45046をどちらも緩和するために、{% data variables.product.prodname_ghe_server %}に追加のアップグレードは必要ありません。' 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 index 78a2cdf79b..d021b2dab0 100644 --- 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 @@ -4,18 +4,18 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - Pages would become unavailable following a MySQL secret rotation until `nginx` was manually restarted. + - '`nginx`が手動で再起動されるまで、MySQLのシークレットのローテーション後にPagesが利用できなくなります。' - 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`. + - ISO 8601の日付でメンテナンススケジュールを設定すると、タイムゾーンがUTCに変換されないことから実際にスケジュールされる時間が一致しません。 + - '`cloud-config.service`に関する誤ったエラーメッセージがコンソールに出力されます。' + - '`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. + - CAS認証を使用し、"Reactivate suspended users"オプションが有効化されている場合、サスペンドされたユーザは自動的に際アクティベートされませんでした。 - 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. + - GitHub Connectのデータ接続レコードに、アクティブ及び休眠ユーザ数と、設定された休眠期間が含まれるようになりました。 known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}で、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/9.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/9.yml index aca3fb391f..702690ea4c 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/9.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/9.yml @@ -7,7 +7,7 @@ sections: bugs: - GitHub Packages storage settings could not be validated and saved in the Management Console when Azure Blob Storage was used. - The mssql.backup.cadence configuration option failed ghe-config-check with an invalid characterset warning. - - Fixes SystemStackError (stack too deep) when getting more than 2^16 keys from memcached. + - memcachedから2^16以上のキーを取得する際のSystemStackError（スタックが深すぎる）を修正しました。 changes: - Secret scanning will skip scanning ZIP and other archive files for secrets. known_issues: diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml index c025012731..ba674017b6 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml @@ -91,7 +91,7 @@ sections: - '{% data variables.product.prodname_ghe_server %} now automatically generates a table of contents for Wikis, based on headings.' - When dragging and dropping files into a Markdown editor, such as images and videos, {% data variables.product.prodname_ghe_server %} now uses the mouse pointer location instead of the cursor location when placing the file. - - heading: 'Issues and pull requests changes' + heading: 'Issue及びPull Requestの変更' notes: - 'You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)."' - | @@ -107,7 +107,7 @@ sections: - You can now filter pull request searches to only include pull requests you are directly requested to review. - Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)." - - heading: 'GitHub Actions changes' + heading: 'GitHub Actionsの変更' notes: - You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)." - 'Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise''s self-hosted runners.' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml index c8eaa66f96..d0bf8c7ec0 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml @@ -83,7 +83,7 @@ sections: - '{% data variables.product.prodname_ghe_server %} now automatically generates a table of contents for Wikis, based on headings.' - When dragging and dropping files into a Markdown editor, such as images and videos, {% data variables.product.prodname_ghe_server %} now uses the mouse pointer location instead of the cursor location when placing the file. - - heading: 'Issues and pull requests changes' + heading: 'Issue及びPull Requestの変更' notes: - 'You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)."' - | @@ -99,7 +99,7 @@ sections: - You can now filter pull request searches to only include pull requests you are directly requested to review. - Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)." - - heading: 'GitHub Actions changes' + heading: 'GitHub Actionsの変更' notes: - You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)." - 'Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise''s self-hosted runners.' 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 a982395ba2..06f1ebd5d7 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,8 +2,8 @@ date: '2021-12-13' sections: security_fixes: - - '{% 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.' + - '{% octicon "alert" aria-label="The alert icon" %} **重大** [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)として特定されたLOg4jライブラリのリモートコード実行の脆弱性は、3.3.1以前のすべてのバージョンの{% data variables.product.prodname_ghe_server %}に影響します。Log4jライブラリは、{% data variables.product.prodname_ghe_server %}インスタンス上で動作するオープンソースのサービスで使われています。この脆弱性は{% data variables.product.prodname_ghe_server %}バージョン3.0.22、3.1.14、3.2.6、3.3.1で修正されました。詳しい情報についてはGitHub Blogの[このポスト](https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/)を参照してください。' + - '** 2021年12月17日更新 **: このリリースでの修正は、このリリース後に公開された[CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046)も緩和します。CVE-2021-44228とCVE-2021-45046をどちらも緩和するために、{% data variables.product.prodname_ghe_server %}に追加のアップグレードは必要ありません。' 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. 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 index 6f3db7eefc..db55dc799f 100644 --- 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 @@ -5,18 +5,18 @@ sections: - '**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. + - '`nginx`が手動で再起動されるまで、MySQLのシークレットのローテーション後にPagesが利用できなくなります。' - 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`. + - ISO 8601の日付でメンテナンススケジュールを設定すると、タイムゾーンがUTCに変換されないことから実際にスケジュールされる時間が一致しません。 + - '`cloud-config.service`に関する誤ったエラーメッセージがコンソールに出力されます。' + - '`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. + - CAS認証を使用し、"Reactivate suspended users"オプションが有効化されている場合、サスペンドされたユーザは自動的に際アクティベートされませんでした。 - 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. + - GitHub Connectのデータ接続レコードに、アクティブ及び休眠ユーザ数と、設定された休眠期間が含まれるようになりました。 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. diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/4.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/4.yml index f62ba222ec..cbe3af6e8f 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/4.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/4.yml @@ -7,7 +7,7 @@ sections: bugs: - GitHub Packages storage settings could not be validated and saved in the Management Console when Azure Blob Storage was used. - The mssql.backup.cadence configuration option failed ghe-config-check with an invalid characterset warning. - - Fixes SystemStackError (stack too deep) when getting more than 2^16 keys from memcached. + - memcachedから2^16以上のキーを取得する際のSystemStackError（スタックが深すぎる）を修正しました。 - A number of select menus across the site rendered incorrectly and were not functional. changes: - Dependency Graph can now be enabled without vulnerability data, allowing customers to see what dependencies are in use and at what versions. Enabling Dependency Graph without enabling GitHub Connect will *not* provide vulnerability information. diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/7.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/7.yml index 647143eb91..985980238b 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/7.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/7.yml @@ -17,7 +17,7 @@ sections: - Repository cache servers could serve data from non-cache locations even when the data was available in the local cache location. changes: - Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log. - - When attempting to cache a value larger than the maximum allowed in Memcached, an error was raised however the key was not reported. + - Memcachedで許されている最大よりも長い値をキャッシュしようとするとエラーが生じますが、キーは報告されませんでした。 - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions. 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/8.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml new file mode 100644 index 0000000000..150826850d --- /dev/null +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml @@ -0,0 +1,34 @@ +--- +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - パッケージは最新のセキュリティバージョンにアップデートされました。 + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + - Videos uploaded to issue comments would not be rendered properly. + - When using the file finder on a repository page, typing the backspace key within the search field would result in search results being listed multiple times and cause rendering problems. + - When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events. + - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. + - Support bundles now include the row count of tables stored in MySQL. + - When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects. + - The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload. + 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をクローズできませんでした。 + - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% 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.' + - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/0-rc1.yml index 6ae7356298..325ffe27e2 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/0-rc1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/0-rc1.yml @@ -84,12 +84,12 @@ sections: - When typing the name of a {% data variables.product.prodname_dotcom %} user in issues, pull requests and discussions, the @mention suggester now ranks existing participants higher than other {% data variables.product.prodname_dotcom %} users, so that it's more likely the user you're looking for will be listed. - Right-to-left languages are now supported natively in Markdown files, issues, pull requests, discussions, and comments. - - heading: 'Issues and pull requests changes' + heading: 'Issue及びPull Requestの変更' notes: - The diff setting to hide whitespace changes in the pull request "Files changed" tab is now retained for your user account for that pull request. The setting you have chosen is automatically reapplied if you navigate away from the page and then revisit the "Files changed" tab of the same pull request. - When using auto assignment for pull request code reviews, you can now choose to only notify requested team members independently of your auto assignment settings. This setting is useful in scenarios where many users are auto assigned but not all users require notification. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-team-member-pull-request-review-notifications-can-be-configured-independently-of-auto-assignment/)." - - heading: 'Branches changes' + heading: 'ブランチの変更' notes: - 'Organization and repository administrators can now trigger webhooks to listen for changes to branch protection rules on their repositories. For more information, see the "[branch_protection_rule](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#branch_protection_rule)" event in the webhooks events and payloads documentation.' - When configuring protected branches, you can now enforce that a required status check is provided by a specific {% data variables.product.prodname_github_app %}. If a status is then provided by a different application, or by a user via a commit status, merging is prevented. This ensures all changes are validated by the intended application. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-12-01-ensure-required-status-checks-provided-by-the-intended-app/)." @@ -98,7 +98,7 @@ sections: - Administrators can now allow only specific users and teams to force push to a repository. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-12-21-specify-who-can-force-push-to-a-repository/)." - When requiring pull requests for all changes to a protected branch, administrators can now choose if approved reviews are also a requirement. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-require-pull-requests-without-requiring-reviews/)." - - heading: 'GitHub Actions changes' + heading: 'GitHub Actionsの変更' notes: - '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} for the `create`, `deployment`, and `deployment_status` events now always receive a read-only token and no secrets. Similarly, workflows triggered by {% data variables.product.prodname_dependabot %} for the `pull_request_target` event on pull requests where the base ref was created by {% data variables.product.prodname_dependabot %}, now always receive a read-only token and no secrets. These changes are designed to prevent potentially malicious code from executing in a privileged workflow. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."' - Workflow runs on `push` and `pull_request` events triggered by {% data variables.product.prodname_dependabot %} will now respect the permissions specified in your workflows, allowing you to control how you manage automatic dependency updates. The default token permissions will remain read-only. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-06-github-actions-workflows-triggered-by-dependabot-prs-will-respect-permissions-key-in-workflows/)." diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/0.yml index 1609c578a1..edec18b18b 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/0.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/0.yml @@ -83,12 +83,12 @@ sections: - When typing the name of a {% data variables.product.prodname_dotcom %} user in issues, pull requests and discussions, the @mention suggester now ranks existing participants higher than other {% data variables.product.prodname_dotcom %} users, so that it's more likely the user you're looking for will be listed. - Right-to-left languages are now supported natively in Markdown files, issues, pull requests, discussions, and comments. - - heading: 'Issues and pull requests changes' + heading: 'Issue及びPull Requestの変更' notes: - The diff setting to hide whitespace changes in the pull request "Files changed" tab is now retained for your user account for that pull request. The setting you have chosen is automatically reapplied if you navigate away from the page and then revisit the "Files changed" tab of the same pull request. - When using auto assignment for pull request code reviews, you can now choose to only notify requested team members independently of your auto assignment settings. This setting is useful in scenarios where many users are auto assigned but not all users require notification. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-team-member-pull-request-review-notifications-can-be-configured-independently-of-auto-assignment/)." - - heading: 'Branches changes' + heading: 'ブランチの変更' notes: - 'Organization and repository administrators can now trigger webhooks to listen for changes to branch protection rules on their repositories. For more information, see the "[branch_protection_rule](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#branch_protection_rule)" event in the webhooks events and payloads documentation.' - When configuring protected branches, you can now enforce that a required status check is provided by a specific {% data variables.product.prodname_github_app %}. If a status is then provided by a different application, or by a user via a commit status, merging is prevented. This ensures all changes are validated by the intended application. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-12-01-ensure-required-status-checks-provided-by-the-intended-app/)." @@ -97,7 +97,7 @@ sections: - Administrators can now allow only specific users and teams to force push to a repository. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-12-21-specify-who-can-force-push-to-a-repository/)." - When requiring pull requests for all changes to a protected branch, administrators can now choose if approved reviews are also a requirement. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-require-pull-requests-without-requiring-reviews/)." - - heading: 'GitHub Actions changes' + heading: 'GitHub Actionsの変更' notes: - '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} for the `create`, `deployment`, and `deployment_status` events now always receive a read-only token and no secrets. Similarly, workflows triggered by {% data variables.product.prodname_dependabot %} for the `pull_request_target` event on pull requests where the base ref was created by {% data variables.product.prodname_dependabot %}, now always receive a read-only token and no secrets. These changes are designed to prevent potentially malicious code from executing in a privileged workflow. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."' - Workflow runs on `push` and `pull_request` events triggered by {% data variables.product.prodname_dependabot %} will now respect the permissions specified in your workflows, allowing you to control how you manage automatic dependency updates. The default token permissions will remain read-only. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-06-github-actions-workflows-triggered-by-dependabot-prs-will-respect-permissions-key-in-workflows/)." diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml index 4a33f1fb4d..1b6fccb745 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml @@ -73,5 +73,10 @@ sections: Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. To start a repository maintenance task manually, browse to `https:///stafftools/repositories///network` for each affected repository and click the Schedule button. + - + heading: Theme picker for GitHub Pages has been removed + notes: + - | + The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)." backups: - '{% data variables.product.prodname_ghe_server %} 3.4 requires at least [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml new file mode 100644 index 0000000000..637bc1f3ab --- /dev/null +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml @@ -0,0 +1,41 @@ +--- +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - パッケージは最新のセキュリティバージョンにアップデートされました。 + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. + - When adding custom patterns and providing non-UTF8 test strings, match highlighting was incorrect. + - LDAP users with an underscore character (`_`) in their user names can now login successfully. + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - After enabling SAML encrypted assertions with Azure as identity provider, the sign in page would fail with a `500` error. + - Character key shortcut preferences weren't respected. + - Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + - Videos uploaded to issue comments would not be rendered properly. + - When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events. + - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - The Nomad allocation timeout for Dependency Graph has been increased to ensure post-upgrade migrations can complete. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. + - Support bundles now include the row count of tables stored in MySQL. + - When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects. + - The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload. + known_issues: + - 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をクローズできませんでした。 + - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 + - | + When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11] + + To work around this problem, you can take one of the two following actions. + - Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute. + - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL. diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml index 942804231b..53671dabd3 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -333,6 +333,11 @@ sections: notes: - | The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, 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)." + - + heading: Theme picker for GitHub Pages has been removed + notes: + - | + The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)." known_issues: - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/github-ae/2021-06/2021-12-06.yml b/translations/ja-JP/data/release-notes/github-ae/2021-06/2021-12-06.yml index 9205e8151d..383b7fc827 100644 --- a/translations/ja-JP/data/release-notes/github-ae/2021-06/2021-12-06.yml +++ b/translations/ja-JP/data/release-notes/github-ae/2021-06/2021-12-06.yml @@ -2,7 +2,7 @@ date: '2021-12-06' friendlyDate: 'December 6, 2021' title: 'December 6, 2021' -currentWeek: true +currentWeek: false sections: features: - @@ -102,7 +102,7 @@ sections: - | People with maintain access can now manage the repository-level "Allow auto-merge" setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only people with admin access could manage this setting. Additionally, this setting can now by controlled using the "[Create a repository](/rest/reference/repos#create-an-organization-repository)" and "[Update a repository](/rest/reference/repos#update-a-repository)" REST APIs. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository)." - | - The assignees selection for issues and pull requests now supports type ahead searching so you can find users in your organization faster. Additionally, search result rankings have been updated to prefer matches at the start of a person's username or profile name. + Issue及びPull Requestのアサインされた人のセクションは先行タイプ検索をサポートしたので、Organization内のユーザを素早く見つけられるようになりました。加えて、検索結果のランキングはユーザのユーザ名もしくはプロフィール名の先頭へのマッチを優先するように更新されました。 - heading: 'リポジトリ' notes: diff --git a/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml b/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml new file mode 100644 index 0000000000..40645a176d --- /dev/null +++ b/translations/ja-JP/data/release-notes/github-ae/2022-05/2022-05-17.yml @@ -0,0 +1,190 @@ +--- +date: '2022-05-17' +friendlyDate: 'May 17, 2022' +title: 'May 17, 2022' +currentWeek: true +sections: + features: + - + heading: 'GitHub Advanced Security features are generally available' + notes: + - | + Code scanning and secret scanning are now generally available for GitHub AE. For more information, see "[About code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)." + - | + Custom patterns for secret scanning is now generally available. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + - + heading: 'View all code scanning alerts for a pull request' + notes: + - | + You can now find all code scanning alerts associated with your pull request with the new pull request filter on the code scanning alerts page. The pull request checks page shows the alerts introduced in a pull request, but not existing alerts on the pull request branch. The new "View all branch alerts" link on the Checks page takes you to the code scanning alerts page with the specific pull request filter already applied, so you can see all the alerts associated with your pull request. This can be useful to manage lots of alerts, and to see more detailed information for individual alerts. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)." + - + heading: 'Security overview for organizations' + notes: + - | + GitHub Advanced Security now offers an organization-level view of the application security risks detected by code scanning, Dependabot, and secret scanning. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. + + In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + + ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) + - + heading: '依存関係グラフ' + notes: + - | + Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." + - + heading: 'Dependabotアラート' + notes: + - | + Dependabot alerts can now notify you of vulnerabilities in your dependencies on GitHub AE. You can enable Dependabot alerts by enabling the dependency graph, enabling GitHub Connect, and syncing vulnerabilities from the GitHub Advisory Database. This feature is in beta and subject to change. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)." + + After you enable Dependabot alerts, members of your organization will receive notifications any time a new vulnerability that affects their dependencies is added to the GitHub Advisory Database or a vulnerable dependency is added to their manifest. Members can customize notification settings. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)." + - + heading: 'Security manager role for organizations' + notes: + - | + Organizations can now grant teams permission to manage security alerts and settings on all their repositories. The "security manager" role can be applied to any team and grants the team's members the following permissions. + + - Read access on all repositories in the organization + - Write access on all security alerts in the organization + - Access to the organization-level security tab + - Write access on security settings at the organization level + - Write access on security settings at the repository level + + For more information, see "[Managing security managers in your organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." + - + heading: 'Ephemeral runners and autoscaling webhooks for GitHub Actions' + notes: + - | + GitHub AE now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. + + Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, GitHub AE automatically unregisteres ephemeral runners, allowing you to perform any post-job management. + + You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to job requests from GitHub Actions. + + For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)." + - + heading: 'Composite actions for GitHub Actions' + notes: + - | + You can reduce duplication in your workflows by using composition to reference other actions. Previously, actions written in YAML could only use scripts. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)." + - + heading: 'New token scope for management of self-hosted runners' + notes: + - | + Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the `new manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to many REST API endpoints to manage your enterprise's self-hosted runners. + - + heading: 'Audit log accessible via REST API' + notes: + - | + You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." + - + heading: 'Expiration dates for personal access tokens' + notes: + - | + You can now set an expiration date on new and existing personal access tokens. GitHub AE will send you an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving you a duplicate token with the same properties as the original. When using a token with the GitHub AE API, you'll see a new header, `GitHub-Authentication-Token-Expiration`, indicating the token's expiration date. You can use this in scripts, for example to log a warning message as the expiration date approaches. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" and "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#using-personal-access-tokens)." + - + heading: 'Export a list of people with access to a repository' + notes: + - | + Organization owners can now export a list of the people with access to a repository in CSV format. For more information, see "[Viewing people with access to your repository](/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository#exporting-a-list-of-people-with-access-to-your-repository)." + - + heading: 'Improved management of code review assignments' + notes: + - | + New settings to manage code review assignment code review assignment help distribute a team's pull request review across the team members so reviews aren't the responsibility of just one or two team members. + + - Child team members: Limit assignment to only direct members of the team. Previously, team review requests could be assigned to direct members of the team or members of child teams. + - Count existing requests: Continue with automatic assignment even if one or more members of the team are already requested. Previously, a team member who was already requested would be counted as one of the team's automatic review requests. + - Team review request: Keep a team assigned to review even if one or more members is newly assigned. + + For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." + - + heading: 'New themes' + notes: + - | + Two new themes are available for the GitHub AE web UI. + + - A dark high contrast theme, with greater contrast between foreground and background elements + - Light and dark colorblind, which swap colors such as red and green for orange and blue + + For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + - + heading: 'Markdown improvements' + notes: + - | + You can now use footnote syntax in any Markdown field to reference relevant information without disrupting the flow of your prose. Footnotes are displayed as superscript links. Click a footnote to jump to the reference, displayed in a new section at the bottom of the document. 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#footnotes)." + - | + You can now toggle between the source view and rendered Markdown view through the web UI by clicking the {% octicon "code" aria-label="The Code icon" %} button to "Display the source diff" at the top of any Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file. + - | + You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + - | + GitHub AE now automatically generates a table of contents for Wikis, based on headings. + changes: + - + heading: 'パフォーマンス' + notes: + - | + Page loads and jobs are now significantly faster for repositories with many Git refs. + - + heading: '管理' + notes: + - | + The user impersonation process is improved. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise owner. For more information, see "[Impersonating a user](/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)." + - + heading: 'GitHub Actions' + notes: + - | + To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." + - | + The audit log now includes additional events for GitHub Actions. GitHub AE now records audit log entries for the following events. + + - A self-hosted runner is registered or removed. + - A self-hosted runner is added to a runner group, or removed from a runner group. + - A runner group is created or removed. + - A workflow run is created or completed. + - A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner. + + For more information, see "[Security hardening for GitHub Actions](/actions/security-guides/security-hardening-for-github-actions)." + - + heading: 'GitHub Advanced Security' + notes: + - | + Code scanning will now map alerts identified in `on:push` workflows to show up on pull requests, when possible. The alerts shown on the pull request are those identified by comparing the existing analysis of the head of the branch to the analysis for the target branch that you are merging against. Note that if the pull request's merge commit is not used, alerts can be less accurate when compared to the approach that uses `on:pull_request` triggers. For more information, see "[About code scanning with CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." + + Some other CI/CD systems can exclusively be configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, code scanning will try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see "[Uploading a SARIF file to GitHub](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)." + - | + GitHub AE now detects secrets from additional providers. For more information, see "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets)." + - + heading: 'プルリクエスト' + notes: + - | + The timeline and Reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members because that team uses code review assignment. + + ![Screenshot of indicator for automatic assignment of code review](https://user-images.githubusercontent.com/2503052/134931920-409dea07-7a70-4557-b208-963357db7a0d.png) + - | + You can now filter pull request searches to only include pull requests you are directly requested to review by choosing **Awaiting review from you**. For more information, see "[Searching issues and pull requests](https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests)." + - | + If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list. + - | + When viewing a branch that has a corresponding open pull request, GitHub AE now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request. + - | + You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click in the toolbar. Note that this feature is currently only available in some browsers. + - | + A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [GitHub Changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/). + - + heading: 'リポジトリ' + notes: + - | + GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](​​https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." + - | + You can now add, delete, or view autolinks through the Repositories API's Autolinks endpoint. For more information, see "[Autolinked references and URLs](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)" and "[Repositories](/rest/reference/repos#autolinks)" in the REST API documentation. + - + heading: 'リリース' + notes: + - | + The tag selection component for GitHub releases is now a drop-down menu rather than a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)." + - + heading: 'Markdown' + notes: + - | + When dragging and dropping files such as images and videos into a Markdown editor, GitHub AE now uses the mouse pointer location instead of the cursor location when placing the file. diff --git a/translations/ja-JP/data/reusables/actions/allow-specific-actions-intro.md b/translations/ja-JP/data/reusables/actions/allow-specific-actions-intro.md index 5918d645aa..efaede7995 100644 --- a/translations/ja-JP/data/reusables/actions/allow-specific-actions-intro.md +++ b/translations/ja-JP/data/reusables/actions/allow-specific-actions-intro.md @@ -4,8 +4,8 @@ When you choose {% data reusables.actions.policy-label-for-select-actions-workflows %}, local actions{% if actions-workflow-policy %} and reusable workflows{% endif %} are allowed, and there are additional options for allowing other specific actions{% if actions-workflow-policy %} and reusable workflows{% endif %}: -- **Allow actions created by {% data variables.product.prodname_dotcom %}:** You can allow all actions created by {% data variables.product.prodname_dotcom %} to be used by workflows. Actions created by {% data variables.product.prodname_dotcom %} are located in the `actions` and `github` organizations. For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.{% ifversion fpt or ghes or ghae-issue-5094 or ghec %} -- **Allow Marketplace actions by verified creators:** {% ifversion ghes or ghae-issue-5094 %}This option is available if you have {% data variables.product.prodname_github_connect %} enabled and configured with {% data variables.product.prodname_actions %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)."{% endif %} You can allow all {% data variables.product.prodname_marketplace %} actions created by verified creators to be used by workflows. When GitHub has verified the creator of the action as a partner organization, the {% octicon "verified" aria-label="The verified badge" %} badge is displayed next to the action in {% data variables.product.prodname_marketplace %}.{% endif %} +- **Allow actions created by {% data variables.product.prodname_dotcom %}:** You can allow all actions created by {% data variables.product.prodname_dotcom %} to be used by workflows. Actions created by {% data variables.product.prodname_dotcom %} are located in the `actions` and `github` organizations. For more information, see the [`actions`](https://github.com/actions) and [`github`](https://github.com/github) organizations.{% ifversion fpt or ghes or ghae or ghec %} +- **Allow Marketplace actions by verified creators:** {% ifversion ghes or ghae %}This option is available if you have {% data variables.product.prodname_github_connect %} enabled and configured with {% data variables.product.prodname_actions %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)."{% endif %} You can allow all {% data variables.product.prodname_marketplace %} actions created by verified creators to be used by workflows. When GitHub has verified the creator of the action as a partner organization, the {% octicon "verified" aria-label="The verified badge" %} badge is displayed next to the action in {% data variables.product.prodname_marketplace %}.{% endif %} - **Allow specified actions{% if actions-workflow-policy %} and reusable workflows{% endif %}:** You can restrict workflows to use actions{% if actions-workflow-policy %} and reusable workflows{% endif %} in specific organizations and repositories. To restrict access to specific tags or commit SHAs of an action{% if actions-workflow-policy %} or reusable workflow{% endif %}, use the same syntax used in the workflow to select the action{% if actions-workflow-policy %} or reusable workflow{% endif %}. diff --git a/translations/ja-JP/data/reusables/actions/jobs/using-matrix-strategy.md b/translations/ja-JP/data/reusables/actions/jobs/using-matrix-strategy.md index baf995ad81..6b0d0c377c 100644 --- a/translations/ja-JP/data/reusables/actions/jobs/using-matrix-strategy.md +++ b/translations/ja-JP/data/reusables/actions/jobs/using-matrix-strategy.md @@ -1,4 +1,4 @@ -Use `jobs..strategy.matrix` to define a matrix of different job configurations. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a veriable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`: +Use `jobs..strategy.matrix` to define a matrix of different job configurations. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a variable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`: ```yaml jobs: diff --git a/translations/ja-JP/data/reusables/actions/message-parameters.md b/translations/ja-JP/data/reusables/actions/message-parameters.md index fd9358b1a0..8f6097244a 100644 --- a/translations/ja-JP/data/reusables/actions/message-parameters.md +++ b/translations/ja-JP/data/reusables/actions/message-parameters.md @@ -1 +1 @@ -| Parameter | Value | | :- | :- |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `title` | Custom title |{% endif %} | `file` | Filename | | `col` | Column number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `endColumn` | End column number |{% endif %} | `line` | Line number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `endLine` | End line number |{% endif %} +| Parameter | Value | | :- | :- |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `title` | Custom title |{% endif %} | `file` | Filename | | `col` | Column number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endColumn` | End column number |{% endif %} | `line` | Line number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endLine` | End line number |{% endif %} diff --git a/translations/ja-JP/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/ja-JP/data/reusables/apps/deprecating_auth_with_query_parameters.md index 94f8884d54..46de512b35 100644 --- a/translations/ja-JP/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/ja-JP/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,4 +1,3 @@ -{% ifversion fpt or ghes or ghae or ghec %} {% warning %} **非推奨の注意:** {% data variables.product.prodname_dotcom %}は、クエリパラメータを使ったAPIの認証を廃止します。 APIの認証は[HTTPの基本認証](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens)で行わなければなりません。{% ifversion fpt or ghec %}APIの認証にクエリパラメータを使用することは、2021年5月5日以降できなくなります。 {% endif %}予定された一時停止を含む詳しい情報については[ブログポスト](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/)を参照してください。 @@ -6,4 +5,3 @@ {% ifversion ghes or ghae %}クエリパラメータを使ったAPIの認証は、利用はできるものの、セキュリティ上の懸念からサポートされなくなりました。 その代わりに、インテグレータはアクセストークン、`client_id`もしくは`client_secret`をヘッダに移すことをおすすめします。 {% data variables.product.prodname_dotcom %}は、クエリパラメータによる認証の削除を、事前に通知します。 {% endif %} {% endwarning %} -{% endif %} diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md index 5cdc3ccfdb..1dfa9be3c4 100644 --- a/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md +++ b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md @@ -28,13 +28,13 @@ {%- ifversion ghes %} | `config_entry` | Contains activities related to configuration settings. These events are only visible in the site admin audit log. {%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | `dependabot_alerts` | 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` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. | `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access. {%- endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} | `dependabot_security_updates` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} を設定する](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)」を参照してください。 | `dependabot_security_updates_new_repos` | 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 or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} | `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 | `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization. {%- endif %} {%- ifversion fpt or ghec %} @@ -116,7 +116,7 @@ {%- ifversion fpt or ghec %} | `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization. {%- endif %} -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} | `repository_vulnerability_alert` | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies). {%- endif %} {%- ifversion fpt or ghec %} diff --git a/translations/ja-JP/data/reusables/cli/filter-issues-and-pull-requests-tip.md b/translations/ja-JP/data/reusables/cli/filter-issues-and-pull-requests-tip.md index 6956ea62a7..d862254f02 100644 --- a/translations/ja-JP/data/reusables/cli/filter-issues-and-pull-requests-tip.md +++ b/translations/ja-JP/data/reusables/cli/filter-issues-and-pull-requests-tip.md @@ -1,7 +1,5 @@ -{% ifversion fpt or ghes or ghae or ghec %} {% tip %} **ヒント**: {% data variables.product.prodname_cli %} を使用してIssueやPull Requestをフィルタすることもできます。 詳しい情報については、ドキュメントの「[`gh issue list`](https://cli.github.com/manual/gh_issue_list)」または「[`gh pr list`](https://cli.github.com/manual/gh_pr_list)」{% data variables.product.prodname_cli %} を参照してください。 {% endtip %} -{% endif %} diff --git a/translations/ja-JP/data/reusables/code-scanning/beta.md b/translations/ja-JP/data/reusables/code-scanning/beta.md index bb9cf0d33c..0b559e0466 100644 --- a/translations/ja-JP/data/reusables/code-scanning/beta.md +++ b/translations/ja-JP/data/reusables/code-scanning/beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-5752 %} +{% ifversion ghae %} diff --git a/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md index af85b53287..4e76a26911 100644 --- a/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ b/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md @@ -1 +1 @@ -1. {% data variables.product.prodname_vscode %}の左サイドバーで、 Remote Explorerのアイコンをクリックしてください。 ![{% data variables.product.prodname_vscode %}のRemote Explorerアイコン](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) +1. {% data variables.product.prodname_vscode_shortname %}の左サイドバーで、 Remote Explorerのアイコンをクリックしてください。 ![{% data variables.product.prodname_vscode %}のRemote Explorerアイコン](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) diff --git a/translations/ja-JP/data/reusables/codespaces/committing-link-to-procedure.md b/translations/ja-JP/data/reusables/codespaces/committing-link-to-procedure.md index 0a9cdc062f..34f98be3b2 100644 --- a/translations/ja-JP/data/reusables/codespaces/committing-link-to-procedure.md +++ b/translations/ja-JP/data/reusables/codespaces/committing-link-to-procedure.md @@ -1,3 +1,3 @@ -新しいコードであれ、設定の変更であれ、codespaceに変更を加えたら、その変更をコミットしたくなるでしょう。 リポジトリに変更をコミットすれば、このリポジトリからcodespaceを作成する他の人が、同じ設定になることを保証できます。 これはまた、{% data variables.product.prodname_vscode %}機能拡張の追加など、あなたが行うすべてのカスタマイズが、すべてのユーザに対して現れるようになるということでもあります。 +新しいコードであれ、設定の変更であれ、codespaceに変更を加えたら、その変更をコミットしたくなるでしょう。 リポジトリに変更をコミットすれば、このリポジトリからcodespaceを作成する他の人が、同じ設定になることを保証できます。 これはまた、{% data variables.product.prodname_vscode_shortname %}機能拡張の追加など、あなたが行うすべてのカスタマイズが、すべてのユーザに対して現れるようになるということでもあります。 詳しい情報については「[codespaceでのソースコントロールの利用](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/ja-JP/data/reusables/codespaces/connect-to-codespace-from-vscode.md index c7761ac154..562be8d99e 100644 --- a/translations/ja-JP/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ b/translations/ja-JP/data/reusables/codespaces/connect-to-codespace-from-vscode.md @@ -1 +1 @@ -{% data variables.product.prodname_vscode %}から直接codespaceに接続できます。 詳しい情報については「[{% data variables.product.prodname_vscode %}でのCodespacesの利用](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)」を参照してください。 +{% data variables.product.prodname_vscode_shortname %}から直接codespaceに接続できます。 詳しい情報については「[{% data variables.product.prodname_vscode_shortname %}でのCodespacesの利用](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md index f6aff8b0f3..c6b3a9fde2 100644 --- a/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md +++ b/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md @@ -1,8 +1,8 @@ -After you connect your account on {% data variables.product.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). +After you connect your account on {% data variables.product.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). {% note %} -**Note**: Currently, {% data variables.product.prodname_vscode %} doesn't allow you to choose a dev container configuration when you create a codespace. If you want to choose a specific dev container configuration, use the {% data variables.product.prodname_dotcom %} web interface to create your codespace. For more information, click the **Web browser** tab at the top of this page. +**Note**: Currently, {% data variables.product.prodname_vscode_shortname %} doesn't allow you to choose a dev container configuration when you create a codespace. If you want to choose a specific dev container configuration, use the {% data variables.product.prodname_dotcom %} web interface to create your codespace. For more information, click the **Web browser** tab at the top of this page. {% endnote %} diff --git a/translations/ja-JP/data/reusables/codespaces/deleting-a-codespace-in-vscode.md b/translations/ja-JP/data/reusables/codespaces/deleting-a-codespace-in-vscode.md index 9d49304dec..11feb3a8f3 100644 --- a/translations/ja-JP/data/reusables/codespaces/deleting-a-codespace-in-vscode.md +++ b/translations/ja-JP/data/reusables/codespaces/deleting-a-codespace-in-vscode.md @@ -1,4 +1,4 @@ -You can delete codespaces from within {% data variables.product.prodname_vscode %} when you are not currently working in a codespace. +You can delete codespaces from within {% data variables.product.prodname_vscode_shortname %} when you are not currently working in a codespace. {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 1. Under "GITHUB CODESPACES", right-click the codespace you want to delete. diff --git a/translations/ja-JP/data/reusables/codespaces/more-info-devcontainer.md b/translations/ja-JP/data/reusables/codespaces/more-info-devcontainer.md index 430a9f1156..f0fd5c863b 100644 --- a/translations/ja-JP/data/reusables/codespaces/more-info-devcontainer.md +++ b/translations/ja-JP/data/reusables/codespaces/more-info-devcontainer.md @@ -1 +1 @@ -For information about the settings and properties that you can set in a `devcontainer.json` file, see "[devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json)" in the {% data variables.product.prodname_vscode %} documentation. \ No newline at end of file +For information about the settings and properties that you can set in a `devcontainer.json` file, see "[devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json)" in the {% data variables.product.prodname_vscode_shortname %} documentation. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/use-visual-studio-features.md b/translations/ja-JP/data/reusables/codespaces/use-visual-studio-features.md index 20b4c76baf..1a76110c72 100644 --- a/translations/ja-JP/data/reusables/codespaces/use-visual-studio-features.md +++ b/translations/ja-JP/data/reusables/codespaces/use-visual-studio-features.md @@ -1 +1 @@ -{% data variables.product.prodname_vscode %}でcodespace内で開発をする間に、コードを編集し、デバッグし、Gtiのコマンドを使うことができます。 詳しい情報については[{% data variables.product.prodname_vscode %}のドキュメンテーション](https://code.visualstudio.com/docs)を参照してください。 +{% data variables.product.prodname_vscode_shortname %}でcodespace内で開発をする間に、コードを編集し、デバッグし、Gtiのコマンドを使うことができます。 詳しい情報については[{% data variables.product.prodname_vscode_shortname %}のドキュメンテーション](https://code.visualstudio.com/docs)を参照してください。 diff --git a/translations/ja-JP/data/reusables/codespaces/vscode-settings-order.md b/translations/ja-JP/data/reusables/codespaces/vscode-settings-order.md index bec24daf60..b33eb8c62e 100644 --- a/translations/ja-JP/data/reusables/codespaces/vscode-settings-order.md +++ b/translations/ja-JP/data/reusables/codespaces/vscode-settings-order.md @@ -1 +1 @@ -{% data variables.product.prodname_vscode %}のエディタ設定を行う際には、_Workspace_、_Remote [Codespaces]_、_User_という3つのスコープが利用できます。 複数のスコープ内で定義された設定については、_Workspace_の設定が優先され、次が_Remote [Codespaces]_、そして_User_となります。 +{% data variables.product.prodname_vscode_shortname %}のエディタ設定を行う際には、_Workspace_、_Remote [Codespaces]_、_User_という3つのスコープが利用できます。 複数のスコープ内で定義された設定については、_Workspace_の設定が優先され、次が_Remote [Codespaces]_、そして_User_となります。 diff --git a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md index 4cfd65386a..c2bfc45615 100644 --- a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md +++ b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-4864 %} +{% ifversion ghae %} {% note %} **Note:** {% data variables.product.prodname_dependabot_alerts %} is currently in beta and is subject to change. diff --git a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md index d5ae9b8415..367cbb25f8 100644 --- a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md +++ b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md @@ -1,3 +1,3 @@ -{% ifversion ghes or ghae-issue-4864 %} -Enterprise owners can configure {% ifversion ghes %}the dependency graph and {% endif %}{% data variables.product.prodname_dependabot_alerts %} for an enterprise. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +{% ifversion ghes or ghae %} +Enterprise owners can configure {% ifversion ghes %}the dependency graph and {% endif %}{% data variables.product.prodname_dependabot_alerts %} for an enterprise. 詳しい情報については{% ifversion ghes %}「[Enterpriseでの依存関係グラフの有効化](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)」及び{% endif %}「[Enterpriseでの{% data variables.product.prodname_dependabot %}の有効化](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/data/reusables/gated-features/dependency-review.md b/translations/ja-JP/data/reusables/gated-features/dependency-review.md index bd88b5b182..779649a9d8 100644 --- a/translations/ja-JP/data/reusables/gated-features/dependency-review.md +++ b/translations/ja-JP/data/reusables/gated-features/dependency-review.md @@ -2,12 +2,12 @@ Dependency review is enabled on public repositories. Dependency review is also available in private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. {%- elsif ghec %} -Dependency review is included in {% data variables.product.product_name %} for public repositories. To use dependency review in private repositories owned by organizations, you must have a license for {% data variables.product.prodname_GH_advanced_security %}. +依存関係レビューは、パブリックリポジトリに対して{% data variables.product.product_name %}に含まれています。 To use dependency review in private repositories owned by organizations, you must have a license for {% data variables.product.prodname_GH_advanced_security %}. {%- elsif ghes > 3.1 %} Dependency review is available for organization-owned repositories in {% data variables.product.product_name %}. This feature requires a license for {% data variables.product.prodname_GH_advanced_security %}. -{%- elsif ghae-issue-4864 %} +{%- elsif ghae %} Dependency review is available for organization-owned repositories in {% data variables.product.product_name %}. This is a {% data variables.product.prodname_GH_advanced_security %} feature (free during the beta release). -{%- endif %} {% data reusables.advanced-security.more-info-ghas %} \ No newline at end of file +{%- endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md index 3f6d5df5ec..5517dbd6ce 100644 --- a/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md +++ b/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} Watchしているか、セキュリティアラートをサブスクライブしているリポジトリ上で {% data variables.product.prodname_dependabot_alerts %}に関する通知の配信方法と頻度を選択できます。 {% endif %} diff --git a/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-options.md b/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-options.md index 78fc92042a..999656560f 100644 --- a/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-options.md +++ b/translations/ja-JP/data/reusables/notifications/vulnerable-dependency-notification-options.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} -{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes > 3.1 or ghae %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %} - メールについては、{% data variables.product.prodname_dependabot %}がリポジトリで有効化された場合、新しいマニフェストファイルがリポジトリにコミットされた場合、重要度が重大もしくは高の新しい脆弱性が見つかった場合に送信されます（**Email each time a vulnerability is found（脆弱性が見つかるたびにメールする）**オプション）。 - ユーザインターフェースについては、脆弱な依存関係があった場合に、リポジトリのファイルとコードビューに警告が表示されます（**UI alerts（UIアラート）**オプション）。 diff --git a/translations/ja-JP/data/reusables/organizations/security-overview-feature-specific-page.md b/translations/ja-JP/data/reusables/organizations/security-overview-feature-specific-page.md new file mode 100644 index 0000000000..13f951ee2f --- /dev/null +++ b/translations/ja-JP/data/reusables/organizations/security-overview-feature-specific-page.md @@ -0,0 +1 @@ +1. あるいは、左のサイドバーを使ってセキュリティ機能ごとに情報をフィルタリングすることもできます。 On each page, you can use filters that are specific to that feature to fine-tune your search. diff --git a/translations/ja-JP/data/reusables/organizations/team_maintainers_can.md b/translations/ja-JP/data/reusables/organizations/team_maintainers_can.md index ffd13da287..19aae1ce72 100644 --- a/translations/ja-JP/data/reusables/organizations/team_maintainers_can.md +++ b/translations/ja-JP/data/reusables/organizations/team_maintainers_can.md @@ -10,6 +10,6 @@ - [OrganizationのメンバーのTeamへの追加](/articles/adding-organization-members-to-a-team) - [OrganizationメンバーのTeamからの削除](/articles/removing-organization-members-from-a-team) - [既存のTeamメンバーのチームメンテナへの昇格](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member) -- リポジトリへのTeamのアクセスの削除{% ifversion fpt or ghes or ghae or ghec %} -- [Manage code review settings for the team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% endif %}{% ifversion fpt or ghec %} +- リポジトリへのTeamのアクセス権の削除 +- [Manage code review settings for the team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% ifversion fpt or ghec %} - [プルリクエストのスケジュールされたリマインダーの管理](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/ja-JP/data/reusables/pull_requests/close-issues-using-keywords.md b/translations/ja-JP/data/reusables/pull_requests/close-issues-using-keywords.md index e0870429bb..1670aeb057 100644 --- a/translations/ja-JP/data/reusables/pull_requests/close-issues-using-keywords.md +++ b/translations/ja-JP/data/reusables/pull_requests/close-issues-using-keywords.md @@ -1 +1 @@ -プルリクエストをIssueにリンクして、{% ifversion fpt or ghes or ghae or ghec %}修復が進んでいることを示すことや、{% endif %}誰かがプルリクエストをマージしたときにIssueを自動的にクローズすることができます。 詳しい情報については「[プルリクエストのIssueへのリンク](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)」を参照してください。 +You can link a pull request to an issue to show that a fix is in progress and to automatically close the issue when someone merges the pull request. 詳しい情報については「[プルリクエストのIssueへのリンク](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/repositories/copy-clone-url.md b/translations/ja-JP/data/reusables/repositories/copy-clone-url.md index 93442e4e82..48aebd76b7 100644 --- a/translations/ja-JP/data/reusables/repositories/copy-clone-url.md +++ b/translations/ja-JP/data/reusables/repositories/copy-clone-url.md @@ -1,6 +1,6 @@ 1. ファイルのリストの上にある{% octicon "download" aria-label="The download icon" %} **Code（コード）**をクリックしてください。 !["Code"ボタン](/assets/images/help/repository/code-button.png) -1. HTTPSを使ってリポジトリをクローンするには、"Clone with HTTPS（HTTPSでクローン）"の下で、 -{% octicon "clippy" aria-label="The clipboard icon" %}をクリックしてください。 To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **Use SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. To clone a repository using {% data variables.product.prodname_cli %}, click **Use {% data variables.product.prodname_cli %}**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. - ![リポジトリをクローンするURLをコピーするクリップボードアイコン](/assets/images/help/repository/https-url-clone.png) - {% ifversion fpt or ghes or ghae or ghec %} - ![GitHub CLIでリポジトリをクローンするためのURLをコピーするためのクリップボードアイコン](/assets/images/help/repository/https-url-clone-cli.png){% endif %} +1. Copy the URL for the repository. + + - To clone the repository using HTTPS, under "HTTPS", click {% octicon "clippy" aria-label="The clipboard icon" %}. + - Organization の SSH 認証局から発行された証明書を含む SSH キーを使用してリポジトリのクローンを作成するには、[**SSH**]、{% octicon "clippy" aria-label="The clipboard icon" %} の順にクリックします。 + - To clone a repository using {% data variables.product.prodname_cli %}, click **{% data variables.product.prodname_cli %}**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. ![GitHub CLIでリポジトリをクローンするためのURLをコピーするためのクリップボードアイコン](/assets/images/help/repository/https-url-clone-cli.png) diff --git a/translations/ja-JP/data/reusables/repositories/default-issue-templates.md b/translations/ja-JP/data/reusables/repositories/default-issue-templates.md index 2027225119..61d5af8ce1 100644 --- a/translations/ja-JP/data/reusables/repositories/default-issue-templates.md +++ b/translations/ja-JP/data/reusables/repositories/default-issue-templates.md @@ -1,2 +1 @@ -You can create default issue templates{% ifversion fpt or ghes or ghae or ghec %} and a default configuration file for issue templates{% endif %} for your organization{% ifversion fpt or ghes or ghae or ghec %} or personal account{% endif %}. 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。 - +You can create default issue templates and a default configuration file for issue templates for your organization or personal account. 詳しい情報については「[デフォルトのコミュニティ健全性ファイルを作成する](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/repositories/dependency-review.md b/translations/ja-JP/data/reusables/repositories/dependency-review.md index 3d3d7623ef..536aa89b11 100644 --- a/translations/ja-JP/data/reusables/repositories/dependency-review.md +++ b/translations/ja-JP/data/reusables/repositories/dependency-review.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} 加えて、 {% data variables.product.prodname_dotcom %}は、リポジトリのデフォルトブランチに対して作成されたPull Request中で追加、更新、削除された依存関係のレビューを行うことができ、プロジェクトに脆弱性をもたらすような変更にフラグを立てることができます。 これによって、脆弱な依存関係がコードベースに達したあとではなく、達する前に特定して対処できるようになります。 詳しい情報については「[Pull Request中の依存関係の変更のレビュー](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md b/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md index ceec95422e..93750c5470 100644 --- a/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md +++ b/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md @@ -1,4 +1,4 @@ -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} Enterprise owners must enable {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} diff --git a/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index 3a599d66a2..e29ea372d6 100644 --- a/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/ja-JP/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% ifversion fpt or ghes or ghae or ghec %}直線状のコミット履歴を必要とする保護されたブランチのルールがリポジトリ中にあるなら、squashマージ、リベースマージ、あるいはその両方を許可しなければなりません。 詳しい情報については、「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)」を参照してください。{% endif %} +If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. 詳しい情報については[保護されたブランチについて](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)を参照してください。 diff --git a/translations/ja-JP/data/reusables/repositories/start-line-comment.md b/translations/ja-JP/data/reusables/repositories/start-line-comment.md index 09b217fd40..77114a2099 100644 --- a/translations/ja-JP/data/reusables/repositories/start-line-comment.md +++ b/translations/ja-JP/data/reusables/repositories/start-line-comment.md @@ -1 +1 @@ -1. コメントを追加したいコードの行の上にカーソルを移動し、青いコメントアイコンをクリックしてください。{% ifversion fpt or ghes or ghae or ghec %}複数行にコメントを追加するには、クリックしてからドラッグで行の範囲を選択し、続いて青いコメントアイコンをクリックしてください。{% endif %} ![青いコメントアイコン](/assets/images/help/commits/hover-comment-icon.gif) +1. Hover over the line of code where you'd like to add a comment, and click the blue comment icon. To add a comment on multiple lines, click and drag to select the range of lines, then click the blue comment icon. ![青いコメントアイコン](/assets/images/help/commits/hover-comment-icon.gif) diff --git a/translations/ja-JP/data/reusables/repositories/suggest-changes.md b/translations/ja-JP/data/reusables/repositories/suggest-changes.md index 22c1a6c0fe..1071b1cd99 100644 --- a/translations/ja-JP/data/reusables/repositories/suggest-changes.md +++ b/translations/ja-JP/data/reusables/repositories/suggest-changes.md @@ -1 +1 @@ -1. あるいは、特定の変更を行{% ifversion fpt or ghes or ghae or ghec %}あるいは複数行{% endif %}に対して示唆するには、{% octicon "diff" aria-label="The diff symbol" %}をクリックし、示唆するブロック内のテキストを編集してください。 ![サジェッションブロック](/assets/images/help/pull_requests/suggestion-block.png) +1. Optionally, to suggest a specific change to the line or lines, click {% octicon "diff" aria-label="The diff symbol" %}, then edit the text within the suggestion block. ![サジェッションブロック](/assets/images/help/pull_requests/suggestion-block.png) diff --git a/translations/ja-JP/data/reusables/secret-scanning/beta.md b/translations/ja-JP/data/reusables/secret-scanning/beta.md index 4dd22083b1..0bc205dfe0 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/beta.md +++ b/translations/ja-JP/data/reusables/secret-scanning/beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-5752 %} +{% ifversion ghae %} 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 fe024055e3..8895e000e5 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 @@ -13,9 +13,9 @@ Adobe | Adobe JSON Web Token | adobe_jwt{% endif %} Alibaba Cloud | Alibaba Clou Amazon | Amazon OAuth Client ID | amazon_oauth_client_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Amazon | Amazon OAuth Client Secret | amazon_oauth_client_secret{% endif %} Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} Atlassian | Atlassian API Token | atlassian_api_token Atlassian | Atlassian JSON Web Token | atlassian_jwt @@ -27,7 +27,7 @@ Azure | Azure Active Directory Application Secret | azure_active_directory_appli Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key{% endif %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token Azure | Azure SAS Token | azure_sas_token Azure | Azure Service Management Certificate | azure_management_certificate {%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %} Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} Azure | Azure Storage Account Key | azure_storage_account_key -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Beamer | Beamer API Key | beamer_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key{% endif %} @@ -35,7 +35,7 @@ Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_k Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key{% endif %} Clojars | Clojars Deploy Token | clojars_deploy_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Contentful | Contentful Personal Access Token | contentful_personal_access_token{% endif %} Databricks | Databricks Access Token | databricks_access_token {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} DigitalOcean | DigitalOcean Personal Access Token | digitalocean_personal_access_token DigitalOcean | DigitalOcean OAuth Token | digitalocean_oauth_token DigitalOcean | DigitalOcean Refresh Token | digitalocean_refresh_token DigitalOcean | DigitalOcean System Token | digitalocean_system_token{% endif %} Discord | Discord Bot Token | discord_bot_token Doppler | Doppler Personal Token | doppler_personal_token Doppler | Doppler Service Token | doppler_service_token Doppler | Doppler CLI Token | doppler_cli_token Doppler | Doppler SCIM Token | doppler_scim_token @@ -55,7 +55,7 @@ Fastly | Fastly API Token | fastly_api_token{% endif %} Finicity | Finicity App Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key{% endif %} Frame.io | Frame.io JSON Web Token | frameio_jwt Frame.io| Frame.io Developer Token | frameio_developer_token -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} FullStory | FullStory API Key | fullstory_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} GitHub | GitHub個人アクセストークン | github_personal_access_token{% endif %} @@ -67,13 +67,13 @@ GitHub | GitHubリフレッシュトークン | github_refresh_token{% endif %} GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %} GitHub | GitHub SSH Private Key | github_ssh_private_key {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} GitLab | GitLab Access Token | gitlab_access_token{% endif %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} Google | Google API Key | google_api_key Google | Google Cloud Private Key ID | google_cloud_private_key_id -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Google | Google OAuth Access Token | google_oauth_access_token{% endif %} @@ -93,9 +93,9 @@ Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %} Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} JD Cloud | JD Cloud Access Key | jd_cloud_access_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Linear | Linear API Key | linear_api_key{% endif %} @@ -115,13 +115,13 @@ Meta | Facebook Access Token | facebook_access_token{% endif %} Midtrans | Midtrans Production Server Key | midtrans_production_server_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Midtrans | Midtrans Sandbox Server Key | midtrans_sandbox_server_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic License Key | new_relic_license_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Notion | Notion Integration Token | notion_integration_token{% endif %} @@ -135,15 +135,15 @@ Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} OpenAI | OpenAI API Key | openai_api_key{% endif %} Palantir | Palantir JSON Web Token | palantir_jwt -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Plivo | Plivo Auth ID | plivo_auth_id{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Plivo | Plivo Auth Token | plivo_auth_token{% endif %} Postman | Postman API Key | postman_api_key Proctorio | Proctorio Consumer Key | proctorio_consumer_key Proctorio | Proctorio Linkage Key | proctorio_linkage_key Proctorio | Proctorio Registration Key | proctorio_registration_key Proctorio | Proctorio Secret Key | proctorio_secret_key Pulumi | Pulumi Access Token | pulumi_access_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} PyPI | PyPI API Token | pypi_api_token{% endif %} @@ -153,9 +153,9 @@ RubyGems | RubyGems API Key | rubygems_api_key{% endif %} Samsara | Samsara API 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 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Shippo | Shippo Live API Token | shippo_live_api_token{% endif %} diff --git a/translations/ja-JP/data/reusables/security-center/permissions.md b/translations/ja-JP/data/reusables/security-center/permissions.md new file mode 100644 index 0000000000..2a6ce48a28 --- /dev/null +++ b/translations/ja-JP/data/reusables/security-center/permissions.md @@ -0,0 +1 @@ +Organization owners and security managers can access the security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} and view their organization's repositories via the enterprise-level security overview. Enterprise owners can use the enterprise-level security overview to view all repositories in their enterprise's organizations{% endif %}. Teamのメンバーは、Teamが管理者権限を持つリポジトリのセキュリティの概要を見ることができます。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/security/compliance-report-list.md b/translations/ja-JP/data/reusables/security/compliance-report-list.md index 731afc0ca0..cb121885f2 100644 --- a/translations/ja-JP/data/reusables/security/compliance-report-list.md +++ b/translations/ja-JP/data/reusables/security/compliance-report-list.md @@ -1,4 +1,5 @@ - SOC 1, Type 2 - SOC 2, Type 2 - Cloud Security Alliance CAIQ self-assessment (CSA CAIQ) +- ISO/IEC 27001:2013 certification - {% data variables.product.prodname_dotcom_the_website %} Services Continuity and Incident Management Plan diff --git a/translations/ja-JP/data/reusables/ssh/key-type-support.md b/translations/ja-JP/data/reusables/ssh/key-type-support.md index 57b5241f88..05e444cc2b 100644 --- a/translations/ja-JP/data/reusables/ssh/key-type-support.md +++ b/translations/ja-JP/data/reusables/ssh/key-type-support.md @@ -1,3 +1,4 @@ +{% ifversion fpt or ghec %} {% note %} **Note:** {% data variables.product.company_short %} improved security by dropping older, insecure key types on March 15, 2022. @@ -7,3 +8,4 @@ As of that date, DSA keys (`ssh-dss`) are no longer supported. You cannot add ne RSA keys (`ssh-rsa`) with a `valid_after` before November 2, 2021 may continue to use any signature algorithm. RSA keys generated after that date must use a SHA-2 signature algorithm. Some older clients may need to be upgraded in order to use SHA-2 signatures. {% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/user-settings/removes-personal-access-tokens.md b/translations/ja-JP/data/reusables/user-settings/removes-personal-access-tokens.md index b11c0bbd8b..c6184d182d 100644 --- a/translations/ja-JP/data/reusables/user-settings/removes-personal-access-tokens.md +++ b/translations/ja-JP/data/reusables/user-settings/removes-personal-access-tokens.md @@ -1 +1 @@ -As a security precaution, {% data variables.product.company_short %} automatically removes personal access tokens that haven't been used in a year.{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} To provide additional security, we highly recommend adding an expiration to your personal access tokens.{% endif %} +As a security precaution, {% data variables.product.company_short %} automatically removes personal access tokens that haven't been used in a year.{% ifversion fpt or ghes > 3.1 or ghae or ghec %} To provide additional security, we highly recommend adding an expiration to your personal access tokens.{% endif %} diff --git a/translations/ja-JP/data/reusables/webhooks/check_run_properties.md b/translations/ja-JP/data/reusables/webhooks/check_run_properties.md index 72f93c0465..1df12c2d8c 100644 --- a/translations/ja-JP/data/reusables/webhooks/check_run_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/check_run_properties.md @@ -1,12 +1,12 @@ -| キー | 種類 | 説明 | -| --------------------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション。 次のいずれかになります。
  • `created` - 新しいチェックランが作成されました。
  • `completed` - チェックランの`status`は`completed`です。
  • `rerequested` - 誰かがPull RequestのUIからチェックランの再実行をリクエストしています。 GitHubのUIに関する詳細については「[ステータスチェックについて](/articles/about-status-checks#checks)」を参照してください。 `rerequested`アクションを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。 誰かがチェックの再実行をリクエストした{% data variables.product.prodname_github_app %}だけが`rerequested`ペイロードを受け取ります。
  • `requested_action` - 誰かが、アプリケーションが提供するアクションの実行をリクエストしました。 誰かがアクションの実行をリクエストした{% data variables.product.prodname_github_app %}だけが`requested_action`ペイロードを受け取ります。 チェックランとリクエストされたアクションについて学ぶには、「[チェックランとリクエストされたアクション](/rest/reference/checks#check-runs-and-requested-actions)」を参照してください。
| -| `check_run` | `オブジェクト` | [check_run](/rest/reference/checks#get-a-check-run)。 | -| `check_run[status]` | `string` | チェックランの現在のステータス。 `queued`、`in_progress`、`completed`のいずれか。 | -| `check_run[conclusion]` | `string` | 完了したチェックランの結果。 `success`、`failure`、`neutral`、`cancelled`、`timed_out`、{% ifversion fpt or ghes or ghae or ghec %}`action_required`、`stale`{% else %}`action_required`{% endif %}のいずれか。 チェックランが`completed`になるまで、この値は`null`になる。 | -| `check_run[name]` | `string` | チェックランの名前。 | -| `check_run[check_suite][id]` | `integer` | このチェックランが一部になっているチェックスイートのid。 | -| `check_run[check_suite][pull_requests]` | `array` | このチェックスイートにマッチするPull Requestの配列。 A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
| -| `check_run[check_suite][deployment]` | `オブジェクト` | リポジトリ環境へのデプロイメント。 これは、チェックランが環境を参照する{% data variables.product.prodname_actions %}ワークフロージョブによって作成された場合にのみ展開される。 | -| `requested_action` | `オブジェクト` | ユーザによってリクエストされたアクション。 | -| `requested_action[identifier]` | `string` | ユーザによってリクエストされたアクションのインテグレーター参照。 | +| キー | 種類 | 説明 | +| --------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `action` | `string` | 実行されたアクション。 次のいずれかになります。
  • `created` - 新しいチェックランが作成されました。
  • `completed` - チェックランの`status`は`completed`です。
  • `rerequested` - 誰かがPull RequestのUIからチェックランの再実行をリクエストしています。 GitHubのUIに関する詳細については「[ステータスチェックについて](/articles/about-status-checks#checks)」を参照してください。 `rerequested`アクションを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。 誰かがチェックの再実行をリクエストした{% data variables.product.prodname_github_app %}だけが`rerequested`ペイロードを受け取ります。
  • `requested_action` - 誰かが、アプリケーションが提供するアクションの実行をリクエストしました。 誰かがアクションの実行をリクエストした{% data variables.product.prodname_github_app %}だけが`requested_action`ペイロードを受け取ります。 チェックランとリクエストされたアクションについて学ぶには、「[チェックランとリクエストされたアクション](/rest/reference/checks#check-runs-and-requested-actions)」を参照してください。
| +| `check_run` | `オブジェクト` | [check_run](/rest/reference/checks#get-a-check-run)。 | +| `check_run[status]` | `string` | チェックランの現在のステータス。 `queued`、`in_progress`、`completed`のいずれか。 | +| `check_run[conclusion]` | `string` | 完了したチェックランの結果。 Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, `action_required` or `stale`. チェックランが`completed`になるまで、この値は`null`になる。 | +| `check_run[name]` | `string` | チェックランの名前。 | +| `check_run[check_suite][id]` | `integer` | このチェックランが一部になっているチェックスイートのid。 | +| `check_run[check_suite][pull_requests]` | `array` | このチェックスイートにマッチするPull Requestの配列。 A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
| +| `check_run[check_suite][deployment]` | `オブジェクト` | リポジトリ環境へのデプロイメント。 これは、チェックランが環境を参照する{% data variables.product.prodname_actions %}ワークフロージョブによって作成された場合にのみ展開される。 | +| `requested_action` | `オブジェクト` | ユーザによってリクエストされたアクション。 | +| `requested_action[identifier]` | `string` | ユーザによってリクエストされたアクションのインテグレーター参照。 | diff --git a/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md b/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md index 217896a2f7..9249552208 100644 --- a/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/check_suite_properties.md @@ -1,10 +1,10 @@ -| キー | 種類 | 説明 | -| ---------------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `string` | 実行されたアクション。 以下のいずれかになる。
  • `completed` - チェックスイート内のすべてのチェックランが完了しました。
  • `requested` - アプリケーションのリポジトリに新しいコードがプッシュされたときに発生します。 `requested`アクションイベントを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。
  • `rerequested` - 誰かがチェックスイート全体の再実行をPull Request UIからリクエストしたときに発生します。 `rerequested`アクションイベントを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。 GitHubのUIに関する詳細については「[ステータスチェックについて](/articles/about-status-checks#checks)」を参照してください。
| -| `check_suite` | `オブジェクト` | [check_suite](/rest/reference/checks#suites)。 | -| `check_suite[head_branch]` | `string` | 変更があるヘッドブランチ名。 | -| `check_suite[head_sha]` | `string` | このチェックスイートに対する最新のコミットのSHA。 | -| `check_suite[status]` | `string` | チェックスイートの一部であるすべてのチェックランのサマリステータス。 `requested`、`in_progress`、`completed`のいずれか。 | -| `check_suite[conclusion]` | `string` | チェックスイートの一部であるすべてのチェックランのサマリの結論。 `success`、`failure`、`neutral`、`cancelled`、`timed_out`、{% ifversion fpt or ghes or ghae or ghec %}`action_required`、`stale`{% else %}`action_required`{% endif %}のいずれか。 チェックランが`completed`になるまで、この値は`null`になる。 | -| `check_suite[url]` | `string` | チェックスイートAPIのリソースを指すURL。 | -| `check_suite[pull_requests]` | `array` | このチェックスイートにマッチするPull Requestの配列。 A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
| +| キー | 種類 | 説明 | +| ---------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `string` | 実行されたアクション。 以下のいずれかになる。
  • `completed` - チェックスイート内のすべてのチェックランが完了しました。
  • `requested` - アプリケーションのリポジトリに新しいコードがプッシュされたときに発生します。 `requested`アクションイベントを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。
  • `rerequested` - 誰かがチェックスイート全体の再実行をPull Request UIからリクエストしたときに発生します。 `rerequested`アクションイベントを受信した場合、[新しいチェックランを作成](/rest/reference/checks#create-a-check-run)しなければなりません。 GitHubのUIに関する詳細については「[ステータスチェックについて](/articles/about-status-checks#checks)」を参照してください。
| +| `check_suite` | `オブジェクト` | [check_suite](/rest/reference/checks#suites)。 | +| `check_suite[head_branch]` | `string` | 変更があるヘッドブランチ名。 | +| `check_suite[head_sha]` | `string` | このチェックスイートに対する最新のコミットのSHA。 | +| `check_suite[status]` | `string` | チェックスイートの一部であるすべてのチェックランのサマリステータス。 `requested`、`in_progress`、`completed`のいずれか。 | +| `check_suite[conclusion]` | `string` | チェックスイートの一部であるすべてのチェックランのサマリの結論。 Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, `action_required` or `stale`. チェックランが`completed`になるまで、この値は`null`になる。 | +| `check_suite[url]` | `string` | チェックスイートAPIのリソースを指すURL。 | +| `check_suite[pull_requests]` | `array` | このチェックスイートにマッチするPull Requestの配列。 A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
| diff --git a/translations/ja-JP/data/reusables/webhooks/installation_properties.md b/translations/ja-JP/data/reusables/webhooks/installation_properties.md index 19c52775c7..4dfcea4ed4 100644 --- a/translations/ja-JP/data/reusables/webhooks/installation_properties.md +++ b/translations/ja-JP/data/reusables/webhooks/installation_properties.md @@ -1,4 +1,4 @@ | キー | 種類 | 説明 | | -------------- | -------- | ------------------------------------------------- | -| `action` | `string` | 実行されたアクション. 次のいずれかになります。
  • `created` - 誰かが{% data variables.product.prodname_github_app %}をインストールする。
  • `deleted` - だれかが{% data variables.product.prodname_github_app %}をアンインストールする。
    • {% ifversion fpt or ghes or ghae or ghec %}
  • `suspend` - だれかが{% data variables.product.prodname_github_app %}のインストールをサスペンドする。
  • `unsuspend` - だれかが{% data variables.product.prodname_github_app %}のインストールをサスペンド解除する。
    • {% endif %}
  • `new_permissions_accepted` - 誰かが{% data variables.product.prodname_github_app %}インストールに対する新しい権限を受け入れる。 {% data variables.product.prodname_github_app %}のオーナーが新しい権限をリクエストすると、{% data variables.product.prodname_github_app %}をインストールした人は新しい権限リクエストを受け入れなければならない。
| +| `action` | `string` | 実行されたアクション. 次のいずれかになります。
  • `created` - 誰かが{% data variables.product.prodname_github_app %}をインストールする。
  • `deleted` - だれかが{% data variables.product.prodname_github_app %}をアンインストールする。
  • `suspend` - だれかが{% data variables.product.prodname_github_app %}のインストールをサスペンドする。
  • `unsuspend` - だれかが{% data variables.product.prodname_github_app %}のインストールをサスペンド解除する。
  • `new_permissions_accepted` - 誰かが{% data variables.product.prodname_github_app %}インストールに対する新しい権限を受け入れる。 {% data variables.product.prodname_github_app %}のオーナーが新しい権限をリクエストすると、{% data variables.product.prodname_github_app %}をインストールした人は新しい権限リクエストを受け入れなければならない。
| | `repositories` | `array` | インストールがアクセスできるリポジトリオブジェクトの配列。 | diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml index 79418696c2..ea947a6f02 100644 --- a/translations/ja-JP/data/variables/product.yml +++ b/translations/ja-JP/data/variables/product.yml @@ -140,10 +140,14 @@ prodname_advisory_database: 'GitHub Advisory Database' prodname_codeql_workflow: 'CodeQL分析ワークフロー' #Visual Studio prodname_vs: 'Visual Studio' +prodname_vscode_shortname: 'VS Code' prodname_vscode: 'Visual Studio Code' prodname_vss_ghe: 'Visual Studio subscriptions with GitHub Enterprise' prodname_vss_admin_portal_with_url: '[Visual Studio subscriptions管理ポータル](https://visualstudio.microsoft.com/subscriptions-administration/)' -prodname_vscode_command_palette: 'VS Code Command Palette' +prodname_vscode_command_palette_shortname: 'VS Code Command Palette' +prodname_vscode_command_palette: 'Visual Studio Code Command Palette' +prodname_vscode_marketplace: 'Visual Studio Code Marketplace' +prodname_vs_marketplace_shortname: 'VS Code Marketplace' #GitHub Dependabot prodname_dependabot: 'Dependabot' prodname_dependabot_alerts: 'Dependabotアラート' diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv index 079cc197fb..99e7d9a1c2 100644 --- a/translations/log/cn-resets.csv +++ b/translations/log/cn-resets.csv @@ -4,12 +4,11 @@ translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifi 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,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,broken liquid tags -translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,broken liquid tags -translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,rendering error -translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md,broken liquid tags -translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md,broken liquid tags +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md,broken liquid tags +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,broken liquid tags +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md,broken liquid tags translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md,broken liquid tags -translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md,broken liquid tags translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,broken liquid tags translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,Listed in localization-support#489 translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,broken liquid tags @@ -171,7 +170,6 @@ translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md,broken liquid tags translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,Listed in localization-support#489 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,broken liquid tags -translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md,broken liquid tags translations/zh-CN/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md,broken liquid tags translations/zh-CN/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,broken liquid tags translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md,broken liquid tags @@ -199,6 +197,7 @@ translations/zh-CN/content/developers/github-marketplace/github-marketplace-over translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md,broken liquid tags translations/zh-CN/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags translations/zh-CN/content/developers/webhooks-and-events/webhooks/about-webhooks.md,broken liquid tags +translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md,broken liquid tags translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md,broken liquid tags translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md,broken liquid tags @@ -294,6 +293,7 @@ translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml,Listed in loc translations/zh-CN/data/release-notes/enterprise-server/2-22/22.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/3-0/0.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/3-0/16.yml,broken liquid tags +translations/zh-CN/data/release-notes/enterprise-server/3-0/19.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/3-1/0.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/3-1/1.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/3-1/10.yml,broken liquid tags @@ -308,6 +308,7 @@ translations/zh-CN/data/release-notes/enterprise-server/3-1/18.yml,broken liquid translations/zh-CN/data/release-notes/enterprise-server/3-1/19.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/3-1/2.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/3-1/20.yml,broken liquid tags +translations/zh-CN/data/release-notes/enterprise-server/3-1/21.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/3-1/3.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/3-1/4.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/3-1/5.yml,broken liquid tags @@ -317,6 +318,9 @@ translations/zh-CN/data/release-notes/enterprise-server/3-1/8.yml,broken liquid translations/zh-CN/data/release-notes/enterprise-server/3-1/9.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml,broken liquid tags translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml,broken liquid tags +translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml,broken liquid tags +translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml,broken liquid tags +translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml,broken liquid tags translations/zh-CN/data/release-notes/github-ae/2021-03/2021-03-03.yml,broken liquid tags translations/zh-CN/data/reusables/actions/actions-use-policy-settings.md,broken liquid tags translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags @@ -335,6 +339,7 @@ translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning. translations/zh-CN/data/reusables/code-scanning/run-additional-queries.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/upload-sarif-ghas.md,broken liquid tags translations/zh-CN/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md,broken liquid tags +translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md,broken liquid tags translations/zh-CN/data/reusables/dotcom_billing/downgrade-org-to-free.md,broken liquid tags translations/zh-CN/data/reusables/enterprise-accounts/emu-password-reset-session.md,broken liquid tags translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md,rendering error diff --git a/translations/log/es-resets.csv b/translations/log/es-resets.csv index d3610cf372..33c03a3848 100644 --- a/translations/log/es-resets.csv +++ b/translations/log/es-resets.csv @@ -2,13 +2,6 @@ file,reason translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,broken liquid tags translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,Listed in localization-support#489 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,Listed in localization-support#489 -translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,Listed in localization-support#489 -translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,Listed in localization-support#489 -translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md,Listed in localization-support#489 -translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md,Listed in localization-support#489 -translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md,Listed in localization-support#489 -translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md,Listed in localization-support#489 -translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,Listed in localization-support#489 translations/es-ES/content/actions/automating-builds-and-tests/about-continuous-integration.md,broken liquid tags translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md,Listed in localization-support#489 translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md,Listed in localization-support#489 @@ -133,6 +126,7 @@ translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces- translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md,Listed in localization-support#489 translations/es-ES/content/codespaces/getting-started/deep-dive.md,Listed in localization-support#489 translations/es-ES/content/codespaces/index.md,Listed in localization-support#489 +translations/es-ES/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md,broken liquid tags translations/es-ES/content/codespaces/overview.md,Listed in localization-support#489 translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,Listed in localization-support#489 translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,Listed in localization-support#489 @@ -308,6 +302,7 @@ translations/es-ES/content/support/learning-about-github-support/about-github-su translations/es-ES/data/release-notes/enterprise-server/3-2/0-rc1.yml,broken liquid tags translations/es-ES/data/release-notes/enterprise-server/3-2/0.yml,broken liquid tags translations/es-ES/data/release-notes/github-ae/2021-06/2021-12-06.yml,broken liquid tags +translations/es-ES/data/release-notes/github-ae/2022-05/2022-05-17.yml,broken liquid tags translations/es-ES/data/reusables/actions/contacting-support.md,broken liquid tags translations/es-ES/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags translations/es-ES/data/reusables/actions/enterprise-storage-ha-backups.md,broken liquid tags diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv index 1d5b30b2b6..93fdea6b65 100644 --- a/translations/log/ja-resets.csv +++ b/translations/log/ja-resets.csv @@ -3,10 +3,10 @@ translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifi translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,broken liquid tags 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,broken liquid tags translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags -translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md,broken liquid tags -translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,broken liquid tags -translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md,broken liquid tags -translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,broken liquid tags +translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md,broken liquid tags +translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md,broken liquid tags +translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,broken liquid tags +translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md,broken liquid tags translations/ja-JP/content/actions/creating-actions/about-custom-actions.md,broken liquid tags translations/ja-JP/content/actions/creating-actions/publishing-actions-in-github-marketplace.md,broken liquid tags translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,broken liquid tags @@ -21,6 +21,7 @@ translations/ja-JP/content/actions/using-github-hosted-runners/about-github-host translations/ja-JP/content/actions/using-workflows/storing-workflow-data-as-artifacts.md,broken liquid tags translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,broken liquid tags +translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md,broken liquid tags translations/ja-JP/content/admin/configuration/configuring-network-settings/network-ports.md,broken liquid tags translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md,broken liquid tags translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,broken liquid tags @@ -221,6 +222,7 @@ translations/ja-JP/data/release-notes/enterprise-server/2-21/6.yml,Listed in loc translations/ja-JP/data/release-notes/enterprise-server/2-22/22.yml,broken liquid tags translations/ja-JP/data/release-notes/enterprise-server/3-0/0.yml,broken liquid tags translations/ja-JP/data/release-notes/enterprise-server/3-0/16.yml,broken liquid tags +translations/ja-JP/data/release-notes/enterprise-server/3-0/19.yml,broken liquid tags translations/ja-JP/data/release-notes/enterprise-server/3-1/0.yml,broken liquid tags translations/ja-JP/data/release-notes/enterprise-server/3-1/1.yml,broken liquid tags translations/ja-JP/data/release-notes/enterprise-server/3-1/10.yml,broken liquid tags @@ -235,6 +237,7 @@ translations/ja-JP/data/release-notes/enterprise-server/3-1/18.yml,broken liquid translations/ja-JP/data/release-notes/enterprise-server/3-1/19.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/20.yml,broken liquid tags +translations/ja-JP/data/release-notes/enterprise-server/3-1/21.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 translations/ja-JP/data/release-notes/enterprise-server/3-1/5.yml,broken liquid tags @@ -244,6 +247,7 @@ translations/ja-JP/data/release-notes/enterprise-server/3-1/8.yml,broken liquid translations/ja-JP/data/release-notes/enterprise-server/3-1/9.yml,broken liquid tags translations/ja-JP/data/release-notes/enterprise-server/3-2/0-rc1.yml,broken liquid tags translations/ja-JP/data/release-notes/enterprise-server/3-2/0.yml,broken liquid tags +translations/ja-JP/data/release-notes/enterprise-server/3-2/3.yml,broken liquid tags translations/ja-JP/data/release-notes/github-ae/2021-03/2021-03-03.yml,broken liquid tags translations/ja-JP/data/reusables/actions/allow-specific-actions-intro.md,broken liquid tags translations/ja-JP/data/reusables/actions/disabling-github-actions.md,broken liquid tags diff --git a/translations/log/pt-resets.csv b/translations/log/pt-resets.csv index f606f27ae2..042dbe0c4a 100644 --- a/translations/log/pt-resets.csv +++ b/translations/log/pt-resets.csv @@ -26,7 +26,6 @@ translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.m translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md,broken liquid tags translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md,broken liquid tags translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,broken liquid tags -translations/pt-BR/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,broken liquid tags translations/pt-BR/content/github/index.md,Listed in localization-support#489 translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error @@ -40,7 +39,6 @@ translations/pt-BR/content/packages/working-with-a-github-packages-registry/work translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,Listed in localization-support#489 translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,broken liquid tags translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,broken liquid tags -translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md,broken liquid tags translations/pt-BR/content/rest/activity/events.md,broken liquid tags translations/pt-BR/content/rest/enterprise-admin/index.md,broken liquid tags translations/pt-BR/content/support/learning-about-github-support/about-github-support.md,broken liquid tags diff --git a/translations/pt-BR/content/account-and-profile/index.md b/translations/pt-BR/content/account-and-profile/index.md index 1804f7f0ff..21e67ac6e3 100644 --- a/translations/pt-BR/content/account-and-profile/index.md +++ b/translations/pt-BR/content/account-and-profile/index.md @@ -37,7 +37,7 @@ topics: - Profiles - Notifications children: - - /setting-up-and-managing-your-github-user-account + - /setting-up-and-managing-your-personal-account-on-github - /setting-up-and-managing-your-github-profile - /managing-subscriptions-and-notifications-on-github --- diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md index 8bf7e159fe..9f48a72b7c 100644 --- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md @@ -129,8 +129,8 @@ Email notifications from {% data variables.product.product_location %} contain t | --- | --- | | `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. | | `To` field | This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} | -| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
  • `assign`: You were assigned to an issue or pull request.
  • `author`: You created an issue or pull request.
  • `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
  • `comment`: You commented on an issue or pull request.
  • `manual`: There was an update to an issue or pull request you manually subscribed to.
  • `mention`: You were mentioned on an issue or pull request.
  • `push`: Someone committed to a pull request you're subscribed to.
  • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
    • {% endif %}
  • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
  • `subscribed`: There was an update in a repository you're watching.
  • `team_mention`: A team you belong to was mentioned on an issue or pull request.
  • `your_activity`: You opened, commented on, or closed an issue or pull request.
| -| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
  • `assign`: You were assigned to an issue or pull request.
  • `author`: You created an issue or pull request.
  • `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
  • `comment`: You commented on an issue or pull request.
  • `manual`: There was an update to an issue or pull request you manually subscribed to.
  • `mention`: You were mentioned on an issue or pull request.
  • `push`: Someone committed to a pull request you're subscribed to.
  • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • {% ifversion fpt or ghes or ghae or ghec %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
    • {% endif %}
  • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
  • `subscribed`: There was an update in a repository you're watching.
  • `team_mention`: A team you belong to was mentioned on an issue or pull request.
  • `your_activity`: You opened, commented on, or closed an issue or pull request.
| +| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae or ghec %} | `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
  • `low`
  • `moderate`
  • `high`
  • `critical`
For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %} ## Choosing your notification settings @@ -139,7 +139,7 @@ Email notifications from {% data variables.product.product_location %} contain t {% data reusables.notifications-v2.manage-notifications %} 3. On the notifications settings page, choose how you receive notifications when: - There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)." - - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} + - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae or ghec %} - There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% endif %} {% ifversion fpt or ghec %} - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5668 %} - There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."{% endif %} @@ -194,7 +194,7 @@ If you are a member of more than one organization, you can configure each one to 5. Select one of your verified email addresses, then click **Save**. ![Switching your per-org email address](/assets/images/help/notifications/notifications_switching_org_email.gif) -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## {% data variables.product.prodname_dependabot_alerts %} notification options {% data reusables.notifications.vulnerable-dependency-notification-enable %} diff --git a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md index 5021bc750c..6c7acf29d2 100644 --- a/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md +++ b/translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md @@ -112,13 +112,13 @@ Para filtrar notificações para uma atividade específica no {% data variables. - `is:gist` - `is:issue-or-pull-request` - `is:release` -- `is:repository-invitation`{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +- `is:repository-invitation`{% ifversion fpt or ghes or ghae or ghec %} - `is:repository-vulnerability-alert`{% endif %}{% ifversion fpt or ghec %} - `is:repository-advisory`{% endif %} - `is:team-discussion`{% ifversion fpt or ghec %} - `is:discussion`{% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} Para informações sobre a redução de ruído de notificações para {% data variables.product.prodname_dependabot_alerts %}, consulte "[Configurar notificações para dependências vulneráveis](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)". {% endif %} @@ -142,7 +142,7 @@ Para filtrar notificações por motivos pelos quais recebeu uma atualização, v | `reason:invitation` | Quando você for convidado para uma equipe, organização ou repositório. | | `reason:manual` | Quando você clicar em **Assinar** em um problema ou uma pull request que você ainda não estava inscrito. | | `reason:mention` | Você foi @mencionado diretamente. | -| `reason:review-requested` | Foi solicitado que você ou uma equipe revise um um pull request.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| `reason:review-requested` | Foi solicitado que você ou uma equipe revise um um pull request.{% ifversion fpt or ghes or ghae or ghec %} | `reason:security-alert` | Quando um alerta de segurança é emitido para um repositório.{% endif %} | `reason:state-change` | Quando o estado de uma pull request ou um problema é alterado. Por exemplo, um problema é fechado ou uma pull request é mesclada. | | `reason:team-mention` | Quando uma equipe da qual você é integrante é @mencionada. | @@ -161,7 +161,7 @@ Por exemplo, para ver notificações da organização octo-org, use `org:octo-or {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Filtros personalizados de {% data variables.product.prodname_dependabot %} {% ifversion fpt or ghec or ghes > 3.2 %} @@ -173,7 +173,7 @@ Se você usar {% data variables.product.prodname_dependabot %} para manter suas Para obter mais informações sobre {% data variables.product.prodname_dependabot %}, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." {% endif %} -{% ifversion ghes < 3.3 or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae %} Se você usar {% data variables.product.prodname_dependabot %} para falar sobre dependências vulneráveis, você pode usar e salvar esses filtros personalizados para mostrar notificações para {% data variables.product.prodname_dependabot_alerts %}: - `is:repository_vulnerability_alert` diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md index 01107f57b4..ea9c975529 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md @@ -92,10 +92,7 @@ A seção de atividade de contribuição contém uma linha do tempo detalhada do ![Filtro de hora de atividade de contribuição](/assets/images/help/profile/contributions_activity_time_filter.png) -{% ifversion fpt or ghes or ghae or ghec %} - ## Exibir contribuições da {% data variables.product.prodname_enterprise %} no {% data variables.product.prodname_dotcom_the_website %} Se você usar {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} ou {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} e proprietário da sua empresa permiteir {% data variables.product.prodname_unified_contributions %}, você poderá enviar contribuições corporativas a partir do seu perfil de {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Enviando contribuições corporativas para seu perfil de {% data variables.product.prodname_dotcom_the_website %}](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)". -{% endif %} diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md similarity index 50% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md index 55f009e2fe..51f384d8af 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md @@ -1,10 +1,11 @@ --- -title: Configurar e gerenciar sua conta de usuário do GitHub -intro: 'Você pode gerenciar as configurações na sua conta pessoal do GitHub, incluindo preferências de e-mail, acesso de colaborador para repositórios pessoais e associações de organizações.' +title: Setting up and managing your personal account on GitHub +intro: 'You can manage settings for your personal account on {% data variables.product.prodname_dotcom %}, including email preferences, collaborator access for personal repositories, and organization memberships.' shortTitle: Contas pessoais redirect_from: - /categories/setting-up-and-managing-your-github-user-account - /github/setting-up-and-managing-your-github-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account versions: fpt: '*' ghes: '*' @@ -13,7 +14,7 @@ versions: topics: - Accounts children: - - /managing-user-account-settings + - /managing-personal-account-settings - /managing-email-preferences - /managing-access-to-your-personal-repositories - /managing-your-membership-in-organizations diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md similarity index 80% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md index f871e59c09..26b3c33099 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md @@ -6,6 +6,7 @@ redirect_from: - /categories/managing-repository-collaborators - /articles/managing-access-to-your-personal-repositories - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' @@ -19,7 +20,7 @@ children: - /inviting-collaborators-to-a-personal-repository - /removing-a-collaborator-from-a-personal-repository - /removing-yourself-from-a-collaborators-repository - - /maintaining-ownership-continuity-of-your-user-accounts-repositories + - /maintaining-ownership-continuity-of-your-personal-accounts-repositories shortTitle: Acesso aos seus repositórios --- 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-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md similarity index 96% rename from 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 rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index 1a545e7e0e..abac96b1ef 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-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md @@ -7,6 +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 + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md similarity index 90% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md index c9e82096f1..f097f1bad9 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md @@ -1,5 +1,5 @@ --- -title: Manter a continuidade da propriedade dos repositórios da sua conta de usuário +title: Maintaining ownership continuity of your personal account's repositories intro: Você pode convidar alguém para gerenciar seus repositórios pertencentes ao usuário se você não for capaz de fazê-lo. versions: fpt: '*' @@ -10,6 +10,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories shortTitle: Continuidade de propriedade --- 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md similarity index 93% rename from 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 rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md index c88edc9073..71cd23a01f 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md @@ -10,6 +10,7 @@ redirect_from: - /articles/removing-a-collaborator-from-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md similarity index 90% rename from 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 rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md index a3e12bda7b..5a0e9e7af2 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md @@ -9,6 +9,7 @@ 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 + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md similarity index 92% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md index 9a1aa37787..e4105746ab 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -5,6 +5,7 @@ redirect_from: - /articles/adding-an-email-address-to-your-github-account - /github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md similarity index 92% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md index aad00ab5f6..e277e1c8f6 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/blocking-command-line-pushes-that-expose-your-personal-email-address - /github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address versions: fpt: '*' ghec: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md similarity index 93% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md index a81525e47b..641c0c62cd 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/changing-your-primary-email-address - /github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md similarity index 91% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md index 9676c64eeb..125e4a7f22 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md @@ -5,6 +5,7 @@ redirect_from: - /categories/managing-email-preferences - /articles/managing-email-preferences - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md similarity index 93% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md index a95066589c..0602fff6a7 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md @@ -5,6 +5,7 @@ redirect_from: - /articles/managing-marketing-emails-from-github - /github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github versions: fpt: '*' ghec: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md similarity index 94% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md index f2a2eb4c76..4ff5ca119e 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md @@ -7,6 +7,7 @@ redirect_from: - /articles/remembering-your-github-username-or-email - /github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email versions: fpt: '*' ghes: '*' @@ -72,5 +73,5 @@ Seu nome de usuário aparece logo após `https://{% data variables.command_line. {% ifversion fpt or ghec %} ## Leia mais -- "[Verificar o endereço de e-mail](/articles/verifying-your-email-address)" +- "[Verificar endereço de e-mail](/articles/verifying-your-email-address)" {% endif %} diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md similarity index 90% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md index b019d42aa9..5c035a981c 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/setting-a-backup-email-address - /github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md similarity index 98% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md index 0eb122b51e..7fd59db474 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md @@ -12,6 +12,7 @@ redirect_from: - /articles/setting-your-commit-email-address - /github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md similarity index 96% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md index 87a3d7bb92..98917b1c19 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md @@ -5,6 +5,7 @@ redirect_from: - /articles/types-of-emails-github-sends - /github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends versions: fpt: '*' ghec: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md similarity index 97% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md index fcb4f70b20..013236c4d0 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md @@ -6,6 +6,7 @@ redirect_from: - /articles/about-your-personal-dashboard - /github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard intro: 'Você pode visitar seu painel pessoal para acompanhar problemas e pull requests nos quais está trabalhando ou seguindo, navegar para os repositórios principais e páginas de equipe, manter-se atualizado sobre atividades recentes nas organizações e nos repositórios em que está inscrito e explorar repositórios recomendados.' versions: fpt: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md similarity index 95% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md index 68f868df84..5c163be9bf 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md @@ -5,6 +5,7 @@ redirect_from: - /articles/best-practices-for-leaving-your-company - /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company versions: fpt: '*' ghec: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md similarity index 87% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md index 5eacc79416..6d543bdcb7 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md @@ -9,6 +9,7 @@ redirect_from: - /articles/changing-your-github-username - /github/setting-up-and-managing-your-github-user-account/changing-your-github-username - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username versions: fpt: '*' ghes: '*' @@ -76,10 +77,10 @@ Após alteração do nome de usuário, os links para sua página de perfil anter {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.account_settings %} -3. Na seção "Change username" (Alterar nome de usuário), clique em **Change username** (Alterar nome de usuário). ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %} -4. Leia os avisos sobre a mudança de seu nome de usuário. Se você ainda quiser alterar seu nome de usuário, clique em **I understand, let's change my username** (Compreendo, vamos alterar meu nome de usuário). ![Botão de aviso Change Username (Alterar nome de usuário)](/assets/images/help/settings/settings-change-username-warning-button.png) +3. In the "Change username" section, click **Change username**. ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %} +4. Leia os avisos sobre a mudança de seu nome de usuário. If you still want to change your username, click **I understand, let's change my username**. ![Botão de aviso Change Username (Alterar nome de usuário)](/assets/images/help/settings/settings-change-username-warning-button.png) 5. Digite um novo nome de usuário. ![Campo New Username (Novo nome de usuário)](/assets/images/help/settings/settings-change-username-enter-new-username.png) -6. Se o nome que você escolheu estiver disponível, clique em **Change my username** (Alterar meu nome de usuário). Se o nome que você escolheu estiver indisponível, tente um nome de usuário diferente ou uma das sugestões que aparecem. ![Botão de aviso Change Username (Alterar nome de usuário)](/assets/images/help/settings/settings-change-my-username-button.png) +6. If the username you've chosen is available, click **Change my username**. Se o nome que você escolheu estiver indisponível, tente um nome de usuário diferente ou uma das sugestões que aparecem. ![Botão de aviso Change Username (Alterar nome de usuário)](/assets/images/help/settings/settings-change-my-username-button.png) {% endif %} ## Leia mais diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md similarity index 94% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md index ef9cdbf958..a8c500b5ea 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md @@ -6,6 +6,7 @@ redirect_from: - /articles/converting-a-user-into-an-organization - /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization intro: Você pode converter a sua conta pessoal em uma organização. Isso permite permissões mais granulares para repositórios que pertencem à organização. versions: fpt: '*' @@ -48,7 +49,7 @@ Você também pode converter sua conta pessoal diretamente em uma organização. 2. [Deixe qualquer organização](/articles/removing-yourself-from-an-organization) a conta pessoal que você está convertendo começou a participar. {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.organizations %} -5. Em "Transform account" (Transformar conta), clique em **Turn into an organization** (Transformar em uma organização). ![Botão de conversão da organização](/assets/images/help/settings/convert-to-organization.png) +5. Under "Transform account", click **Turn into an organization**. ![Botão de conversão da organização](/assets/images/help/settings/convert-to-organization.png) 6. Na caixa de diálogo Account Transformation Warning (Aviso de transformação da conta), revise e confirme a conversão. Observe que as informações nessa caixa são as mesmas do aviso no início deste artigo. ![Aviso de conversão](/assets/images/help/organizations/organization-account-transformation-warning.png) 7. Na página "Transform your user into an organization" (Transformar usuário em uma organização), em "Choose an organization owner" (Escolher um proprietário da organização), escolha a conta pessoal secundária que você criou na seção anterior ou outro usuário em que confia para gerenciar a organização. ![Página Add organization owner (Adicionar proprietário da organização)](/assets/images/help/organizations/organization-add-owner.png) 8. Escolha a assinatura da nova organização e insira as informações de cobrança se solicitado. diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md similarity index 96% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md index 93218c1700..bd6a186b84 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md @@ -1,11 +1,12 @@ --- -title: Excluir sua conta de usuário +title: Deleting your personal account intro: 'Você pode excluir sua conta pessoal em {% data variables.product.product_name %} a qualquer momento.' redirect_from: - /articles/deleting-a-user-account - /articles/deleting-your-user-account - /github/setting-up-and-managing-your-github-user-account/deleting-your-user-account - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md similarity index 68% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md index 1815a2918e..690f54559d 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md @@ -6,6 +6,7 @@ redirect_from: - /categories/user-accounts - /articles/managing-user-account-settings - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings versions: fpt: '*' ghes: '*' @@ -18,15 +19,15 @@ children: - /managing-your-theme-settings - /managing-your-tab-size-rendering-preference - /changing-your-github-username - - /merging-multiple-user-accounts + - /merging-multiple-personal-accounts - /converting-a-user-into-an-organization - - /deleting-your-user-account - - /permission-levels-for-a-user-account-repository - - /permission-levels-for-user-owned-project-boards + - /deleting-your-personal-account + - /permission-levels-for-a-personal-account-repository + - /permission-levels-for-a-project-board-owned-by-a-personal-account - /managing-accessibility-settings - /managing-the-default-branch-name-for-your-repositories - - /managing-security-and-analysis-settings-for-your-user-account - - /managing-access-to-your-user-accounts-project-boards + - /managing-security-and-analysis-settings-for-your-personal-account + - /managing-access-to-your-personal-accounts-project-boards - /integrating-jira-with-your-personal-projects - /best-practices-for-leaving-your-company - /what-does-the-available-for-hire-checkbox-do diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md similarity index 92% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md index 654780a195..259186629a 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md @@ -5,6 +5,7 @@ redirect_from: - /articles/integrating-jira-with-your-personal-projects - /github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects versions: ghes: '*' ghae: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md similarity index 92% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md index a2e1089b60..21ebe854d2 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md @@ -1,5 +1,5 @@ --- -title: Gerenciar acessos aos quadros de projetos de sua conta de usuário +title: Managing access to your personal account's project boards intro: 'Como proprietário de quadro de projeto, você pode adicionar ou remover um colaborador e personalizar as permissões dele em um quadro de projeto.' redirect_from: - /articles/managing-project-boards-in-your-repository-or-organization @@ -7,6 +7,7 @@ redirect_from: - /articles/managing-access-to-your-user-accounts-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md similarity index 91% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md index c00e0d550c..bb46c833d2 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md @@ -3,6 +3,8 @@ title: Gerenciando configurações de acessibilidade intro: 'Você pode desabilitar os principais atalhos em {% data variables.product.prodname_dotcom %} nas suas configurações de acessibilidade.' versions: feature: keyboard-shortcut-accessibility-setting +redirect_from: + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings --- ## Sobre as configurações de acessibilidade diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md similarity index 94% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md index 4134b3b9c2..5c3e0ecf1a 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md @@ -1,5 +1,5 @@ --- -title: Gerenciar as configurações de segurança e análise para a sua conta de usuário +title: Managing security and analysis settings for your personal account intro: 'Você pode controlar recursos que protegem e analisam o código nos seus projetos no {% data variables.product.prodname_dotcom %}.' versions: fpt: '*' @@ -10,6 +10,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account shortTitle: Gerenciar segurança & análise --- diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md similarity index 100% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md 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-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md similarity index 84% rename from 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 rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md index 3d01382e2c..501ede1bc1 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-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md @@ -9,6 +9,8 @@ versions: topics: - Accounts shortTitle: Gerenciando o tamanho da sua aba +redirect_from: + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference --- 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. 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-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md similarity index 69% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md index 3a568d8445..037960a34f 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-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md @@ -11,6 +11,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings shortTitle: Gerenciar configurações de tema --- @@ -18,7 +19,7 @@ Por escolha e flexibilidade sobre como e quando você usa {% data variables.prod Você pode querer usar um tema escuro para reduzir o consumo de energia em certos dispositivos, reduzir o cansaço da vista em condições com pouca luz, ou porque você prefere o tema. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}Se você tiver baixa visão, você poderá aproveitar um tema de alto contraste, com maior contraste entre o primeiro plano e os elementos de segundo plano.{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} se você for daltônico, você poderá beneficiar-se dos nossos temas de cor clara e escura. +{% ifversion fpt or ghes > 3.2 or ghae or ghec %}Se você tiver baixa visão, você poderá aproveitar um tema de alto contraste, com maior contraste entre o primeiro plano e os elementos de segundo plano.{% endif %}{% ifversion fpt or ghae or ghec %} se você for daltônico, você poderá beneficiar-se dos nossos temas de cor clara e escura. {% endif %} @@ -31,10 +32,10 @@ Você pode querer usar um tema escuro para reduzir o consumo de energia em certo 1. Clique no tema que deseja usar. - Se você escolheu um único tema, clique em um tema. - {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} + {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} - Se você escolheu seguir as configurações do sistema, clique em um tema diurno e um tema noturno. - {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} + {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} {% ifversion fpt or ghec %} - Se você quiser escolher um tema que esteja atualmente em beta público, primeiro você deverá habilitá-lo com pré-visualização de recursos. Para obter mais informações, consulte "[Explorar versões de acesso antecipado com visualização de recursos em](/get-started/using-github/exploring-early-access-releases-with-feature-preview)".{% endif %} diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md similarity index 89% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md index b199b20b96..00fb0fc2c0 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md @@ -1,5 +1,5 @@ --- -title: Fazer merge de várias contas de usuário +title: Merging multiple personal accounts intro: 'Se você tem contas separadas para o trabalho e uso pessoal, é possível fazer merge das contas.' redirect_from: - /articles/can-i-merge-two-accounts @@ -7,6 +7,7 @@ redirect_from: - /articles/merging-multiple-user-accounts - /github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts versions: fpt: '*' ghec: '*' @@ -39,7 +40,7 @@ shortTitle: Fazer merge de várias contas pessoais 1. [Transfira quaisquer repositórios](/articles/how-to-transfer-a-repository) da conta que você quer excluir para a conta que quer manter. Os problemas, pull requests e wikis também serão transferidos. Verifique se os repositórios estão na conta que você quer manter. 2. [Atualize as URLs remote](/github/getting-started-with-github/managing-remote-repositories) em quaisquer clones locais dos repositórios que foram movidos. -3. [Exclua a conta](/articles/deleting-your-user-account) que não quer mais usar. +3. [Exclua a conta](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account) que não quer mais usar. 4. Para atribuir commits anteriores à nova conta, adicione o endereço de e-mail que você usou para criar os commits para a conta que você está mantendo. Para obter mais informações, consulte "[Por que minhas contribuições não aparecem no meu perfil?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)" ## Leia mais diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md similarity index 98% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md index 15583bc6b2..d0ce67fb2d 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md @@ -1,10 +1,11 @@ --- -title: Níveis de permissão para um repositório de conta de usuário +title: Permission levels for a personal account repository intro: 'Um repositório pertencente a uma conta pessoal tem dois níveis de permissão: o proprietário e os colaboradores do repositório.' redirect_from: - /articles/permission-levels-for-a-user-account-repository - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository versions: fpt: '*' ghes: '*' @@ -12,7 +13,7 @@ versions: ghec: '*' topics: - Accounts -shortTitle: Repositórios de usuário de permissão +shortTitle: Permissões do repositório --- ## Sobre níveis de permissão para o repositório de uma conta pessoal @@ -46,7 +47,7 @@ O proprietário do repositório tem controle total do repositório. Além das a | Excluir e restaurar pacotes | "[Excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)" {% endif %} | Personalizar a visualização das mídias sociais do repositório | "[Personalizar a visualização das mídias sociais do seu repositório](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | -| Criar um modelo a partir do repositório | "[Criando um repositório de modelo](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)"{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| Criar um modelo a partir do repositório | "[Criando um repositório de modelo](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)"{% ifversion fpt or ghes or ghae or ghec %} | Controle o acesso a {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis | "[Gerenciar as configurações de segurança e análise do repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %} | Ignorar {% data variables.product.prodname_dependabot_alerts %} no repositório | "[Visualizando {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | | Gerenciar o uso de dados para um repositório privado | "[Gerenciar as configurações de uso de dados para o seu repositório privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)" diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md similarity index 92% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md index 35a70e775a..2ef7b1517a 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md @@ -1,10 +1,11 @@ --- -title: Níveis de permissão em quadros de projeto pertencentes a usuários +title: Permission levels for a project board owned by a personal account intro: 'Um quadro de projeto pertencente a uma conta pessoal tem dois níveis de permissão: o proprietário e colaboradores do quadro do projeto.' redirect_from: - /articles/permission-levels-for-user-owned-project-boards - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards versions: fpt: '*' ghes: '*' @@ -12,7 +13,7 @@ versions: ghec: '*' topics: - Accounts -shortTitle: Permissão de seções de projetos do usuário +shortTitle: Permissões do quadro de projeto --- ## Visão geral das permissões diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md similarity index 92% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md index 99e7d2955b..dd3f7ce381 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md @@ -5,6 +5,7 @@ redirect_from: - /articles/what-does-the-available-for-hire-checkbox-do - /github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do versions: fpt: '*' ghec: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md similarity index 96% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md index 4f3f9297b3..a9d942fce7 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md @@ -5,6 +5,7 @@ redirect_from: - /articles/about-organization-membership - /github/setting-up-and-managing-your-github-user-account/about-organization-membership - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md similarity index 86% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md index 5087d5022f..fb691ceb60 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md @@ -8,6 +8,7 @@ redirect_from: - /articles/accessing-an-organization - /github/setting-up-and-managing-your-github-user-account/accessing-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md similarity index 88% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md index de7b8536e1..9013c54dda 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md @@ -4,6 +4,7 @@ intro: 'Se você é integrante de uma organização, é possível divulgar ou oc redirect_from: - /articles/managing-your-membership-in-organizations - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md similarity index 96% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md index e3d85c86b6..07ba2d336b 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md @@ -9,6 +9,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders shortTitle: Gerenciar lembretes agendados --- diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md similarity index 90% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md index 9eaa28f7ff..3819b5432e 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md @@ -6,6 +6,7 @@ redirect_from: - /articles/publicizing-or-hiding-organization-membership - /github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md similarity index 91% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md index 7fc980189c..630d5cb7d5 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md @@ -6,6 +6,7 @@ redirect_from: - /articles/removing-yourself-from-an-organization - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md similarity index 92% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md index 3dd6e3407a..cd78e8b39a 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md @@ -7,6 +7,7 @@ redirect_from: - /articles/requesting-organization-approval-for-oauth-apps - /github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps versions: fpt: '*' ghec: '*' diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md similarity index 97% rename from translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md rename to translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md index 480e7ba401..cbe11c0e3b 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md @@ -7,6 +7,7 @@ redirect_from: - /articles/viewing-peoples-roles-in-an-organization - /github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md deleted file mode 100644 index 03d6dfdc37..0000000000 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: Criar e testar Node.js ou Python -shortTitle: Criar & testar Node.js ou Python -intro: É possível criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu projeto. Use o seletor de linguagem para mostrar exemplos para a sua linguagem de escolha. -redirect_from: - - /actions/guides/building-and-testing-nodejs-or-python -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: tutorial -topics: - - CI ---- - - - diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index 0b09cf173b..586b62aaf5 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -11,13 +11,11 @@ versions: ghae: '*' ghec: '*' type: tutorial -hidden: true topics: - CI - Node - JavaScript shortTitle: Criar & testar Node.js -hasExperimentalAlternative: true --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md index 09afe8240e..443eb48166 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -11,12 +11,10 @@ versions: ghae: '*' ghec: '*' type: tutorial -hidden: true topics: - CI - Python shortTitle: Criar & testar o Python -hasExperimentalAlternative: true --- {% data reusables.actions.enterprise-beta %} @@ -246,7 +244,7 @@ steps: - run: pip test ``` -Por padrão, a ação `setup-python` busca o arquivo de dependência (`requirements.txt` para pip ou `Pipfile.lock` para pipenv) em todo o repositório. Para obter mais informações, consulte "[Armazenando em cache as dependências de pacotes](https://github.com/actions/setup-python#caching-packages-dependencies)" no README do `setup-python`. +By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip, `Pipfile.lock` for pipenv or `poetry.lock` for poetry) in the whole repository. Para obter mais informações, consulte "[Armazenando em cache as dependências de pacotes](https://github.com/actions/setup-python#caching-packages-dependencies)" no README do `setup-python`. Se você tiver um requisito personalizado ou precisar de melhores controles para cache, você poderá usar a ação [`cache`](https://github.com/marketplace/actions/cache). O Pip armazena dependências em diferentes locais, dependendo do sistema operacional do executor. O caminho que você precisa efetuar o armazenamento em cache pode ser diferente do exemplo do Ubuntu acima, dependendo do sistema operacional que você usa. Para obter mais informações, consulte [Exemplos de armazenamento em cache do Python](https://github.com/actions/cache/blob/main/examples.md#python---pip) no repositório de ação `cache`. diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/index.md b/translations/pt-BR/content/actions/automating-builds-and-tests/index.md index a91dbb30a3..4fa8dac77c 100644 --- a/translations/pt-BR/content/actions/automating-builds-and-tests/index.md +++ b/translations/pt-BR/content/actions/automating-builds-and-tests/index.md @@ -14,13 +14,14 @@ redirect_from: - /actions/language-and-framework-guides/github-actions-for-java - /actions/language-and-framework-guides/github-actions-for-javascript-and-typescript - /actions/language-and-framework-guides/github-actions-for-python + - /actions/guides/building-and-testing-nodejs-or-python + - /actions/automating-builds-and-tests/building-and-testing-nodejs-or-python children: - /about-continuous-integration - /building-and-testing-java-with-ant - /building-and-testing-java-with-gradle - /building-and-testing-java-with-maven - /building-and-testing-net - - /building-and-testing-nodejs-or-python - /building-and-testing-nodejs - /building-and-testing-powershell - /building-and-testing-python 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 b3dfb9a156..2d49269cd8 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 @@ -223,7 +223,7 @@ Por exemplo, este `cleanup.js` só será executado em executores baseados no Lin ### `runs.steps` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Obrigatório** As etapas de que você planeja executar nesta ação. Elas podem ser etapas de `run` ou etapas de `uses`. {% else %} **Obrigatório** As etapas de que você planeja executar nesta ação. @@ -231,7 +231,7 @@ Por exemplo, este `cleanup.js` só será executado em executores baseados no Lin #### `runs.steps[*].run` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Optional** O comando que você deseja executar. Isso pode ser inline ou um script no seu repositório de ação: {% else %} **Obrigatório** O comando que você deseja executar. Isso pode ser inline ou um script no seu repositório de ação: @@ -261,7 +261,7 @@ Para obter mais informações, consulte "[`github context`](/actions/reference/c #### `runs.steps[*].shell` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **Opcional** O shell onde você deseja executar o comando. Você pode usar qualquer um dos shells listados [aqui](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Obrigatório se `run` estiver configurado. {% else %} **Obrigatório** O shell onde você quer executar o comando. Você pode usar qualquer um dos shells listados [aqui](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Obrigatório se `run` estiver configurado. @@ -314,7 +314,7 @@ steps: **Opcional** Especifica o diretório de trabalho onde o comando é executado. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} #### `runs.steps[*].uses` **Opcional** Seleciona uma ação a ser executada como parte de uma etapa do seu trabalho. A ação é uma unidade reutilizável de código. Você pode usar uma ação definida no mesmo repositório que o fluxo de trabalho, um repositório público ou em uma [imagem publicada de contêiner Docker](https://hub.docker.com/). diff --git a/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md index 408de14ea7..85942e30a9 100644 --- a/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md +++ b/translations/pt-BR/content/actions/deployment/about-deployments/deploying-with-github-actions.md @@ -156,7 +156,7 @@ Você também pode criar um aplicativo que usa webhooks de status de implantaç ## Escolhendo um corredor -Você pode executar seu fluxo de trabalho de implantação em executores hospedados em {% data variables.product.company_short %} ou em executores auto-hospedados. O tráfego dos executores hospedados em {% data variables.product.company_short %} pode vir de uma [ampla gama de endereços de rede](/rest/reference/meta#get-github-meta-information). Se você estiver fazendo a implantação em um ambiente interno e sua empresa restringir o tráfego externo em redes privadas, os fluxos de trabalho de {% data variables.product.prodname_actions %} em execução em executores hospedados em {% data variables.product.company_short %} podem não ser comunicados com seus serviços ou recursos internos. Para superar isso, você pode hospedar seus próprios executores. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" e "[Sobre executores hospedados no GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners)." +Você pode executar seu fluxo de trabalho de implantação em executores hospedados em {% data variables.product.company_short %} ou em executores auto-hospedados. O tráfego dos executores hospedados em {% data variables.product.company_short %} pode vir de uma [ampla gama de endereços de rede](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be able to communicate with your internal services or resources. Para superar isso, você pode hospedar seus próprios executores. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" e "[Sobre executores hospedados no GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners)." {% endif %} diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md index 3ad705de52..c502cd04b8 100644 --- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md @@ -134,4 +134,4 @@ Os seguintes recursos também podem ser úteis: * Para o fluxo de trabalho inicial original, consulte [`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml) no repositório `starter-workflows` de {% data variables.product.prodname_actions %}. * A ação usada para fazer a implantação do aplicativo web é a ação oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) do Azure. * Para obter mais exemplos de fluxos de trabalho do GitHub Action que fazem a implantação no Azure, consulte o repositório [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples). -* O início rápido de "[Criar um aplicativo web Node.js no Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" na documentação do aplicativo web do Azure mostra como usar o VS Code com a [extensão do Azure App Service](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice). +* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using {% data variables.product.prodname_vscode %} with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice). diff --git a/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md index c1e1ea2515..3c82ac9aa4 100644 --- a/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md +++ b/translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md @@ -69,7 +69,7 @@ You can use any machine as a self-hosted runner as long at it meets these requir * 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. -{% ifversion fpt or ghes > 3.2 or ghec or ghae-issue-4462 %} +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## Autoscaling your self-hosted runners You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." 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 3c50f77346..69d4c85382 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 @@ -5,7 +5,7 @@ versions: fpt: '*' ghec: '*' ghes: '>3.2' - ghae: issue-4462 + ghae: '*' type: overview --- diff --git a/translations/pt-BR/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/pt-BR/content/actions/managing-workflow-runs/skipping-workflow-runs.md index 47eb1d1ff1..919b3491dc 100644 --- a/translations/pt-BR/content/actions/managing-workflow-runs/skipping-workflow-runs.md +++ b/translations/pt-BR/content/actions/managing-workflow-runs/skipping-workflow-runs.md @@ -14,7 +14,7 @@ shortTitle: Ignorar execução de fluxo de trabalho {% note %} -**Note:** If a workflow is skipped due to [path filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), [branch filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) or a commit message (see below), then checks associated with that workflow will remain in a "Pending" state. A pull request that requires those checks to be successful will be blocked from merging. +**Observação:** Se um fluxo de trabalho for ignorado devido ao [filtro de branch](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore) [branch filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) ou uma mensagem de commit (veja abaixo), as verificações associadas a esse fluxo de trabalho permanecerão em um estado "Pendente". Um pull request que requer que essas verificações sejam bem sucedidas será bloqueado do merge. {% endnote %} diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md index 30bf1058b5..63b49a3b79 100644 --- a/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/pt-BR/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -208,7 +208,8 @@ Os trabalhos simultâneos e os tempos de execução do fluxo de trabalho em {% d ### Usar diferentes linguagens em {% data variables.product.prodname_actions %} Ao trabalhar com diferentes linguagens em {% data variables.product.prodname_actions %}, você pode criar uma etapa no seu trabalho para configurar as dependências da sua linguagem. Para obter mais informações sobre como trabalhar com uma linguagem em particular, consulte o guia específico: - - [Criar e testar Node.js ou Python](/actions/guides/building-and-testing-nodejs-or-python) + - [Criar e testar Node.js](/actions/guides/building-and-testing-nodejs) + - [Criar e testar o Python](/actions/guides/building-and-testing-python) - [Criar e testar PowerShell](/actions/guides/building-and-testing-powershell) - [Criar e estar o Java com o Maven](/actions/guides/building-and-testing-java-with-maven) - [Criar e estar o Java com o Gradle](/actions/guides/building-and-testing-java-with-gradle) 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 918b8f6b84..f4f22800f1 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,11 +202,11 @@ Os mesmos princípios descritos acima para o uso de ações de terceiros também {% endif %} {% if allow-actions-to-approve-pr %} -## Preventing {% data variables.product.prodname_actions %} from {% if allow-actions-to-approve-pr-with-ent-repo %}creating or {% endif %}approving pull requests +## Impedindo que {% data variables.product.prodname_actions %} de {% if allow-actions-to-approve-pr-with-ent-repo %}crie ou {% endif %}aprove pull requests -{% data reusables.actions.workflow-pr-approval-permissions-intro %} Allowing workflows, or any other automation, to {% if allow-actions-to-approve-pr-with-ent-repo %}create or {% endif %}approve pull requests could be a security risk if the pull request is merged without proper oversight. +{% data reusables.actions.workflow-pr-approval-permissions-intro %} A permissão de fluxos de trabalho ou qualquer outra automação, para {% if allow-actions-to-approve-pr-with-ent-repo %}criar ou {% endif %}aprovar pull requests poderia ser um risco de segurança se o pull request fosse mesclado sem a supervisão adequada. -For more information on how to configure this setting, see {% if allow-actions-to-approve-pr-with-ent-repo %}{% ifversion ghes or ghec or ghae %}"[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#preventing-github-actions-from-creating-or-approving-pull-requests)",{% endif %}{% endif %} "[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#preventing-github-actions-from-{% if allow-actions-to-approve-pr-with-ent-repo %}creating-or-{% endif %}approving-pull-requests)"{% if allow-actions-to-approve-pr-with-ent-repo %}, and "[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#preventing-github-actions-from-creating-or-approving-pull-requests)"{% endif %}. +Para obter mais informações sobre como definir essa configuração, consulte {% if allow-actions-to-approve-pr-with-ent-repo %}{% ifversion ghes or ghec or ghae %}"[Aplicando políticas para {% data variables.product.prodname_actions %} na sua empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#preventing-github-actions-from-creating-or-approving-pull-requests)",{% endif %}{% endif %} "[Desabilitando ou limitando {% data variables.product.prodname_actions %} para a sua organização](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-{% if allow-actions-to-approve-pr-with-ent-repo %}creating-or-{% endif %}approving-pull-requests)"{% if allow-actions-to-approve-pr-with-ent-repo %}, and "[Gerenciando as configurações de {% data variables.product.prodname_actions %} para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests)"{% endif %}. {% endif %} ## Usando os Scorecards OpenSSF para proteger fluxos de trabalho diff --git a/translations/pt-BR/content/actions/using-jobs/using-conditions-to-control-job-execution.md b/translations/pt-BR/content/actions/using-jobs/using-conditions-to-control-job-execution.md index b3fcd995fb..a81e7a48f2 100644 --- a/translations/pt-BR/content/actions/using-jobs/using-conditions-to-control-job-execution.md +++ b/translations/pt-BR/content/actions/using-jobs/using-conditions-to-control-job-execution.md @@ -17,12 +17,12 @@ miniTocMaxHeadingLevel: 4 {% note %} -**Note:** A job that is skipped will report its status as "Success". It will not prevent a pull request from merging, even if it is a required check. +**Observação:** Um trabalho que ignorado irá relatar seu status como "Sucesso". Isso não impedirá o merge de um pull request mesmo que seja uma verificação necessária. {% endnote %} {% data reusables.actions.jobs.section-using-conditions-to-control-job-execution %} -You would see the following status on a skipped job: +Você verá o seguinte status em um trabalho ignorado: ![Skipped-required-run-details](/assets/images/help/repository/skipped-required-run-details.png) diff --git a/translations/pt-BR/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/pt-BR/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md index 300e22f883..964127c3b4 100644 --- a/translations/pt-BR/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md +++ b/translations/pt-BR/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md @@ -37,7 +37,7 @@ Para armazenar dependências em cache para um trabalho, você pode usar a ação setup-node - pip, pipenv + pip, pipenv, poetry setup-python 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 61a514326f..c75b0f63e1 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 @@ -24,7 +24,7 @@ Os acionadores de fluxo de trabalho são eventos que fazem com que um fluxo de t Alguns eventos têm vários tipos de atividades. Para esses eventos, você pode especificar quais tipos de atividade ativarão a execução de um fluxo de trabalho. Para obter mais informações sobre o significado de cada tipo de atividade, consulte "[Eventos de webhook e cargas](/developers/webhooks-and-events/webhook-events-and-payloads)". Observe que nem todos os eventos de webhook acionam fluxos de trabalho. -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4968 %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae %} ### `branch_protection_rule` | Carga de evento webhook | Tipos de atividade | `GITHUB_SHA` | `GITHUB_REF` | @@ -1051,7 +1051,7 @@ em: {% endnote %} -Executa o fluxo de trabalho quando a atividade de da versão no repositório ocorre. Para obter informações sobre as APIs de versões, consulte "[Release](/graphql/reference/objects#release)" na documentação da API do GraphQL ou "[Versões](/rest/reference/repos#releases)" na documentação da API REST. +Executa o fluxo de trabalho quando a atividade de da versão no repositório ocorre. Para obter informações sobre as APIs de versões, consulte "[Release](/graphql/reference/objects#release)" na documentação da API do GraphQL ou "[Versões](/rest/reference/releases)" na documentação da API REST. Por exemplo, você pode executar um fluxo de trabalho quando uma versão tiver sido `published`. 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 2cc86fbbdd..34b1393ffe 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 @@ -99,18 +99,18 @@ Você pode usar o comando `set-output` no seu fluxo de trabalho para definir o m A tabela a seguir mostra quais funções do conjunto de ferramentas estão disponíveis dentro de um fluxo de trabalho: -| Função do kit de ferramentas | Comando equivalente do fluxo de trabalho | -| ---------------------------- | --------------------------------------------------------------------- | -| `core.addPath` | Acessível usando o arquivo de ambiente `GITHUB_PATH` | -| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +| Função do kit de ferramentas | Comando equivalente do fluxo de trabalho | +| ---------------------------- | ---------------------------------------------------------------- | +| `core.addPath` | Acessível usando o arquivo de ambiente `GITHUB_PATH` | +| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `core.notice` | `notice` {% endif %} -| `core.error` | `erro` | -| `core.endGroup` | `endgroup` | -| `core.exportVariable` | Acessível usando o arquivo de ambiente `GITHUB_ENV` | -| `core.getInput` | Acessível por meio do uso da variável de ambiente `INPUT_{NAME}` | -| `core.getState` | Acessível por meio do uso da variável de ambiente `STATE_{NAME}` | -| `core.isDebug` | Acessível por meio do uso da variável de ambiente `RUNNER_DEBUG` | +| `core.error` | `erro` | +| `core.endGroup` | `endgroup` | +| `core.exportVariable` | Acessível usando o arquivo de ambiente `GITHUB_ENV` | +| `core.getInput` | Acessível por meio do uso da variável de ambiente `INPUT_{NAME}` | +| `core.getState` | Acessível por meio do uso da variável de ambiente `STATE_{NAME}` | +| `core.isDebug` | Acessível por meio do uso da variável de ambiente `RUNNER_DEBUG` | {%- if actions-job-summaries %} | `core.summary` | Pode ser acessado usando a variável de ambiente `GITHUB_STEP_SUMMARY` | {%- endif %} @@ -170,7 +170,7 @@ Write-Output "::debug::Set the Octocat variable" {% endpowershell %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ## Configurando uma mensagem de aviso diff --git a/translations/pt-BR/content/admin/code-security/index.md b/translations/pt-BR/content/admin/code-security/index.md index 901fe3d8f1..41abaa8a2c 100644 --- a/translations/pt-BR/content/admin/code-security/index.md +++ b/translations/pt-BR/content/admin/code-security/index.md @@ -5,7 +5,7 @@ intro: Você pode criar a segurança no fluxo de trabalho de seus desenvolvedore versions: ghes: '*' ghec: '*' - ghae: issue-4864 + ghae: '*' topics: - Enterprise children: diff --git a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md index f0b8e9106d..59656db324 100644 --- a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md @@ -5,7 +5,7 @@ shortTitle: Sobre a segurança da cadeia de suprimento permissions: '' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise diff --git a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md index a60feeb9e5..3bdc0b1caa 100644 --- a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md +++ b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md @@ -4,7 +4,7 @@ shortTitle: Segurança da cadeia de suprimento intro: 'Você pode visualizar, manter e proteger as dependências na cadeia de suprimento de software de seus desenvolvedores.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' topics: - Enterprise children: diff --git a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md index 12eb7c6c66..08bdd07a4d 100644 --- a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md @@ -5,7 +5,7 @@ shortTitle: Visualizando os dados de vulnerabilidade permissions: 'Site administrators can view vulnerability data on {% data variables.product.product_location %}.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md index 06f24815ea..1662c1c12d 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -12,7 +12,7 @@ topics: ## Sobre o {% data variables.product.prodname_github_connect %} -{% data variables.product.prodname_github_connect %} melhora {% data variables.product.product_name %}, o que permite que {% data variables.product.product_location %} se beneficie do poder de {% data variables.product.prodname_dotcom_the_website %} de maneira limitada. Depois que você habilitar {% data variables.product.prodname_github_connect %}, você pode habilitar recursos e fluxos de trabalho adicionais que dependem de {% data variables.product.prodname_dotcom_the_website %} como, por exemplo, {% ifversion ghes or ghae-issue-4864 %}{% data variables.product.prodname_dependabot_alerts %} para vulnerabilidades de segurança que são monitoradas no {% data variables.product.prodname_advisory_database %}{% else %}, o que permite que os usuários usem ações com base na comunidade de {% data variables.product.prodname_dotcom_the_website %} nos seus arquivos de fluxo de trabalho{% endif %}. +{% data variables.product.prodname_github_connect %} melhora {% data variables.product.product_name %}, o que permite que {% data variables.product.product_location %} se beneficie do poder de {% data variables.product.prodname_dotcom_the_website %} de maneira limitada. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}. {% data variables.product.prodname_github_connect %} não abre {% data variables.product.product_location %} para o público na internet. Nenhum dos dados privados da sua empresa está exposto os usuários de {% data variables.product.prodname_dotcom_the_website %}. Em vez disso, {% data variables.product.prodname_github_connect %} transmite apenas os dados limitados necessários para os recursos individuais que você optar por habilitar. A menos que você habilite a sincronização de licença, nenhum dado pessoal será transmitido por {% data variables.product.prodname_github_connect %}. Para obter mais informações sobre quais dados são transmitidos por {% data variables.product.prodname_github_connect %}, consulte "[Transmissão de dados para o {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)". @@ -28,7 +28,7 @@ Após configurar a conexão entre {% data variables.product.product_location %} | Funcionalidade | Descrição | Mais informações | | ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %} -| Sincronização automática da licença do usuário | Gerencie o uso da licença entre as suas implantações de {% data variables.product.prodname_enterprise %} sincronizando automaticamente as licenças de usuários de {% data variables.product.product_location %} para {% data variables.product.prodname_ghe_cloud %}. | "[Habilitando a sincronização automática de licença de usuário para sua empresa](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae-issue-4864 %} +| Sincronização automática da licença do usuário | Gerencie o uso da licença entre as suas implantações de {% data variables.product.prodname_enterprise %} sincronizando automaticamente as licenças de usuários de {% data variables.product.product_location %} para {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} | {% data variables.product.prodname_dependabot %} | Permite aos usuários encontrar e corrigir vulnerabilidades nas dependências do código. | "[Habilitando {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} | Ações de {% data variables.product.prodname_dotcom_the_website %} | Permitir que os usuários usem ações de {% data variables.product.prodname_dotcom_the_website %} em arquivos de fluxo de trabalho. | "[Hbilitando o acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% if server-statistics %} | {% data variables.product.prodname_server_statistics %} | Analise os seus próprios dados agregados do servidor do GitHub Enterprise e ajude-nos a melhorar os produtos do GitHub. | "[Habilitando {% data variables.product.prodname_server_statistics %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} @@ -62,9 +62,9 @@ Ao habilitar {% data variables.product.prodname_github_connect %} ou funcionalid Os dados adicionais são transmitidos se você habilitar as funcionalidades individuais de {% data variables.product.prodname_github_connect %}. -| Funcionalidade | Dados | Para onde os dados são transmitidos? | Onde os dados são usados? | -| ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |{% ifversion ghes %} -| Sincronização automática da licença do usuário | O ID de usuário de cada {% data variables.product.product_name %} e endereço de e-mail | De {% data variables.product.product_name %} para {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %} +| Funcionalidade | Dados | Para onde os dados são transmitidos? | Onde os dados são usados? | +| ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------ |{% ifversion ghes %} +| Sincronização automática da licença do usuário | O ID de usuário de cada {% data variables.product.product_name %} e endereço de e-mail | De {% data variables.product.product_name %} para {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %} | {% data variables.product.prodname_dependabot_alerts %} | Alertas de vulnerabilidade | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %} | {% data variables.product.prodname_dependabot_updates %} | As dependências e metadados para o repositório de cada dependência

Se uma dependência for armazenada em um repositório privado em {% data variables.product.prodname_dotcom_the_website %}, os dados só serão transmitidos se {% data variables.product.prodname_dependabot %} estiver configurado e autorizado para acessar esse repositório. | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} | Ações de {% data variables.product.prodname_dotcom_the_website %} | Nome da ação, ação (arquivo YAML de {% data variables.product.prodname_marketplace %}) | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %}

De {% data variables.product.product_name %} para {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% if server-statistics %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md index 6b90321137..13b05b9c38 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -15,7 +15,7 @@ redirect_from: permissions: 'Enterprise owners can enable {% data variables.product.prodname_dependabot %}.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise @@ -64,6 +64,8 @@ Após habilitar {% data variables.product.prodname_dependabot_alerts %}, você p {% endnote %} +By default, {% data variables.product.prodname_actions %} runners used by {% data variables.product.prodname_dependabot %} need access to the internet, to download updated packages from upstream package managers. For {% data variables.product.prodname_dependabot_updates %} powered by {% data variables.product.prodname_github_connect %}, internet access provides your runners with a token that allows access to dependencies and advisories hosted on {% data variables.product.prodname_dotcom_the_website %}. + Com {% data variables.product.prodname_dependabot_updates %}, {% data variables.product.company_short %} cria automaticamente pull requests para atualizar dependências de duas maneiras. - **{% data variables.product.prodname_dependabot_version_updates %}**: Os usuários adicionam um arquivo de configuração de {% data variables.product.prodname_dependabot %} ao repositório para habilitar {% data variables.product.prodname_dependabot %} e criar pull requests quando uma nova versão de uma dependência monitorada for lançada. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)". @@ -120,6 +122,11 @@ Antes de habilitar {% data variables.product.prodname_dependabot_updates %}, voc ![Captura de tela do menu suspenso para habilitar a atualização de dependências vulneráveis](/assets/images/enterprise/site-admin-settings/dependabot-updates-button.png) -{% elsif ghes > 3.2 %} -Ao habilitar {% data variables.product.prodname_dependabot_alerts %}, você também deve considerar configurar {% data variables.product.prodname_actions %} para {% data variables.product.prodname_dependabot_security_updates %}. Este recurso permite aos desenvolvedores corrigir a vulnerabilidades nas suas dependências. Para obter mais informações, consulte "[Gerenciar executores auto-hospedados para {% data variables.product.prodname_dependabot_updates %} na sua empresa](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates). " +{% endif %} +{% ifversion ghes > 3.2 %} + +Ao habilitar {% data variables.product.prodname_dependabot_alerts %}, você também deve considerar configurar {% data variables.product.prodname_actions %} para {% data variables.product.prodname_dependabot_security_updates %}. Este recurso permite aos desenvolvedores corrigir a vulnerabilidades nas suas dependências. Para obter mais informações, consulte "[Gerenciar executores auto-hospedados para {% data variables.product.prodname_dependabot_updates %} na sua empresa](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates). " + +If you need enhanced security, we recommend configuring {% data variables.product.prodname_dependabot %} to use private registries. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_dependabot %}](/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot)." + {% endif %} 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 b725fd09d8..ecb8ae6884 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 @@ -674,6 +674,12 @@ Este utilitário reempacota manualmente uma rede de repositórios para otimizar Você pode adicionar o argumento opcional `--prune` para remover objetos inacessíveis do Git que não são referenciados em um branch, tag ou qualquer outra referência. Fazer isso é útil principalmente para remover de imediato [informações confidenciais já eliminadas](/enterprise/user/articles/remove-sensitive-data/). +{% warning %} + +**Aviso**: Antes de usar o argumento `--prune` para remover objetos Git inacessíveis, coloque {% data variables.product.product_location %} em modo de manutenção, ou certifique-se de que o repositório esteja off-line. Para obter mais informações, consulte "[Habilitar e programar o modo de manutenção](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)". + +{% endwarning %} + ```shell ghe-repo-gc username/reponame ``` diff --git a/translations/pt-BR/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md b/translations/pt-BR/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md index 2b018ddda0..d92c0ce963 100644 --- a/translations/pt-BR/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md +++ b/translations/pt-BR/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md @@ -33,12 +33,13 @@ Em seguida, quando for dito para buscar `https://github.example.com/myorg/myrepo ## Configurando um cache de repositório -1. Durante o beta, você deve habilitar o sinalizador de recurso para o cache do repositório no dispositivo principal de {% data variables.product.prodname_ghe_server %}. +{% ifversion ghes = 3.3 %} +1. No seu dispositivo primário de {% data variables.product.prodname_ghe_server %}, habilite o sinalizador do recurso para o cache do repositório. ``` $ ghe-config cluster.cache-enabled true ``` - +{%- endif %} 1. Configure um novo appliance do {% data variables.product.prodname_ghe_server %} na plataforma desejada. Este dispositivo será o cache do repositório. Para obter mais informações, consulte "[Configurar instância do {% data variables.product.prodname_ghe_server %}](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)". {% data reusables.enterprise_installation.replica-steps %} 1. Conecte ao endereço IP do repositório utilizando o SSH. @@ -46,7 +47,13 @@ Em seguida, quando for dito para buscar `https://github.example.com/myorg/myrepo ```shell $ ssh -p 122 admin@REPLICA IP ``` +{%- ifversion ghes = 3.3 %} +1. Na réplica do seu cache, habilite o sinalizador do recurso para o cache do repositório. + ``` + $ ghe-config cluster.cache-enabled true + ``` +{%- endif %} {% data reusables.enterprise_installation.generate-replication-key-pair %} {% data reusables.enterprise_installation.add-ssh-key-to-primary %} 1. Para verificar a conexão com o primário e habilitar o modo de réplica no cache do repositório, execute `ghe-repl-setup` novamente. diff --git a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md index 58243da6a2..881783fd92 100644 --- a/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md +++ b/translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md @@ -18,7 +18,7 @@ topics: O SNMP é um padrão comum para monitorar dispositivos em uma rede. É altamente recomendável ativar o SNMP para monitorar a integridade da {% data variables.product.product_location %} e saber quando adicionar mais memória, armazenamento ou potência do processador à máquina host. -O {% data variables.product.prodname_enterprise %} tem uma instalação SNMP padrão que permite aproveitar [vários plugins](http://www.monitoring-plugins.org/doc/man/check_snmp.html) disponíveis para Nagios ou qualquer outro sistema de monitoramento. +O {% data variables.product.prodname_enterprise %} tem uma instalação SNMP padrão que permite aproveitar [vários plugins](https://www.monitoring-plugins.org/doc/man/check_snmp.html) disponíveis para Nagios ou qualquer outro sistema de monitoramento. ## Configurar SMTP v2c @@ -66,7 +66,7 @@ Se habilitar o SNMP v3, você poderá aproveitar o aumento da segurança baseada #### Consultar dados SNMP -As informações de hardware e software do appliance estão disponíveis no SNMP v3. Devido à falta de criptografia e privacidade para os níveis de segurança dw `noAuthNoPriv` e `authNoPriv`, excluimos a tabela `hrSWRun` (1.3.6.1.2.1.25.4) dos relatórios SNMP resultantes. Incluímos esta tabela para o caso de você estar usando o nível de segurança `authPriv`. Para obter mais informações, consulte a "[Documentação de referência do OID](http://oidref.com/1.3.6.1.2.1.25.4)". +As informações de hardware e software do appliance estão disponíveis no SNMP v3. Devido à falta de criptografia e privacidade para os níveis de segurança dw `noAuthNoPriv` e `authNoPriv`, excluimos a tabela `hrSWRun` (1.3.6.1.2.1.25.4) dos relatórios SNMP resultantes. Incluímos esta tabela para o caso de você estar usando o nível de segurança `authPriv`. Para obter mais informações, consulte a "[Documentação de referência do OID](https://oidref.com/1.3.6.1.2.1.25.4)". Com o SNMP v2c, ficam disponíveis somente as informações em nível de hardware. Os aplicativos e serviços no {% data variables.product.prodname_enterprise %} não têm OIDs configurados para reportar métricas. Diversas MIBs estão disponíveis, o que pode ser visto ao executar `snmpwalk` em uma estação de trabalho à parte com suporte SNMP na rede: diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index 0c7a487e9e..2e9b94782e 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -32,7 +32,7 @@ Este guia mostra como aplicar uma abordagem de gerenciamento centralizada para o 1. Implantar um executor auto-hospedado para a sua empresa 1. Criar um grupo para gerenciar o acesso aos executores disponíveis para sua empresa 1. Opcionalmente, restringir ainda mais os repositórios que podem usar o executor -{%- ifversion ghec or ghae-issue-4462 or ghes > 3.2 %} +{%- ifversion ghec or ghae or ghes > 3.2 %} 1. Opcionalmente, crie ferramentas personalizadas para dimensionar automaticamente seus executores auto-hospedados {% endif %} @@ -122,7 +122,7 @@ Opcionalmente, os proprietários da organização podem restringir ainda mais a Para obter mais informações, consulte "[Gerenciando acesso a runners auto-hospedados usando grupos](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)". -{% ifversion ghec or ghae-issue-4462 or ghes > 3.2 %} +{% ifversion ghec or ghae or ghes > 3.2 %} ## 5. Dimensione automaticamente seus executores auto-hospedados diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index b75787043a..d2f5819344 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -45,7 +45,7 @@ Antes de permitir o acesso a todas as ações de {% data variables.product.prodn 1. Em "Os usuários podem usar as ações do GitHub.com em execuções do fluxo de trabalho", use o menu suspenso e selecione **Habilitado**. ![Menu suspenso para ações do GitHub.com em execuções do fluxos de trabalho](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) 1. {% data reusables.actions.enterprise-limit-actions-use %} -{% ifversion ghes > 3.2 or ghae-issue-4815 %} +{% ifversion ghes > 3.2 or ghae %} ## Retirada automática de namespaces para ações acessadas em {% data variables.product.prodname_dotcom_the_website %} diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md index 33c62dce8f..e81e29dffa 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md @@ -33,7 +33,7 @@ Se sua máquina tiver acesso aos dois sistemas ao mesmo tempo, você poderá faz A ferramenta `actions-sync` só pode fazer download de ações de {% data variables.product.prodname_dotcom_the_website %} armazenadas em repositórios públicos. -{% ifversion ghes > 3.2 or ghae-issue-4815 %} +{% ifversion ghes > 3.2 or ghae %} {% note %} **Observação:** A ferramenta `actions-sync` destina-se a ser usada em sistemas em que {% data variables.product.prodname_github_connect %} não está habilitado. Se você executar a ferramenta em um sistema com {% data variables.product.prodname_github_connect %} habilitado, você poderá ver o erro `O repositório foi desativado e não pode ser reutilizado`. Isso indica que um fluxo de trabalho usou essa ação diretamente em {% data variables.product.prodname_dotcom_the_website %} e o namespace está desativado em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Desativação automática de namespaces para ações acessadas em {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)". diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index 4af65033cb..7845586e73 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -42,7 +42,7 @@ Uma vez configurado {% data variables.product.prodname_github_connect %}, você 1. Configure o YAML do seu fluxo de trabalho para usar `{% data reusables.actions.action-checkout %}`. 1. Cada vez que o seu fluxo de trabalho é executado, o executor usará a versão especificada `ações/checkout` de {% data variables.product.prodname_dotcom_the_website %}. - {% ifversion ghes > 3.2 or ghae-issue-4815 %} + {% ifversion ghes > 3.2 or ghae %} {% note %} **Nota:** A primeira vez que a ação `checkout` é usada a partir de {% data variables.product.prodname_dotcom_the_website %}, o namespace `actions/check-` é automaticamente desativado em {% data variables.product.product_location %}. Se você quiser reverter para uma cópia local da ação, primeiro você precisará remover o namespace da desativação. Para obter mais informações, consulte "[Desativação automática de namespaces para ações acessadas em {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)". diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md index 0b98549583..b99c55dcbc 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md @@ -80,7 +80,7 @@ Os seguintes atributos o SAML estão disponíveis para {% data variables.product | `NameID` | Sim | Identificador de usuário persistente. Qualquer formato de identificador de nome persistente pode ser usado. {% ifversion ghec %}Se você usa uma empresa com {% data variables.product.prodname_emus %}, {% endif %}{% data variables.product.product_name %} irá normalizar o elemento `NameID` para usar como um nome de usuário, a menos que seja fornecida uma das declarações alternativas. Para obter mais informações, consulte "[Considerações de nome de usuário para autenticação externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)". | | `SessionNotOnOrAfter` | Não | A data que {% data variables.product.product_name %} invalida a sessão associada. Após a invalidação, a pessoa deve efetuar a autenticação novamente para acessar {% ifversion ghec or ghae %}os recursos da sua empresa{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. Para obter mais informações, consulte "[Duração da sessão e fim do tempo](#session-duration-and-timeout)". | {%- ifversion ghes or ghae %} -| `administrator` | No | When the value is `true`, {% data variables.product.product_name %} will automatically promote the user to be a {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %}. Any other value or a non-existent value will demote the account and remove administrative access. | | `username` | No | The username for {% data variables.product.product_location %}. | +| `administrator` | No | When the value is `true`, {% data variables.product.product_name %} will automatically promote the user to be a {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %}. Qualquer outro valor ou um valor inexistente irá rebaixar a conta e remover o acesso administrativo. | | `username` | Não | O nome de usuário para {% data variables.product.product_location %}. | {%- endif %} | `full_name` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} full name of the user to display on the user's profile page. | | `emails` | No | The email addresses for the user.{% ifversion ghes or ghae %} You can specify more than one address.{% endif %}{% ifversion ghec or ghes %} If you sync license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_github_connect %} uses `emails` to identify unique users across products. For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %} | | `public_keys` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} public SSH keys for the user. You can specify more than one key. | | `gpg_keys` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} GPG keys for the user. You can specify more than one key. | @@ -93,20 +93,20 @@ Para especificar mais de um valor para um atributo, use múltiplos elementos de ``` -## SAML response requirements +## Requisitos de resposta do SAML -{% data variables.product.product_name %} requires that the response message from your IdP fulfill the following requirements. +{% data variables.product.product_name %} exige que a mensagem de resposta do seu IdP atenda aos seguintes requisitos. -- Your IdP must provide the `` element on the root response document and match the ACS URL only when the root response document is signed. If your IdP signs the assertion, {% data variables.product.product_name %} will ignore the assertion. -- Your IdP must always provide the `` element as part of the `` element. The value must match your `EntityId` for {% data variables.product.product_name %}.{% ifversion ghes or ghae %} This value is the URL where you access {% data variables.product.product_location %}, such as {% ifversion ghes %}`http(s)://HOSTNAME`{% elsif ghae %}`https://SUBDOMAIN.githubenterprise.com`, `https://SUBDOMAIN.github.us`, or `https://SUBDOMAIN.ghe.com`{% endif %}.{% endif %} +- Seu IdP deve fornecer o elemento `` no documento de resposta raiz e corresponder ao URL do ACS somente quando o documento de resposta raiz for assinado. Se seu IdP assinar a declaração, {% data variables.product.product_name %} irá ignorar a verificação. +- Seu IdP deve sempre fornecer o elemento `` como parte do elemento ``. O valor deve corresponder ao seu `EntityId` para {% data variables.product.product_name %}.{% ifversion ghes or ghae %} Este valor é o URL onde você pode acessar {% data variables.product.product_location %}, such as {% ifversion ghes %}`http(s)://HOSTNAME`{% elsif ghae %}`https://SUBDOMAIN.githubenterprise.com`, `https://SUBDOMAIN.github.us` ou `https://SUBDOMAIN.ghe.com`{% endif %}.{% endif %} {%- ifversion ghec %} - - If you configure SAML for an organization, this value is `https://github.com/orgs/ORGANIZATION`. - - If you configure SAML for an enterprise, this URL is `https://github.com/enterprises/ENTERPRISE`. + - Se você configurar o SAML para uma organização, este valor será `https://github.com/orgs/ORGANIZAÇÃO`. + - Se você configurar o SAML para uma empresa, essa URL será `https://github.com/enterprises/ENTERPRISE`. {%- endif %} -- Your IdP must protect each assertion in the response with a digital signature. You can accomplish this by signing each individual `` element or by signing the `` element. -- Your IdP must provide a `` element as part of the `` element. You may use any persistent name identifier format. -- Your IdP must include the `Recipient` attribute, which must be set to the ACS URL. The following example demonstrates the attribute. +- Seu IdP deve proteger cada declaração na resposta com uma assinatura digital. Você pode realizar isso assinando cada elemento individual `` ou assinando o `elemento`. +- Seu IdP deve fornecer um elemento `` como parte do elemento ``. Você pode usar qualquer formato de identificador de nome persistente. +- Seu IdP deve incluir o atributo `Destinatário`, que deve ser definido como o URL do ACS. O exemplo a seguir demonstra o atributo. ```xml @@ -126,17 +126,17 @@ Para especificar mais de um valor para um atributo, use múltiplos elementos de ``` -## Session duration and timeout +## Duração da sessão e tempo limite -To prevent a person from authenticating with your IdP and staying authorized indefinitely, {% data variables.product.product_name %} periodically invalidates the session for each user account with access to {% ifversion ghec or ghae %}your enterprise's resources{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. After invalidation, the person must authenticate with your IdP once again. By default, if your IdP does not assert a value for the `SessionNotOnOrAfter` attribute, {% data variables.product.product_name %} invalidates a session {% ifversion ghec %}24 hours{% elsif ghes or ghae %}one week{% endif %} after successful authentication with your IdP. +Para impedir que uma pessoa efetue a autenticação com o seu IdP e permaneça indefinidamente autorizada, {% data variables.product.product_name %} invalida periodicamente a sessão para cada conta de usuário com acesso aos {% ifversion ghec or ghae %} recursos da sua empresa{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. Depois da invalidação, a pessoa deverá efetuar a autenticação com seu IdP novamente. By default, if your IdP does not assert a value for the `SessionNotOnOrAfter` attribute, {% data variables.product.product_name %} invalidates a session {% ifversion ghec %}24 hours{% elsif ghes or ghae %}one week{% endif %} after successful authentication with your IdP. -To customize the session duration, you may be able to define the value of the `SessionNotOnOrAfter` attribute on your IdP. If you define a value less than 24 hours, {% data variables.product.product_name %} may prompt people to authenticate every time {% data variables.product.product_name %} initiates a redirect. +Para personalizar a duração da sessão, talvez você possa definir o valor do atributo `SessionNotOnOrAfter` no seu IdP. Se você definir um valor em menos de 24 horas, {% data variables.product.product_name %} poderá solicitar a autenticação das pessoas toda vez que {% data variables.product.product_name %} iniciar um redirecionamento. {% note %} **Atenção**: -- For Azure AD, the configurable lifetime policy for SAML tokens does not control session timeout for {% data variables.product.product_name %}. -- Okta does not currently send the `SessionNotOnOrAfter` attribute during SAML authentication with {% data variables.product.product_name %}. For more information, contact Okta. +- Para Azure AD, a política de tempo de vida configurável para tokens do SAML não controla o tempo limite de sessão para {% data variables.product.product_name %}. +- O Okta não envia atualmente o atributo `SessionNotOnOrAfter` durante a autenticação do SAML com {% data variables.product.product_name %}. Para mais informações, entre em contato com Okta. {% endnote %} diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md index d4a3a22db3..3a5d6fd196 100644 --- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md +++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md @@ -1,6 +1,6 @@ --- title: Instalar o GitHub Enterprise Server no Azure -intro: 'To install {% data variables.product.prodname_ghe_server %} on Azure, you must deploy onto a memory-optimized instance that supports premium storage.' +intro: 'Para instalar {% data variables.product.prodname_ghe_server %} no Azure, você deve implantar em uma instância otimizada para memória que seja compatível com o armazenamento premium.' redirect_from: - /enterprise/admin/guides/installation/installing-github-enterprise-on-azure - /enterprise/admin/installation/installing-github-enterprise-server-on-azure @@ -30,7 +30,7 @@ Você pode implantar o {% data variables.product.prodname_ghe_server %} no Azure ## Determinar o tipo de máquina virtual -Antes de lançar {% data variables.product.product_location %} no Azure, você deverá determinar o tipo de máquina que melhor atende às necessidades da sua organização. For more information about memory optimized machines, see "[Memory optimized virtual machine sizes](https://docs.microsoft.com/en-gb/azure/virtual-machines/sizes-memory)" in the Microsoft Azure documentation. To review the minimum resource requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)." +Antes de lançar {% data variables.product.product_location %} no Azure, você deverá determinar o tipo de máquina que melhor atende às necessidades da sua organização. Para obter mais informações sobre máquinas otimizadas de memória, consulte "[Tamanhos otimizados de memória para máquinas virtuais](https://docs.microsoft.com/en-gb/azure/virtual-machines/sizes-memory)" na documentação do Microsoft Azure. Para revisar os requisitos mínimos de recursos para {% data variables.product.product_name %}, consulte "[Requisitos Mínimos](#minimum-requirements)". {% data reusables.enterprise_installation.warning-on-scaling %} diff --git a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index 1b03ab39a0..70770a1481 100644 --- a/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -188,7 +188,7 @@ topics: | `config_entry.update` | A definição de uma configuração foi editada. Esses eventos só são visíveis no log de auditoria do administrador do site. O tipo de eventos registrados relaciona-se a:
- Configurações e políticas corporativas
- Permissões da organização e do repositório
- Git, LFS do Git, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, projeto, e configurações de segurança do código. | {%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} ### ações de categoria de `dependabot_alerts` | Ação | Descrição | @@ -226,7 +226,7 @@ topics: | `dependabot_security_updates_new_repos.enable` | O proprietário de uma empresa {% ifversion ghes %} ou administrador do site{% endif %} habilitou {% data variables.product.prodname_dependabot_security_updates %} para todos os novos repositórios. | {%- endif %} -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} ### ações de categoria de `dependency_graph` | Ação | Descrição | @@ -620,69 +620,69 @@ topics: {%- ifversion fpt or ghec %} | `org.oauth_app_access_approved` | Um proprietário [concedeu acesso da organização a um {% data variables.product.prodname_oauth_app %}](/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization). | `org.oauth_app_access_denied` | Um proprietário [desabilitou o acesso de {% data variables.product.prodname_oauth_app %} a uma organização previamente aprovada.](/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization) | `org.oauth_app_access_requested` | Um integrante da organização solicitou que um proprietário conceda acesso de {% data variables.product.prodname_oauth_app %} a uma organização. {%- endif %} -| `org.recreate` | Uma organização foi restaurada. | `org.register_self_hosted_runner` | Um novo executor auto-hospedado foi registrado. Para obter mais informações, consulte "[Adicionar um executor auto-hospedado a uma organização](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". | `org.remove_actions_secret` | Um segredo de {% data variables.product.prodname_actions %} foi removido. | `org.remove_integration_secret` | Um segredo de integração de {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} ou de {% data variables.product.prodname_codespaces %}{% endif %} foi removido de uma organização. | `org.remove_billing_manager` | Um proprietário removeu um gerente de cobrança de uma organização. |{% ifversion fpt or ghec %}For more information, see "[Removing a billing manager from your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization)"{% endif %}{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and a billing manager didn't use 2FA or disabled 2FA.{% endif %}| | `org.remove_member` | An [owner removed a member from an organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disabled 2FA{% endif %}. Além disso, [um membro da organização removeu-se](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization) de uma organização. | `org.remove_outside_collaborator` | An owner removed an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an outside collaborator didn't use 2FA or disabled 2FA{% endif %}. | `org.remove_self_hosted_runner` | Um executor auto-hospedado foi removido. Para obter mais informações, consulte "[Remover um executor de uma organização](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)." | `org.rename` | Uma organização foi renomeada. | `org.restore_member` | O membro e uma organização foi restaurado. Para obter mais informações, consulte "[Restabelecer ex-integrantes da organização](/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization)". +| `org.recreate` | Uma organização foi restaurada. | `org.register_self_hosted_runner` | Um novo executor auto-hospedado foi registrado. Para obter mais informações, consulte "[Adicionar um executor auto-hospedado a uma organização](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)". | `org.remove_actions_secret` | Um segredo de {% data variables.product.prodname_actions %} foi removido. | `org.remove_integration_secret` | Um segredo de integração de {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} ou de {% data variables.product.prodname_codespaces %}{% endif %} foi removido de uma organização. | `org.remove_billing_manager` | Um proprietário removeu um gerente de cobrança de uma organização. |{% ifversion fpt or ghec %}For more information, see "[Removendo um gerente de cobrança da sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization)"{% endif %}{% ifversion not ghae %} ou quando [a autenticação de dois fatores era obrigatõria em uma organização](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) e um gerente de cobrança não usou a 2FA ou desabilitou a 2FA.{% endif %}| | `org.remove_member` | Um [proprietário removeu um integrante de uma organização](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} ou quando [a autenticação de dois fatores era obrigatória em uma organização](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) e o integrante da organização não usa a 2FA ou desabilitou a 2FA{% endif %}. Além disso, [um membro da organização removeu-se](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization) de uma organização. | `org.remove_outside_collaborator` | Um proprietário removeu um colaborador externo de uma organização{% ifversion not ghae %} ou quando [autenticação de dois fatores foi exigida em uma organização](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) e um colaborador externo não usou a 2FA ou desabilitou a 2FA{% endif %}. | `org.remove_self_hosted_runner` | Um executor auto-hospedado foi removido. Para obter mais informações, consulte "[Remover um executor de uma organização](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)." | `org.rename` | Uma organização foi renomeada. | `org.restore_member` | O membro e uma organização foi restaurado. Para obter mais informações, consulte "[Restabelecer ex-integrantes da organização](/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization)". {%- ifversion ghec %} -| `org.revoke_external_identity` | An organization owner revoked a member's linked identity. Para obter mais informações, consulte "[Visualizar e gerenciar o acesso SAML de um integrante à sua organização](/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)". | `org.revoke_sso_session` | An organization owner revoked a member's SAML session. Para obter mais informações, consulte "[Visualizar e gerenciar o acesso SAML de um integrante à sua organização](/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)". +| `org.revoke_external_identity` | O proprietário de uma organização revogou a identidade vinculada de um integrante. Para obter mais informações, consulte "[Visualizar e gerenciar o acesso SAML de um integrante à sua organização](/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)". | `org.revoke_sso_session` | O proprietário de uma organização revogou a sessão do SAML de um integrante. Para obter mais informações, consulte "[Visualizar e gerenciar o acesso SAML de um integrante à sua organização](/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 %} -| `org.runner_group_created` | A self-hosted runner group was created. Para obter mais informações, consulte "[Criar um grupo de executores auto-hospedados para uma organização](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)". | `org.runner_group_removed` | A self-hosted runner group was removed. Para obter mais informações, consulte "[Remover um grupo de executores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)". +| `org.runner_group_created` | Um grupo de executores auto-hospedado foi criado. Para obter mais informações, consulte "[Criar um grupo de executores auto-hospedados para uma organização](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)". | `org.runner_group_removed` | Um grupo de executores auto-hospedado foi removido. Para obter mais informações, consulte "[Remover um grupo de executores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)". {%- ifversion fpt or ghec %} -| `org.runner_group_renamed` | A self-hosted runner group was renamed. Para obter mais informações, consulte "[Alterar a política de acesso de um grupo de executores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)". +| `org.runner_group_renamed` | Um grupo de executores auto-hospedado foi renomeado. Para obter mais informações, consulte "[Alterar a política de acesso de um grupo de executores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)". {%- endif %} -| `org.runner_group_updated` | The configuration of a self-hosted runner group was changed. Para obter mais informações, consulte "[Alterar a política de acesso de um grupo de executores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)". | `org.runner_group_runner_removed` | The REST API was used to remove a self-hosted runner from a group. Para obter mais informações, consulte "[Remover um executor auto-hospedado de um grupo para uma organização](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)". | `org.runner_group_runners_added` | A self-hosted runner was added to a group. Para obter mais informações, consulte [Transferir um executor auto-hospedado para um grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | `org.runner_group_runners_updated`| A runner group's list of members was updated. Para obter mais informações, consulte "[Definir executores auto-hospedados em um grupo para uma organização](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". +| `org.runner_group_updated` | A configuração de um grupo de executores auto-hospedado foi alterada. Para obter mais informações, consulte "[Alterar a política de acesso de um grupo de executores auto-hospedados](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)". | `org.runner_group_runner_removed` | A API REST foi usada para remover um executor auto-hospedado de um grupo. Para obter mais informações, consulte "[Remover um executor auto-hospedado de um grupo para uma organização](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)". | `org.runner_group_runners_added` | Um executor auto-hospedado foi adicionado a um grupo. Para obter mais informações, consulte [Transferir um executor auto-hospedado para um grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). | `org.runner_group_runners_updated` | A lista de um grupo de executores foi atualizada. Para obter mais informações, consulte "[Definir executores auto-hospedados em um grupo para uma organização](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". {%- ifversion fpt or ghec %} -| `org.runner_group_visiblity_updated` | The visibility of a self-hosted runner group was updated via the REST API. Para obter mais informações, consulte "[Atualize um grupo de executores auto-hospedados para uma organização](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)". +| `org.runner_group_visiblity_updated` | A visibilidade de um grupo de executores auto-hospedados de foi atualizada por meio da API REST. Para obter mais informações, consulte "[Atualize um grupo de executores auto-hospedados para uma organização](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)". {%- endif %} {%- if secret-scanning-audit-log-custom-patterns %} -| `org.secret_scanning_push_protection_disable` | An organization owner or administrator disabled push protection for secret scanning. Para obter mais informações, consulte "[Protegendo pushes com digitalização de segredo](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". | `org.secret_scanning_push_protection_enable` | An organization owner or administrator enabled push protection for secret scanning. +| `org.secret_scanning_push_protection_disable` | O proprietário ou administrador de uma organização desabilitou a proteção de push para a digitalização de segredo. Para obter mais informações, consulte "[Protegendo pushes com digitalização de segredo](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". | `org.secret_scanning_push_protection_enable` | O proprietário ou administrador de uma organização habilitou a proteção de push para a digitalização de segredo. {%- endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} -| `org.self_hosted_runner_online` | The runner application was started. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)". | `org.self_hosted_runner_offline` | The runner application was stopped. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)". +| `org.self_hosted_runner_online` | O aplicativo do executor foi iniciado. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)". | `org.self_hosted_runner_offline` | O aplicativo do executor foi interrompido. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)". {%- endif %} {%- ifversion fpt or ghec or ghes %} -| `org.self_hosted_runner_updated` | The runner application was updated. Pode ser visto usando a API REST e a interface do usuário; não visível na exportação de JSON/CSV. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." +| `org.self_hosted_runner_updated` | O aplicativo do executor foi atualizado. Pode ser visto usando a API REST e a interface do usuário; não visível na exportação de JSON/CSV. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." {%- endif %} {%- ifversion fpt or ghec %} -| `org.set_actions_fork_pr_approvals_policy` | The setting for requiring approvals for workflows from public forks was changed for an organization. For more information, see "[Requiring approval for workflows from public forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)." +| `org.set_actions_fork_pr_approvals_policy` | A configuração que exige aprovações para os fluxos de trabalho de bifurcações públicas foi alterada para uma organização. Para obter mais informações, consulte "[Exigindo aprovação para fluxos de trabalho de bifurcações públicas](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)." {%- endif %} -| `org.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs in an organization was changed. For more information, see "[Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)." +| `org.set_actions_retention_limit` | O período de retenção para artefatos e registros de {% data variables.product.prodname_actions %} em uma organização foi alterado. Para obter mais informações, consulte "[Configurar o período de retenção para artefatos e registros de {% data variables.product.prodname_actions %} na sua organização](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization). {%- ifversion fpt or ghec or ghes %} -| `org.set_fork_pr_workflows_policy` | The policy for workflows on private repository forks was changed. For more information, see "[Enabling workflows for private repository forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)." +| `org.set_fork_pr_workflows_policy` | A política para os fluxos de trabalho nas bifurcações de repositórios privados foi alterada. Para obter mais informações, consulte "[Habilitar fluxos de trabalho para bifurcações privadas do repositório](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)." {%- endif %} {%- ifversion ghes %} -| `org.sso_response` | A SAML single sign-on response was generated when a member attempted to authenticate with an organization. +| `org.sso_response` | Uma resposta de logon único do SAML foi gerada quando um integrante tentou efetuar a autenticação com uma organização. {%- endif %} {%- ifversion not ghae %} -| `org.transform` | A user account was converted into an organization. For more information, see "[Converting a user into an organization](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)." +| `org.transform` | Uma conta de usuário foi convertida em uma organização. Para obter mais informações, consulte "[Converter um usuário em uma organização](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)." {%- endif %} -| `org.unblock_user` | An organization owner unblocked a user from an organization. {% ifversion fpt or ghec %}For more information, see "[Unblocking a user from your organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)."{% endif %} +| `org.unblock_user` | O proprietário de uma organização desbloqueou o usuário de uma organização. {% ifversion fpt or ghec %}Para obter mais informações, consulte "[Desbloqueando um usuário da sua organização](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)."{% endif %} {%- ifversion fpt or ghec or ghes %} -| `org.update_actions_secret` | A {% data variables.product.prodname_actions %} secret was updated. +| `org.update_actions_secret` | Um segredo de {% data variables.product.prodname_actions %} foi atualizado. {%- endif %} -| `org.update_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was updated for an organization. | `org.update_default_repository_permission` | An organization owner changed the default repository permission level for organization members. | `org.update_member` | An organization owner changed a person's role from owner to member or member to owner. | `org.update_member_repository_creation_permission` | An organization owner changed the create repository permission for organization members. | `org.update_member_repository_invitation_permission` | An organization owner changed the policy setting for organization members inviting outside collaborators to repositories. Para obter mais informações, consulte "[Configurar permissões para adicionar colaboradores externos](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)". | `org.update_new_repository_default_branch_setting` | An organization owner changed the name of the default branch for new repositories in the organization. Para obter mais informações, consulte "[Gerenciar o nome do branch padrão para repositórios na sua organização](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)". +| `org.update_integration_secret` | Um segredo de integração de {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} ou de {% data variables.product.prodname_codespaces %}{% endif %} foi atualizado para uma organização. | `org.update_default_repository_permission` | O proprietário de uma organização alterou o nível de permissão padrão do repositório para os integrantes da organização. | `org.update_member` | O proprietário de uma organização mudou a função de uma pessoa de proprietário para integrante ou de integrante para proprietário. | `org.update_member_repository_creation_permission` | O proprietário de uma organização alterou a permissão de criar repositório para integrantes da organização. | `org.update_member_repository_invitation_permission` | O proprietário de uma organização alterou a configuração de política para os integrantes da organização convidando colaboradores externos para repositórios. Para obter mais informações, consulte "[Configurar permissões para adicionar colaboradores externos](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)". | `org.update_new_repository_default_branch_setting` | O proprietário de uma organização alterou o nome da branch padrão para novos repositórios na organização. Para obter mais informações, consulte "[Gerenciar o nome do branch padrão para repositórios na sua organização](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)". {%- ifversion ghec or ghae %} -| `org.update_saml_provider_settings` | An organization's SAML provider settings were updated. | `org.update_terms_of_service` | An organization changed between the Standard Terms of Service and the Corporate Terms of Service. {% ifversion ghec %}For more information, see "[Upgrading to the Corporate Terms of Service](/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service)."{% endif %} +| `org.update_saml_provider_settings` | As configurações do provedor de SAML da organização foram atualizadas. | `org.update_terms_of_service` | Uma organização alterada entre os Termos de Serviço Padrão e os Termos de Serviço Corporativos. {% ifversion ghec %}Para obter mais informações, consulte "[Atualizando para os Termos de Serviço Corporativo](/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service)."{% endif %} {%- endif %} {%- ifversion ghec or ghes or ghae %} ### ações da categoria `org_credential_authorization` -| Ação | Descrição | -| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `org_credential_authorization.deauthorized` | A member deauthorized credentials for use with SAML single sign-on. | -| {% ifversion ghec or ghae %}For more information, see "[Authenticating with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on)."{% endif %} | | -| `org_credential_authorization.grant` | A member authorized credentials for use with SAML single sign-on. | -| {% ifversion ghec or ghae %}For more information, see "[Authenticating with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on)."{% endif %} | | -| `org_credential_authorization.revoke` | An owner revoked authorized credentials. {% ifversion ghec %}For more information, see "[Viewing and managing your active SAML sessions](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)."{% endif %} +| Ação | Descrição | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `org_credential_authorization.deauthorized` | Um membro cancelou a autorização das credenciais para uso com o logon único SAML. | +| {% ifversion ghec or ghae %}Para obter mais informações, consulte "[Efetuando a autenticação com o logon único SAML](/authentication/authenticating-with-saml-single-sign-on)".{% endif %} | | +| `org_credential_authorization.grant` | Um integrante autorizou credenciais para uso com o logon único SAML. | +| {% ifversion ghec or ghae %}Para obter mais informações, consulte "[Efetuando a autenticação com o logon único SAML](/authentication/authenticating-with-saml-single-sign-on)".{% endif %} | | +| `org_credential_authorization.revoke` | Um proprietário revogou as credenciais autorizadas. {% ifversion ghec %}Para obter mais informações, consulte "[Visualizando e gerenciando suas sessões de SAML ativas](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)".{% endif %} {%- endif %} {%- if secret-scanning-audit-log-custom-patterns %} ### Ações da categoria `org_secret_scanning_custom_pattern` -| Ação | Descrição | -| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `org_secret_scanning_custom_pattern.create` | A custom pattern is published for secret scanning in an organization. Para obter mais informações, consulte "[Definindo padrões personalizados para digitalização de segredo](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-organization). " | -| `org_secret_scanning_custom_pattern.delete` | A custom pattern is removed from secret scanning in an organization. Para obter mais informações, consulte "[Definindo padrões personalizados para digitalização de segredo](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern). " | -| `org_secret_scanning_custom_pattern.update` | As alterações em um padrão personalizado são salvas para a digitalização de segredo em uma organização. Para obter mais informações, consulte "[Definindo padrões personalizados para digitalização de segredo](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern). " | +| Ação | Descrição | +| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `org_secret_scanning_custom_pattern.create` | Um padrão personalizado foi publicado para a digitalização de segredo em uma organização. Para obter mais informações, consulte "[Definindo padrões personalizados para digitalização de segredo](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-organization). " | +| `org_secret_scanning_custom_pattern.delete` | Um padrão personalizado foi removido da digitalização de segredo em uma organização. Para obter mais informações, consulte "[Definindo padrões personalizados para digitalização de segredo](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern). " | +| `org_secret_scanning_custom_pattern.update` | As alterações em um padrão personalizado são salvas para a digitalização de segredo em uma organização. Para obter mais informações, consulte "[Definindo padrões personalizados para digitalização de segredo](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern). " | {%- endif %} ### Ações da categoria `organization_default_label` @@ -727,56 +727,56 @@ topics: | `packages.part_upload` | Uma versão específica de pacote foi parcialmente enviada para uma organização. | | `packages.upstream_package_fetched` | Uma versão específica de pacote foi obtida a partir proxy upstream do npm. | | `packages.version_download` | Uma versão específica do pacote foi baixada. | -| `packages.version_upload` | A specific package version was uploaded. | +| `packages.version_upload` | Foi feito o upload da versão de um pacote específico. | {%- endif %} {%- ifversion fpt or ghec %} -### `pages_protected_domain` category actions +### Ações da categoria `pages_protected_domain` -| Ação | Descrição | -| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `pages_protected_domain.create` | A {% data variables.product.prodname_pages %} verified domain was created for an organization or enterprise. Para obter mais informações, consulte "[Verificando o seu domínio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)." | -| `pages_protected_domain.delete` | A {% data variables.product.prodname_pages %} verified domain was deleted from an organization or enterprise. Para obter mais informações, consulte "[Verificando o seu domínio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)." | -| `pages_protected_domain.verify` | A {% data variables.product.prodname_pages %} domain was verified for an organization or enterprise. Para obter mais informações, consulte "[Verificando o seu domínio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)." | +| Ação | Descrição | +| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `pages_protected_domain.create` | Um domínio verificado de {% data variables.product.prodname_pages %} foi criado para uma organização ou empresa. Para obter mais informações, consulte "[Verificando o seu domínio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)." | +| `pages_protected_domain.delete` | Um domínio verificado de {% data variables.product.prodname_pages %} foi excluído para uma organização ou empresa. Para obter mais informações, consulte "[Verificando o seu domínio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)." | +| `pages_protected_domain.verify` | Um domínio verificado de {% data variables.product.prodname_pages %} foi verificado para uma organização ou empresa. Para obter mais informações, consulte "[Verificando o seu domínio personalizado para {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)." | ### ações de categoria `payment_method` -| Ação | Descrição | -| ----------------------- | ---------------------------------------------------------------------------- | -| `payment_method.create` | A new payment method was added, such as a new credit card or PayPal account. | -| `payment_method.remove` | A payment method was removed. | -| `payment_method.update` | An existing payment method was updated. | +| Ação | Descrição | +| ----------------------- | ----------------------------------------------------------------------------------------------- | +| `payment_method.create` | Um novo método de pagamento foi adicionado, como uma nova conta de cartão de crédito ou PayPal. | +| `payment_method.remove` | Um método de pagamento foi removido. | +| `payment_method.update` | Um método de pagamento existente foi atualizado. | -### `prebuild_configuration` category actions +### Ações da categoria `prebuild_configuration` -| Ação | Descrição | -| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `prebuild_configuration.create` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was created. Para obter mais informações, consulte[Sobre as pré-criações de codespaces](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)". | -| `prebuild_configuration.destroy` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was deleted. Para obter mais informações, consulte[Sobre as pré-criações de codespaces](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)". | -| `prebuild_configuration.run_triggered` | A user initiated a run of a {% data variables.product.prodname_codespaces %} prebuild configuration for a repository branch. Para obter mais informações, consulte[Sobre as pré-criações de codespaces](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)". | -| `prebuild_configuration.update` | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was edited. Para obter mais informações, consulte[Sobre as pré-criações de codespaces](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)". | +| Ação | Descrição | +| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `prebuild_configuration.create` | Uma configuração de pré-compilação de {% data variables.product.prodname_codespaces %} para um repositório foi criada. Para obter mais informações, consulte[Sobre as pré-criações de codespaces](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)". | +| `prebuild_configuration.destroy` | Uma configuração de pré-compilação de {% data variables.product.prodname_codespaces %} para um repositório foi excluída. Para obter mais informações, consulte[Sobre as pré-criações de codespaces](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)". | +| `prebuild_configuration.run_triggered` | Um usuário iniciou uma execução de uma configuração de pré-compilação de {% data variables.product.prodname_codespaces %} para o branch de um repositório. Para obter mais informações, consulte[Sobre as pré-criações de codespaces](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)". | +| `prebuild_configuration.update` | Uma configuração de pré-compilação de {% data variables.product.prodname_codespaces %} para um repositório foi editada. Para obter mais informações, consulte[Sobre as pré-criações de codespaces](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)". | {%- endif %} {%- ifversion ghes %} -### `pre_receive_environment` category actions +### Ações da categoria `pre_receive_environment` -| Ação | Descrição | -| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `pre_receive_environment.create` | A pre-receive hook environment was created. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." | -| `pre_receive_environment.destroy` | A pre-receive hook environment was deleted. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." | -| `pre_receive_environment.download` | A pre-receive hook environment was downloaded. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." | -| `pre_receive_environment.update` | A pre-receive hook environment was updated. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." | +| Ação | Descrição | +| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `pre_receive_environment.create` | Um ambiente de hook de pre-receive foi criado. Para obter mais informações, consulte[Criando um ambiente de hook pre-receive](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)". | +| `pre_receive_environment.destroy` | Um ambiente de hook de pre-receive foi excluído. Para obter mais informações, consulte[Criando um ambiente de hook pre-receive](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)". | +| `pre_receive_environment.download` | Um ambiente de hook de pre-receive foi baixado. Para obter mais informações, consulte[Criando um ambiente de hook pre-receive](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)". | +| `pre_receive_environment.update` | Um ambiente de hook de pre-receive foi atualizado. Para obter mais informações, consulte[Criando um ambiente de hook pre-receive](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)". | -### `pre_receive_hook` category actions +### Ações da categoria `pre_receive_hook` -| Ação | Descrição | -| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `pre_receive_hook.create` | A pre-receive hook was created. For more information, see "[Creating pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#creating-pre-receive-hooks)." | -| `pre_receive_hook.destroy` | A pre-receive hook was deleted. For more information, see "[Deleting pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#deleting-pre-receive-hooks)." | -| `pre_receive_hook.enforcement` | A pre-receive hook enforcement setting allowing repository and organization administrators to override the hook configuration was enabled or disabled. For more information, see "[Managing pre-receive hooks on the GitHub Enterprise Server appliance](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance)." | -| `pre_receive_hook.rejected_push` | A pre-receive hook rejected a push. | -| `pre_receive_hook.update` | A pre-receive hook was created. For more information, see "[Editing pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#editing-pre-receive-hooks)." | -| `pre_receive_hook.warned_push` | A pre-receive hook warned about a push. | +| Ação | Descrição | +| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `pre_receive_hook.create` | Um hook de pre-receive foi criado. Para obter mais informações, consulte "format@@0[Criando hooks pre-receive](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#creating-pre-receive-hooks)". | +| `pre_receive_hook.destroy` | Um hook de pre-receive foi excluído. Para obter mais informações, consulte "format@@0[Excluindo hooks pre-receive](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#deleting-pre-receive-hooks)". | +| `pre_receive_hook.enforcement` | Uma configuração de aplicação de hook pre-receive que permite que os administradores da organização e do repositório substituam a configuração de hook foi habilitada ou desabilitada. Para obter mais informações, consulte "["Gerenciando hooks de pre-receive no dispositivo do GitHub Enterprise Server](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance)". | +| `pre_receive_hook.rejected_push` | Um hook pre-receive rejeitou um push. | +| `pre_receive_hook.update` | Um hook de pre-receive foi criado. Para obter mais informações, consulte "format@@0[Editando hooks pre-receive](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#editing-pre-receive-hooks)". | +| `pre_receive_hook.warned_push` | Um hook pre-receive avisou sobre um push. | {%- endif %} ### Ações da categoria `private_repository_forking` @@ -821,25 +821,25 @@ topics: ### Ações da categoria `project_view` -| Ação | Descrição | -| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `project_view.create` | A view was created in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#creating-a-project-view)." | -| `project_view.delete` | A view was deleted in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#deleting-a-saved-view)." | +| Ação | Descrição | +| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `project_view.create` | Uma visualização foi criada em um quadro de projeto. Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#creating-a-project-view)". | +| `project_view.delete` | Uma visualização foi excluída em um quadro de projeto. Para obter mais informações, consulte "[Personalizar as visualizações do seu projeto (beta)](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#deleting-a-saved-view)". | {%- endif %} ### ações da categoria `protected_branch` | Ação | Descrição | | ---------------------------------------- | ---------------------------------------------------------------------- | -| `protected_branch.create` | Branch protection was enabled on a branch. | -| `protected_branch.destroy` | Branch protection was disabled on a branch. | +| `protected_branch.create` | A proteção de branch foi habilitada em um branch. | +| `protected_branch.destroy` | A proteção de branch foi desabilitada em um branch. | | `protected_branch.dismiss_stale_reviews` | Enforcement of dismissing stale pull requests was updated on a branch. | {%- ifversion ghes %} -| `protected_branch.dismissal_restricted_users_teams` | Enforcement of restricting users and/or teams who can dismiss reviews was updated on a branch. +| `protected_branch.dismissal_restricted_users_teams` | A exigência de restrição de usuários e/ou equipes que podem ignorar avaliações foi atualizada em um branch. {%- endif %} -| `protected_branch.policy_override` | A branch protection requirement was overridden by a repository administrator. | `protected_branch.rejected_ref_update` | A branch update attempt was rejected. | `protected_branch.required_status_override` | The required status checks branch protection requirement was overridden by a repository administrator. | `protected_branch.review_policy_and_required_status_override` | The required reviews and required status checks branch protection requirements were overridden by a repository administrator. | `protected_branch.review_policy_override` | The required reviews branch protection requirement was overridden by a repository administrator. | `protected_branch.update_admin_enforced` | Branch protection was enforced for repository administrators. +| `protected_branch.policy_override` | Um requisito de proteção de branch foi sobrescrito pelo administrador de um repositório. | `protected_branch.rejected_ref_update` | Uma tentativa de atualização de branch foi rejeitada. | `protected_branch.required_status_override` | O status exigido verifica se o requisito de proteção do branch foi substituído pelo administrador de um repositório. | `protected_branch.review_policy_and_required_status_override` | As revisões necessárias e os requisitos de proteção de status requeridos foram ignorados pelo administrador de um repositório. | `protected_branch.review_policy_override` | O requisito de proteção da branch de revisões necessário foi substituído pelo administrador de um repositório. | `protected_branch.update_admin_enforced` | A proteção do branch foi aplicada para os administradores do repositório. {%- ifversion ghes %} -| `protected_branch.update_allow_deletions_enforcement_level` | Enforcement of allowing users with push access to delete matching branches was updated on a branch. | `protected_branch.update_allow_force_pushes_enforcement_level` | Enforcement of allowing force pushes for all users with push access was updated on a branch. | `protected_branch.update_linear_history_requirement_enforcement_level` | Enforcement of requiring linear commit history was updated on a branch. +| `protected_branch.update_allow_deletions_enforcement_level` | A exigência de permitir aos usuários com acesso de push para excluir branches correspondentes foi atualizada em um branch. | `protected_branch.update_allow_force_pushes_enforcement_level` | A exigência da permissão de push forçado para todos os usuários com acesso de push foi atualizada em um branch. | `protected_branch.update_linear_history_requirement_enforcement_level` | Enforcement of requiring linear commit history was updated on a branch. {%- endif %} | `protected_branch.update_pull_request_reviews_enforcement_level` | Enforcement of required pull request reviews was updated on a branch. Pode ser `0`(desativado), `1`(não administrador), `2`(todos). | `protected_branch.update_require_code_owner_review` | Enforcement of required code owner review was updated on a branch. | `protected_branch.update_required_approving_review_count` | Enforcement of the required number of approvals before merging was updated on a branch. | `protected_branch.update_required_status_checks_enforcement_level` | Enforcement of required status checks was updated on a branch. | `protected_branch.update_signature_requirement_enforcement_level` | Enforcement of required commit signing was updated on a branch. | `protected_branch.update_strict_required_status_checks_policy` | Enforcement of required status checks was updated on a branch. | `protected_branch.update_name` | A branch name pattern was updated for a branch. @@ -862,7 +862,7 @@ topics: | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `pull_request.close` | A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)." | | `pull_request.converted_to_draft` | A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)." | -| `pull_request.create` | A pull request was created. For more information, see "[Creating a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." | +| `pull_request.create` | A pull request was created. Para obter mais informações, consulte "[Criar uma pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)." | | `pull_request.create_review_request` | A review was requested on a pull request. Para obter mais informações, consulte "[Sobre merges do pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)". | | `pull_request.in_progress` | A pull request was marked as in progress. | | `pull_request.indirect_merge` | Um pull request foi considerado como merge aplicado porque os commits do pull request foram mesclados no branch de destino. | @@ -918,15 +918,15 @@ topics: {%- ifversion ghes %} | `repo.disk_archive` | A repository was archived on disk. Para obter mais informações, consulte "[Arquivando repositórios](/repositories/archiving-a-github-repository/archiving-repositories)". {%- endif %} -| `repo.download_zip` | A source code archive of a repository was downloaded as a ZIP file. | `repo.pages_cname` | A {% data variables.product.prodname_pages %} custom domain was modified in a repository. | `repo.pages_create` | A {% data variables.product.prodname_pages %} site was created. | `repo.pages_destroy` | A {% data variables.product.prodname_pages %} site was deleted. | `repo.pages_https_redirect_disabled` | HTTPS redirects were disabled for a {% data variables.product.prodname_pages %} site. | `repo.pages_https_redirect_enabled` | HTTPS redirects were enabled for a {% data variables.product.prodname_pages %} site. | `repo.pages_source` | A {% data variables.product.prodname_pages %} source was modified. | `repo.pages_private` | A {% data variables.product.prodname_pages %} site visibility was changed to private. | `repo.pages_public` | A {% data variables.product.prodname_pages %} site visibility was changed to public. | `repo.register_self_hosted_runner` | A new self-hosted runner was registered. Para obter mais informações, consulte "[Adicionar um executor auto-hospedado a um repositório](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). ". | `repo.remove_self_hosted_runner` | A self-hosted runner was removed. Para obter mais informações, consulte "[Remover um executor de um repositório](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)". | `repo.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was deleted for a repository. | `repo.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was deleted for a repository. | `repo.remove_member` | A collaborator was removed from a repository. | `repo.remove_topic` | A topic was removed from a repository. | `repo.rename` | A repository was renamed. +| `repo.download_zip` | A source code archive of a repository was downloaded as a ZIP file. | `repo.pages_cname` | A {% data variables.product.prodname_pages %} custom domain was modified in a repository. | `repo.pages_create` | A {% data variables.product.prodname_pages %} site was created. | `repo.pages_destroy` | A {% data variables.product.prodname_pages %} site was deleted. | `repo.pages_https_redirect_disabled` | HTTPS redirects were disabled for a {% data variables.product.prodname_pages %} site. | `repo.pages_https_redirect_enabled` | HTTPS redirects were enabled for a {% data variables.product.prodname_pages %} site. | `repo.pages_source` | Uma fonte de {% data variables.product.prodname_pages %} foi modificada. | `repo.pages_private` | Um site de {% data variables.product.prodname_pages %} foi alterado para privado. | `repo.pages_public` | Um site de {% data variables.product.prodname_pages %} foi alterado para público. | `repo.register_self_hosted_runner` | Um novo executor auto-hospedado foi registrado. Para obter mais informações, consulte "[Adicionar um executor auto-hospedado a um repositório](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). ". | `repo.remove_self_hosted_runner` | Um executor auto-hospedado foi removido. Para obter mais informações, consulte "[Remover um executor de um repositório](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)". | `repo.remove_actions_secret` | Um segredo de {% data variables.product.prodname_actions %} excluído de um repositório. | `repo.remove_integration_secret` | Um segredo de integração de {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} ou {% data variables.product.prodname_codespaces %}{% endif %} foi excluído de um repositório. | `repo.remove_member` | Um colaborador foi removido de um repositório. | `repo.remove_topic` | A topic was removed from a repository. | `repo.rename` | A repository was renamed. {%- ifversion fpt or ghec %} | `repo.set_actions_fork_pr_approvals_policy` | The setting for requiring approvals for workflows from public forks was changed for a repository. For more information, see "[Configuring required approval for workflows from public forks](/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 %} | `repo.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs in a repository was changed. Para obter mais informações, consulte "[Configurar o período de retenção para artefatos e registros de {% data variables.product.prodname_actions %} no seu repositório](/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 ghec or ghes > 3.1 or ghae %} -| `repo.self_hosted_runner_online` | The runner application was started. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)". | `repo.self_hosted_runner_offline` | The runner application was stopped. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)". | `repo.self_hosted_runner_updated` | The runner application was updated. Pode ser visto usando a API REST e a interface do usuário; não visível na exportação de JSON/CSV. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." +| `repo.self_hosted_runner_online` | O aplicativo do executor foi iniciado. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)". | `repo.self_hosted_runner_offline` | O aplicativo do executor foi interrompido. Só pode ser visto usando a API REST. Não é visível na interface do usuário ou na exportação do JSON/CSV. Para obter mais informações, consulte "[Verificar o status de um executor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)". | `repo.self_hosted_runner_updated` | O aplicativo do executor foi atualizado. Pode ser visto usando a API REST e a interface do usuário; não visível na exportação de JSON/CSV. Para obter mais informações, consulte "[Sobre os executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)." {%- endif %} -| `repo.staff_unlock` | An enterprise administrator or GitHub staff (with permission from a repository administrator) temporarily unlocked the repository. | `repo.transfer` | A user accepted a request to receive a transferred repository. | `repo.transfer_outgoing` | A repository was transferred to another repository network. | `repo.transfer_start` | A user sent a request to transfer a repository to another user or organization. | `repo.unarchived` | A repository was unarchived. Para obter mais informações, consulte "[Arquivar um repositório de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)". | `repo.update_actions_settings` | A repository administrator changed {% data variables.product.prodname_actions %} policy settings for a repository. | `repo.update_actions_secret` | A {% data variables.product.prodname_actions %} secret was updated. | `repo.update_actions_access_settings` | The setting to control how a repository was used by {% data variables.product.prodname_actions %} workflows in other repositories was changed. | `repo.update_default_branch` | The default branch for a repository was changed. | `repo.update_integration_secret` | A {% data variables.product.prodname_dependabot %} or {% data variables.product.prodname_codespaces %} integration secret was updated for a repository. | `repo.update_member` | A user's permission to a repository was changed. +| `repo.staff_unlock` | An enterprise administrator or GitHub staff (with permission from a repository administrator) temporarily unlocked the repository. | `repo.transfer` | A user accepted a request to receive a transferred repository. | `repo.transfer_outgoing` | A repository was transferred to another repository network. | `repo.transfer_start` | A user sent a request to transfer a repository to another user or organization. | `repo.unarchived` | A repository was unarchived. Para obter mais informações, consulte "[Arquivar um repositório de {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)". | `repo.update_actions_settings` | A repository administrator changed {% data variables.product.prodname_actions %} policy settings for a repository. | `repo.update_actions_secret` | Um segredo de {% data variables.product.prodname_actions %} foi atualizado. | `repo.update_actions_access_settings` | The setting to control how a repository was used by {% data variables.product.prodname_actions %} workflows in other repositories was changed. | `repo.update_default_branch` | The default branch for a repository was changed. | `repo.update_integration_secret` | A {% data variables.product.prodname_dependabot %} or {% data variables.product.prodname_codespaces %} integration secret was updated for a repository. | `repo.update_member` | A user's permission to a repository was changed. {%- ifversion fpt or ghec %} ### Ações da categoria `repository_advisory` @@ -1014,7 +1014,7 @@ topics: | `repository_visibility_change.disable` | The ability for enterprise members to update a repository's visibility was disabled. Members are unable to change repository visibilities in an organization, or all organizations in an enterprise. | | `repository_visibility_change.enable` | The ability for enterprise members to update a repository's visibility was enabled. Members are able to change repository visibilities in an organization, or all organizations in an enterprise. | -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} ### ações de categoria de `repository_vulnerability_alert` | Ação | Descrição | 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 a9a340b853..99981f6a71 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 @@ -66,7 +66,7 @@ Você pode optar por desativar {% data variables.product.prodname_actions %} par 1. Em "Políticas", selecione {% data reusables.actions.policy-label-for-select-actions-workflows %} e adicione suas ações necessárias{% if actions-workflow-policy %} e fluxos de trabalho reutilizáveis{% endif %} à lista. {% if actions-workflow-policy %} ![Adicionar ações e fluxos de trabalho reutilizáveis à lista de permissões](/assets/images/help/organizations/enterprise-actions-policy-allow-list-with-workflows.png) - {%- elsif ghes or ghae-issue-5094 %} + {%- elsif ghes or ghae %} ![Adicionar ações à lista de permissões](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) {%- elsif ghae %} ![Adicionar ações à lista de permissões](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) @@ -121,35 +121,35 @@ Se uma política for habilitada para uma empresa, ela poderá ser desabilitada s {% data reusables.actions.workflow-permissions-intro %} -Você pode definir as permissões padrão para o `GITHUB_TOKEN` nas configurações para sua empresa, organizações ou repositórios. If you choose a restricted option as the default in your enterprise settings, this prevents the more permissive setting being chosen in the organization or repository settings. +Você pode definir as permissões padrão para o `GITHUB_TOKEN` nas configurações para sua empresa, organizações ou repositórios. Se você escolher uma opção restrita como padrão nas configurações da empresa, isto impedirá que a configuração mais permissiva seja escolhida nas configurações da organização ou repositório. {% data reusables.actions.workflow-permissions-modifying %} ### Configurar as permissões padrão do `GITHUB_TOKEN` {% if allow-actions-to-approve-pr-with-ent-repo %} -By default, when you create a new enterprise, `GITHUB_TOKEN` only has read access for the `contents` scope. +Por padrão, ao criar uma nova empresa, `GITHUB_TOKEN` só tem acesso de leitura para o escopo `conteúdos`. {% endif %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. +1. Em "Permissões do fluxo de trabalho", escolha se você quer o `GITHUB_TOKEN` para ter acesso de leitura e escrita para todos os escopos, ou apenas ler acesso para o escopo `conteúdo`. ![Definir permissões do GITHUB_TOKEN para esta empresa](/assets/images/help/settings/actions-workflow-permissions-enterprise{% if allow-actions-to-approve-pr-with-ent-repo %}-with-pr-approval{% endif %}.png) 1. Clique em **Salvar** para aplicar as configurações. {% if allow-actions-to-approve-pr-with-ent-repo %} -### Preventing {% data variables.product.prodname_actions %} from creating or approving pull requests +### Impedindo {% data variables.product.prodname_actions %} de criar ou aprovar pull requests {% data reusables.actions.workflow-pr-approval-permissions-intro %} -By default, when you create a new enterprise, workflows are not allowed to create or approve pull requests. +Por padrão, ao criar uma nova empresa, não se permite que os fluxos de trabalho criem ou aprovem pull requests. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. Under "Workflow permissions", use the **Allow GitHub Actions to create and approve pull requests** setting to configure whether `GITHUB_TOKEN` can create and approve pull requests. +1. Em "Fluxos de trabalho", use a configuração **Permitir que o GitHub Actions crie e aprove pull requests** para configurar se `GITHUB_TOKEN` pode criar e aprovar pull requests. ![Definir permissões do GITHUB_TOKEN para esta empresa](/assets/images/help/settings/actions-workflow-permissions-enterprise-with-pr-approval.png) 1. Clique em **Salvar** para aplicar as configurações. diff --git a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md index 546916b9fc..a23c8aecf0 100644 --- a/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md @@ -68,7 +68,15 @@ Você pode ver mais informações sobre o acesso da pessoa à sua empresa como, {% ifversion ghec %} ## Visualizando convites pendentes -Você pode ver todos os convites pendentes para se tornar administradores, integrantes ou colaboradores externos em sua empresa. É possível filtrar a lista de forma útil, por exemplo, por organização. Ou localizar uma determinada pessoa procurando pelo nome de usuário ou o nome de exibição dela. +You can see all the pending invitations to become members, administrators, or outside collaborators in your enterprise. É possível filtrar a lista de forma útil, por exemplo, por organização. Ou localizar uma determinada pessoa procurando pelo nome de usuário ou o nome de exibição dela. + +In the list of pending members, for any individual account, you can cancel all invitations to join organizations owned by your enterprise. This does not cancel any invitations for that same person to become an enterprise administrator or outside collaborator. + +{% note %} + +**Note:** If an invitation was provisioned via SCIM, you must cancel the invitation via your identity provider (IdP) instead of on {% data variables.product.prodname_dotcom %}. + +{% endnote %} Se você usar {% data variables.product.prodname_vss_ghe %}, a lista de convites pendentes incluirá todos os assinantes de {% data variables.product.prodname_vs %} que não fizeram parte de nenhuma das suas organizações em {% data variables.product.prodname_dotcom %}, mesmo que o assinante não tenha um convite pendente para participar de uma organização. Para obter mais informações sobre como fazer com que os assinantes de {% data variables.product.prodname_vs %} acessem {% data variables.product.prodname_enterprise %}, consulte "[Configurando {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)" @@ -77,7 +85,9 @@ Se você usar {% data variables.product.prodname_vss_ghe %}, a lista de convites 1. Em "Pessoas", clique em **Convites pendentes.**. ![Captura de tela da aba "Convites pendentes" na barra lateral](/assets/images/help/enterprises/pending-invitations-tab.png) +1. Optionally, to cancel all invitations for an account to join organizations owned by your enterprise, to the right of the account, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Cancel invitation**. + ![Screenshot of the "Cancel invitation" button](/assets/images/help/enterprises/cancel-enterprise-member-invitation.png) 1. Opcionalmente, para visualizar os convites pendentes para administradores corporativos ou colaboradores externos, em "Integrantes pendentes", clique em **Administradores** ou **Colaboradores externos**. ![Captura de tela das abas "Membros", "Administradores", e "Colaboradores externos"](/assets/images/help/enterprises/pending-invitations-type-tabs.png) diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index b33a479c06..017e46a867 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -28,28 +28,40 @@ Você pode acessar seus recursos em {% data variables.product.product_name %} de ## Efetuar a autenticação no seu navegador -Você pode efetuar a autenticação no {% data variables.product.product_name %} no navegador {% ifversion ghae %}usando o seu IdP. Para obter mais informações, consulte "[Sobre a autenticação com o logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."{% else %}de formas diferentes. +{% ifversion ghae %} + +Você pode efetuar a autenticação no {% data variables.product.product_name %} no navegador usando o seu IdP. Para obter mais informações, consulte "[Sobre a autenticação com logon único SAML](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)". + +{% else %} {% ifversion fpt or ghec %} -- Se você for um integrante de um {% data variables.product.prodname_emu_enterprise %}, você irá efetuar a autenticação em {% data variables.product.product_name %} no seu navegador usando seu IdP. Para obter mais informações, consulte "[Efetuando a autenticação como um usuário gerenciado](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %} - Se você não for um integrante de um {% data variables.product.prodname_emu_enterprise %}, você irá efetuar a autenticação usando seu nome de usuário e senha do {% data variables.product.prodname_dotcom_the_website %}. Pode-se exigir, também, que você habilite a autenticação de dois fatores. +Se você for um integrante de um {% data variables.product.prodname_emu_enterprise %}, você irá efetuar a autenticação em {% data variables.product.product_name %} no seu navegador usando seu IdP. Para obter mais informações, consulte "[Efetuando a autenticação como um usuário gerenciado](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %} + +Se você não for um integrante de um {% data variables.product.prodname_emu_enterprise %}, você irá efetuar a autenticação usando seu nome de usuário e senha do {% data variables.product.prodname_dotcom_the_website %}. Você também pode usar a autenticação de dois fatores e o logon único SAML, que pode ser exigido pela organização e pelos proprietários da empresa. + +{% else %} + +Você pode efetuar a autenticação no {% data variables.product.product_name %} no seu navegador de várias maneiras. + {% endif %} - **Apenas nome de usuário e senha** - Você criará uma senha ao criar sua conta em {% data variables.product.product_name %}. Recomendamos que você use um gerenciador de senhas para gerar uma senha aleatória e única. Para obter mais informações, consulte "[Criando uma senha forte](/github/authenticating-to-github/creating-a-strong-password)."{% ifversion fpt or ghec %} - Se você não tiver habilitado a 2FA, {% data variables.product.product_name %} irá pedir verificação adicional quando você efetuar o login a partir de um dispositivo não reconhecido, como um novo perfil de navegador, um navegador onde os cookies foram excluídos ou um novo computador. - Depois de fornecer seu nome de usuário e senha, será solicitado que você forneça um código de verificação que enviaremos para você por e-mail. Se você tiver o aplicativo para dispositivos móveis do GitHub Mobile, você receberá uma notificação pelo aplicativo.{% endif %} + Depois de fornecer seu nome de usuário e senha, será solicitado que você forneça um código de verificação que enviaremos para você por e-mail. If you have the {% data variables.product.prodname_mobile %} application installed, you'll receive a notification there instead. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."{% endif %} - **Autenticação de dois fatores (2FA)** (recomendado) - - If you enable 2FA, after you successfully enter your username and password, we'll also prompt you to provide a code that's generated by a time-based one time password (TOTP) application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. Para obter mais informações, consulte "[Acessar o {% data variables.product.prodname_dotcom %} usando a autenticação de dois fatores](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)". - - Além de autenticação com um aplicativo TOTP{% ifversion fpt or ghec %} ou uma mensagem de texto{% endif %}, você pode opcionalmente adicionar um método alternativo de autenticação com {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} ou{% endif %} uma chave de segurança usando WebAuthn. Para obter mais informações, consulte {% ifversion fpt or ghec %}"[Configurando autenticação de dois fatores com {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" e {% endif %}"[Configurando autenticação de dois fatores usando uma chave de segurança](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key).{% endif %}{% ifversion ghes %} -- **Autenticação do provedor de identidade (IdP)** - - O administrador do site pode configurar {% data variables.product.product_location %} para usar a autenticação com um IdP ao invés de um nome de usuário e senha. Para obter mais informações, consulte "[Métodos de autenticação externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)". + - Se você habilitar o 2FA, depois que você digitar seu nome de usuário e senha com sucesso, também vamos solicitar que você forneça um código gerado por um aplicativo {% ifversion fpt or ghec %} baseado em senha única (TOTP) no seu dispositivo móvel ou enviado como mensagem de texto (SMS){% endif %}. Para obter mais informações, consulte "[Acessar o {% data variables.product.prodname_dotcom %} usando a autenticação de dois fatores](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)". + - Além de autenticação com um aplicativo TOTP{% ifversion fpt or ghec %} ou uma mensagem de texto{% endif %}, você pode opcionalmente adicionar um método alternativo de autenticação com {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} ou{% endif %} uma chave de segurança usando WebAuthn. Para obter mais informações, consulte {% ifversion fpt or ghec %}"[Configurando autenticação de dois fatores com {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" e {% endif %}"[Configurando autenticação de dois fatores usando uma chave de segurança](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key).{% ifversion ghes %} +- **Autenticação externa** + - O administrador do site pode configurar {% data variables.product.product_location %} para usar a autenticação externa ao invés de um nome de usuário e senha. Para obter mais informações, consulte "[Métodos de autenticação externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)".{% endif %}{% ifversion fpt or ghec %} +- **logon único SAML** + - Antes de poder acessar os recursos pertencentes a uma conta corporativa ou organizacional que usa o logon único SAML, talvez você precise efetuar a autenticação por meio de um IdP. Para obter mais informações, consulte "[Sobre autenticação com logon único SAML](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}."{% endif %}{% endif %} + {% endif %} ## Efetuar a autenticação com {% data variables.product.prodname_desktop %} - Você pode efetuar a autenticação com o {% data variables.product.prodname_desktop %} usando seu navegador. Para obter mais informações, consulte " Autenticar-se no {% data variables.product.prodname_dotcom %}."

@@ -77,11 +89,11 @@ Você pode acessar repositórios no {% data variables.product.product_name %} pe ### HTTPS -Você pode trabalhar com todos os repositórios no {% data variables.product.product_name %} por meio de HTTPS, mesmo que você esteja atrás de um firewall ou proxy. +Você pode trabalhar com todos os repositórios no {% data variables.product.product_name %} por meio de HTTPS, mesmo que você esteja atrás de um firewall ou proxy. Se você fizer a autenticação com {% data variables.product.prodname_cli %}, você poderá efetuar a autenticação com um token de acesso pessoal ou por meio do navegador web. Para mais informações sobre a autenticação com {% data variables.product.prodname_cli %}, consulte [`login gh`](https://cli.github.com/manual/gh_auth_login). -Se você efetuar a autenticação sem {% data variables.product.prodname_cli %}, você deverá efetuar a autenticação com um token de acesso pessoal. {% data reusables.user-settings.password-authentication-deprecation %} Sempre que você usar o Git para efetuar a autenticação com {% data variables.product.product_name %}, será solicitado que você insira as suas credenciais para efetuar a autenticação com {% data variables.product.product_name %}, a menos que você faça o armazenamento em cache de um [auxiliar de credenciais](/github/getting-started-with-github/caching-your-github-credentials-in-git). +Se você efetuar a autenticação sem {% data variables.product.prodname_cli %}, você deverá efetuar a autenticação com um token de acesso pessoal. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them with a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git). diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md index d29266dc11..7dc03a5e4f 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md @@ -44,7 +44,7 @@ Um token com nenhum escopo atribuído só pode acessar informações públicas. {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.personal_access_tokens %} {% data reusables.user-settings.generate_new_token %} -5. Dê ao seu token um nome descritivo. ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %} +5. Dê ao seu token um nome descritivo. ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae or ghec %} 6. Para dar ao seu token uma data de vencimento, selecione o menu suspenso **Vencimento** e, em seguida, clique em um padrão ou use o seletor de calendário. ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %} 7. Selecione os escopos, ou as permissões, aos quais deseja conceder esse token. Para usar seu token para acessar repositórios da linha de comando, selecione **repo**. {% ifversion fpt or ghes or ghec %} @@ -80,5 +80,5 @@ Em vez de inserir manualmente seu PAT para cada operação de HTTPS do Git, voc ## Leia mais -- "[Sobre autenticação no GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} - "[Vencimento e revogação do Token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md index 7bd08e14ce..6b43287f8e 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md @@ -25,9 +25,9 @@ Você pode remover o arquivo com o commit mais recente com `git rm`. Para obter {% warning %} -Este artigo diz a você como tornar commits com dados confidenciais inacessíveis a partir de quaisquer branches ou tags do seu repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. No entanto, é importante destacar que esses commits talvez ainda possam ser acessados em clones ou bifurcações do repositório diretamente por meio de hashes SHA-1 em visualizações em cache no {% data variables.product.product_name %} e por meio de qualquer pull request que faça referência a eles. Não é possível remover dados confidenciais dos clones ou bifurcações de usuários do seu repositório, mas você pode remover permanentemente as visualizações e referências em cache para os dados confidenciais em pull requests no {% data variables.product.product_name %} entrando em contato com {% data variables.contact.contact_support %}. +**Aviso**: Este artigo diz a você como tornar commits com dados confidenciais inacessíveis a partir de quaisquer branches ou tags do seu repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. No entanto, esses commits talvez ainda possam ser acessados em clones ou bifurcações do repositório diretamente por meio de hashes SHA-1 em visualizações em cache no {% data variables.product.product_name %} e por meio de qualquer pull request que faça referência a eles. Não é possível remover dados confidenciais dos clones ou bifurcações de usuários do seu repositório, mas você pode remover permanentemente as visualizações e referências em cache para os dados confidenciais em pull requests no {% data variables.product.product_name %} entrando em contato com {% data variables.contact.contact_support %}. -**Aviso: Depois de ter feito o push de um commit para {% data variables.product.product_name %}, você deve considerar todos os dados confidenciais no commit comprometido.** Se você fez o commit de uma senha, altere-a! Se tiver feito commit de uma chave, crie outra. A remoção dos dados comprometidos não resolve sua exposição inicial, especialmente em clones ou bifurcações existentes do seu repositório. Considere essas limitações ao tomar a decisão de reescrever a história do repositório. +**Depois de ter feito o push de um commit para {% data variables.product.product_name %}, você deve considerar todos os dados confidenciais no commit comprometido.** Se você fez o commit de uma senha, altere-a! Se tiver feito commit de uma chave, crie outra. A remoção dos dados comprometidos não resolve sua exposição inicial, especialmente em clones ou bifurcações existentes do seu repositório. Considere essas limitações ao tomar a decisão de reescrever a história do repositório. {% endwarning %} @@ -152,7 +152,7 @@ Para ilustrar como `git filter-repo` funciona, mostraremos como remover seu arqu Depois de usar a ferramenta BFG ou `git filter-repo` para remover os dados confidenciais e fazer push das suas alterações para {% data variables.product.product_name %}, você deve seguir mais algumas etapas para remover completamente os dados de {% data variables.product.product_name %}. -1. Entre em contato com o {% data variables.contact.contact_support %} e solicite a remoção das visualizações em cache e das referências aos dados confidenciais em pull requests no {% data variables.product.product_name %}. Forneça o nome do repositório e/ou um link para o commit que você precisa que seja removido. +1. Entre em contato com o {% data variables.contact.contact_support %} e solicite a remoção das visualizações em cache e das referências aos dados confidenciais em pull requests no {% data variables.product.product_name %}. Forneça o nome do repositório e/ou um link para o commit que você precisa removido.{% ifversion ghes %} Para obter mais informações sobre como os administradores do site podem remover objetos do Git inacessíveis, consulte "[Utilitários da linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repo-gc)."{% endif %} 2. Peça para os colaboradores [fazerem rebase](https://git-scm.com/book/en/Git-Branching-Rebasing), *e não* merge, nos branches criados a partir do histórico antigo do repositório. Um commit de merge poderia reintroduzir o histórico antigo completo (ou parte dele) que você acabou de se dar ao trabalho de corrigir. 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 2bbdc8a6eb..cc16b9ea52 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 @@ -28,15 +28,11 @@ O log de segurança lista todas as ações realizadas nos últimos 90 dias. 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 %} -{% ifversion fpt or ghae or ghes or ghec %} ## Pesquisar no seu registro de segurança {% data reusables.audit_log.audit-log-search %} ### Pesquisar com base na ação -{% else %} -## Entender eventos no seu log de segurança -{% endif %} Os eventos listados no seu registro de segurança são acionados por suas ações. As ações são agrupadas nas seguintes categorias: @@ -109,10 +105,10 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev ### Ações da categoria `oauth_authorization` -| Ação | Descrição | -| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `create` | Acionada quando você [concede acesso a um {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps). | -| `destroy` | Acionada quando você [revoga o acesso de {% data variables.product.prodname_oauth_app %} à sua conta](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} e quando [as autorizações são revogadas ou vencem](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %} +| Ação | Descrição | +| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `create` | Acionada quando você [concede acesso a um {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps). | +| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %} {% ifversion fpt or ghec %} @@ -178,25 +174,25 @@ Uma visão geral de algumas das ações mais comuns que são registradas como ev {% ifversion fpt or ghec %} ### ações de categoria de `patrocinadores` -| Ação | Descrição | -| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `custom_amount_settings_change` | Acionada quando você habilita ou desabilita os valores personalizados ou quando altera os valores sugeridos (consulte "[Gerenciar as suas camadas de patrocínio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | -| `repo_funding_links_file_action` | Acionada quando você altera o arquivo FUNDING no repositório (consulte "[Exibir botão de patrocinador no repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | -| `sponsor_sponsorship_cancel` | Acionada quando você cancela um patrocínio (consulte "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | -| `sponsor_sponsorship_create` | Acionada quando você patrocina uma conta (consulte "[Patrocinar um contribuidor de código aberto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | -| `sponsor_sponsorship_payment_complete` | Acionada depois que você patrocinar uma conta e seu pagamento ser processado (consulte [Patrocinando um colaborador de código aberto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | -| `sponsor_sponsorship_preference_change` | Acionada quando você altera o recebimento de atualizações de e-mail de um desenvolvedor patrocinado (consulte "[Gerenciar o patrocínio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)") | -| `sponsor_sponsorship_tier_change` | Acionada quando você faz upgrade ou downgrade do patrocínio (consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | -| `sponsored_developer_approve` | Acionada quando sua conta do {% data variables.product.prodname_sponsors %} é aprovada (consulte "[Configuração de {% data variables.product.prodname_sponsors %} para sua conta pessoal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `sponsored_developer_create` | Acionada quando sua conta de {% data variables.product.prodname_sponsors %} é criada (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta pessoal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `sponsored_developer_disable` | Acionada quando sua conta {% data variables.product.prodname_sponsors %} está desabilitado | -| `sponsored_developer_redraft` | Acionada quando sua conta de {% data variables.product.prodname_sponsors %} é retornada ao estado de rascunho a partir do estado aprovado | -| `sponsored_developer_profile_update` | Acionada quando você edita seu perfil de desenvolvedor patrocinado (consulte "[Editar informações de perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)") | -| `sponsored_developer_request_approval` | Acionada quando você enviar seu aplicativo para {% data variables.product.prodname_sponsors %} para aprovação (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta pessoal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `sponsored_developer_tier_description_update` | Acionada quando você altera a descrição de uma camada de patrocínio (consulte "[Gerenciar suas camadas de patrocínio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)") | -| `sponsored_developer_update_newsletter_send` | Acionada quando você envia uma atualização por e-mail aos patrocinadores (consulte "[Entrar em contato com os patrocinadores](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)") | -| `waitlist_invite_sponsored_developer` | Acionada quando você é convidado a juntar-se a {% data variables.product.prodname_sponsors %} a partir da lista de espera (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta pessoal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | -| `waitlist_join` | Acionada quando você se junta à lista de espera para tornar-se um desenvolvedor patrocinado (consulte "[Configurar {% data variables.product.prodname_sponsors %} para sua conta pessoal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)") | +| Ação | Descrição | +| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `custom_amount_settings_change` | Acionada quando você habilita ou desabilita os valores personalizados ou quando altera os valores sugeridos (consulte "[Gerenciar as suas camadas de patrocínio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") | +| `repo_funding_links_file_action` | Acionada quando você altera o arquivo FUNDING no repositório (consulte "[Exibir botão de patrocinador no repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | +| `sponsor_sponsorship_cancel` | Acionada quando você cancela um patrocínio (consulte "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | +| `sponsor_sponsorship_create` | Acionada quando você patrocina uma conta (consulte "[Patrocinar um contribuidor de código aberto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | +| `sponsor_sponsorship_payment_complete` | Acionada depois que você patrocinar uma conta e seu pagamento ser processado (consulte [Patrocinando um colaborador de código aberto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") | +| `sponsor_sponsorship_preference_change` | Acionada quando você altera o recebimento de atualizações de e-mail de um desenvolvedor patrocinado (consulte "[Gerenciar o patrocínio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)") | +| `sponsor_sponsorship_tier_change` | Acionada quando você faz upgrade ou downgrade do patrocínio (consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)") | +| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `sponsored_developer_disable` | Acionada quando sua conta {% data variables.product.prodname_sponsors %} está desabilitado | +| `sponsored_developer_redraft` | Acionada quando sua conta de {% data variables.product.prodname_sponsors %} é retornada ao estado de rascunho a partir do estado aprovado | +| `sponsored_developer_profile_update` | Acionada quando você edita seu perfil de desenvolvedor patrocinado (consulte "[Editar informações de perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)") | +| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `sponsored_developer_tier_description_update` | Acionada quando você altera a descrição de uma camada de patrocínio (consulte "[Gerenciar suas camadas de patrocínio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)") | +| `sponsored_developer_update_newsletter_send` | Acionada quando você envia uma atualização por e-mail aos patrocinadores (consulte "[Entrar em contato com os patrocinadores](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)") | +| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | {% endif %} {% ifversion fpt or ghec %} diff --git a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md index ec0373359b..af896a2c19 100644 --- a/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md +++ b/translations/pt-BR/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md @@ -14,7 +14,7 @@ redirect_from: - /github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation --- -Se um token {% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}venceu ou {% endif %} foi revogado, ele não poderá mais ser usado para autenticar o Git e solicitações de API. Não é possível restaurar um token vencido ou revogado, você ou o aplicativo deverá criar um novo token. +Se um token {% ifversion fpt or ghae or ghes > 3.2 or ghec %}venceu ou {% endif %} foi revogado, ele não poderá mais ser usado para autenticar o Git e solicitações de API. Não é possível restaurar um token vencido ou revogado, você ou o aplicativo deverá criar um novo token. Este artigo explica os possíveis motivos pelos quais seu token {% data variables.product.product_name %} pode ser revogado ou vencido. @@ -24,7 +24,7 @@ Este artigo explica os possíveis motivos pelos quais seu token {% data variable {% endnote %} -{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## Token revogado após atingir sua data de validade Ao criar um token de acesso pessoal, recomendamos que você defina uma data de vencimento para o seu token. Ao alcançar a data de vencimento do seu token, este será automaticamente revogado. Para obter mais informações, consulte "[Criando um token de acesso pessoal](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." 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 f83547ab56..5f0b328b4c 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 @@ -57,7 +57,7 @@ Consulte "[Revisar integrações autorizadas](/articles/reviewing-your-authorize {% ifversion not ghae %} -Se você redefiniu sua senha de conta e também gostaria de acionar um logout do aplicativo GitHub Mobile, você pode revogar a sua autorização do aplicativo OAuth "GitHub iOS" ou "GitHub Android". Para obter mais informações, consulte "[Revisar integrações autorizadas](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)". +If you have reset your account password and would also like to trigger a sign-out from the {% data variables.product.prodname_mobile %} app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. This will sign out all instances of the {% data variables.product.prodname_mobile %} app associated with your account. Para obter mais informações, consulte "[Revisar integrações autorizadas](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)". {% endif %} diff --git a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md index 5e78365d34..6f109c093f 100644 --- a/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md +++ b/translations/pt-BR/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md @@ -22,7 +22,7 @@ shortTitle: Altere método de entrega de 2FA {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security %} -3. Next to "Primary two-factor method", click **Change**. ![Edit primary delivery options](/assets/images/help/2fa/edit-primary-delivery-option.png) +3. Ao lado de "Método primário de dois fatores", clique em **Alterar**. ![Editar opções de entrega primária](/assets/images/help/2fa/edit-primary-delivery-option.png) 4. Em "Delivery options" (Opções de entrega), clique em **Reconfigure two-factor authentication** (Reconfigurar autenticação de dois fatores). ![Alternar as opções de entrega de 2FA](/assets/images/help/2fa/2fa-switching-methods.png) 5. Decida se deseja configurar a autenticação de dois fatores usando um app móvel TOTP ou uma mensagem de texto. Para obter mais informações, consulte "[Configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)". - Para configurar a autenticação de dois fatores usando um app móvel TOTP, clique em **Set up using an app** (Configurar usando um app). 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 eadd932a07..6bf90c1d20 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 @@ -48,7 +48,7 @@ Os trabalhos que são executados em Windows e macOS runners que o {% data variab O armazenamento usado por um repositório é o armazenamento total usado por artefatos {% data variables.product.prodname_actions %} e {% data variables.product.prodname_registry %}. Seu custo de armazenamento é o uso total de todos os repositórios de sua conta. Para obter mais informações sobre preços para {% data variables.product.prodname_registry %}, consulte "[Sobre cobrança para {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)." - Se o uso da sua conta ultrapassar esses limites e você definir um limite de gastos acima de US$ 0, você pagará US$ 0,25 por GB de armazenamento por mês e uso por minuto, dependendo do sistema operacional usado pelo executor hospedado em {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} arredonda os minutos que cada trabalho usa até o minuto mais próximo. + If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} arredonda os minutos que cada trabalho usa até o minuto mais próximo. {% note %} diff --git a/translations/pt-BR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/pt-BR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md index f21951f544..8e37eec43e 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md +++ b/translations/pt-BR/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md @@ -50,9 +50,9 @@ Todos os dados transferidos, quando acionados por {% data variables.product.prod O uso do armazenamento é compartilhado com artefatos de construção produzidos por {% data variables.product.prodname_actions %} para repositórios de sua conta. 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)." -O {% data variables.product.prodname_dotcom %} cobra o uso da conta que possui o repositório onde o pacote é publicado. Se o uso da sua conta ultrapassar esses limites e você definir um limite de gastos acima de US$ 0, você pagará US$ 0,25 por GB de armazenamento e US$ 0,50 por GB de transferência de dados. +O {% data variables.product.prodname_dotcom %} cobra o uso da conta que possui o repositório onde o pacote é publicado. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and $0.50 USD per GB of data transfer. -Por exemplo, se sua organização usa {% data variables.product.prodname_team %}, permite gastos ilimitados, usa 150GB de armazenamento, e possui 50GB de transferência de dados durante um mês, a organização teria excessos de 148GB para armazenamento e 40GB para transferência de dados para esse mês. O excesso de armazenamento custaria US$ 0,25 por GB ou US$ 37. O excesso para transferência de dados custaria US$ 0,50 ou US$ 20 por GB. +Por exemplo, se sua organização usa {% data variables.product.prodname_team %}, permite gastos ilimitados, usa 150GB de armazenamento, e possui 50GB de transferência de dados durante um mês, a organização teria excessos de 148GB para armazenamento e 40GB para transferência de dados para esse mês. The storage overage would cost $0.008 USD per GB per day or $37 USD. O excesso para transferência de dados custaria US$ 0,50 ou US$ 20 por GB. {% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %} diff --git a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md index d926a547bc..12bea6ec71 100644 --- a/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md +++ b/translations/pt-BR/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md @@ -57,7 +57,7 @@ Uma pessoa pode ser capaz de concluir as tarefas porque a pessoa tem todas as fu **Dicas**: - Embora não seja necessário, recomendamos que o proprietário da organização envie um convite para o mesmo endereço de e-mail usado para o nome primário do usuário do assinante (UPN). Quando o endereço de e-mail em {% data variables.product.product_location %} corresponder ao UPN do assinante, você poderá garantir que outra empresa não reivindique a licença do assinante. - - Se o assinante aceitar o convite para a organização com uma conta pessoal existente em {% data variables.product.product_location %}, recomendamos que o assinante adicione o endereço de e-mail que ele usa para {% data variables.product.prodname_vs %} à sua conta pessoal em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Adicionar um endereço de e-mail à sua conta de {% data variables.product.prodname_dotcom %}](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)". + - Se o assinante aceitar o convite para a organização com uma conta pessoal existente em {% data variables.product.product_location %}, recomendamos que o assinante adicione o endereço de e-mail que ele usa para {% data variables.product.prodname_vs %} à sua conta pessoal em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Adicionar um endereço de e-mail à sua conta de {% data variables.product.prodname_dotcom %}](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)". - Se o proprietário da organização tiver de convidar um grande número de assinantes, um script poderá agilizar o processo. Para obter mais informações, consulte [a amostra de script do PowerShell](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) no repositório `github/platform-samples`. {% endtip %} diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md index cccde8bdec..a462055e5a 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md @@ -73,7 +73,7 @@ By default, the {% data variables.product.prodname_codeql_workflow %} uses the ` If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Additionally, when an `on:push` scan returns results that can be mapped to an open pull request, these alerts will automatically appear on the pull request in the same places as other pull request alerts. The alerts are identified by comparing the existing analysis of the head of the branch to the analysis for the target branch. For more information on {% data variables.product.prodname_code_scanning %} alerts in pull requests, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." {% endif %} @@ -85,7 +85,7 @@ For more information about the `pull_request` event, see "[Events that trigger w If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." {% endif %} diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index 8e17b6479c..60ed88d52d 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -147,9 +147,9 @@ Os nomes das verificações de análise de {% data variables.product.prodname_co ![Verificações de pull request de {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-pr-checks.png) -Quando os trabalhos de {% data variables.product.prodname_code_scanning %} forem concluídos, {% data variables.product.prodname_dotcom %} calcula se quaisquer alertas foram adicionados pelo pull request e adiciona a entrada "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" à lista de verificações. Depois de {% data variables.product.prodname_code_scanning %} ser executado pelo menos uma vez, você poderá clicar em **Detalhes** para visualizar os resultados da análise. Se você usou um pull request para adicionar {% data variables.product.prodname_code_scanning %} ao repositório, inicialmente você verá uma mensagem de {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} "Análise não encontrada"{% else %}"Análise ausente"{% endif %} ao clicar em **Detalhes** na verificação de "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" +Quando os trabalhos de {% data variables.product.prodname_code_scanning %} forem concluídos, {% data variables.product.prodname_dotcom %} calcula se quaisquer alertas foram adicionados pelo pull request e adiciona a entrada "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" à lista de verificações. Depois de {% data variables.product.prodname_code_scanning %} ser executado pelo menos uma vez, você poderá clicar em **Detalhes** para visualizar os resultados da análise. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. -{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ![Análise não encontrada para mensagem de commit](/assets/images/help/repository/code-scanning-analysis-not-found.png) A tabela lista uma ou mais categorias. Cada categoria está relacionada a análises específicas, para a mesma ferramenta e commit, realizadas em uma linguagem diferente ou em uma parte diferente do código. Para cada categoria a tabela mostra as duas análises que {% data variables.product.prodname_code_scanning %} tentou comparar para determinar quais alertas foram introduzidos ou corrigidos no pull request. @@ -159,13 +159,13 @@ Por exemplo, na captura de tela acima, {% data variables.product.prodname_code_s ![Análise ausente para mensagem de commit](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png) {% endif %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ### Motivos para a mensagem "Análise não encontrada" {% else %} ### Motivos para a mensagem "Análise ausente" {% endif %} -Depois que {% data variables.product.prodname_code_scanning %} analisou o código em um pull request, ele precisa comparar a análise do branch de tópico (o branch que você usou para criar o pull request) com a análise do branch de base (o branch no qual você deseja mesclar o pull request). Isso permite que {% data variables.product.prodname_code_scanning %} calcule quais alertas foram recém-introduzidos pelo pull request, que alertas já estavam presentes no branch de base e se alguns alertas existentes são corrigidos pelas alterações no pull request. Inicialmente, se você usar um pull request para adicionar {% data variables.product.prodname_code_scanning %} a um repositório, o branch de base ainda não foi analisado. Portanto, não é possível computar esses detalhes. Neste caso, quando você clicar nos resultados verificando o pull request você verá a mensagem {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}"Análise não encontrada"{% else %}"Análise ausente do commit base SHA-HASH"{% endif %}. +Depois que {% data variables.product.prodname_code_scanning %} analisou o código em um pull request, ele precisa comparar a análise do branch de tópico (o branch que você usou para criar o pull request) com a análise do branch de base (o branch no qual você deseja mesclar o pull request). Isso permite que {% data variables.product.prodname_code_scanning %} calcule quais alertas foram recém-introduzidos pelo pull request, que alertas já estavam presentes no branch de base e se alguns alertas existentes são corrigidos pelas alterações no pull request. Inicialmente, se você usar um pull request para adicionar {% data variables.product.prodname_code_scanning %} a um repositório, o branch de base ainda não foi analisado. Portanto, não é possível computar esses detalhes. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. Há outras situações em que não pode haver análise para o último commit do branch de base para um pull request. Isso inclui: diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md index d9514a5133..9fbe7b008a 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md @@ -28,7 +28,7 @@ topics: ## Sobre os resultados de {% data variables.product.prodname_code_scanning %} em pull requests Em repositórios onde {% data variables.product.prodname_code_scanning %} está configurado como uma verificação de pull request, {% data variables.product.prodname_code_scanning %} verifica o código no pull request. Por padrão, isso é limitado a pull requests que visam o branch-padrão ou branches protegidos, mas você pode alterar esta configuração em {% data variables.product.prodname_actions %} ou em um sistema de CI/CD de terceiros. Se o merge das alterações introduziria novos alertas de {% data variables.product.prodname_code_scanning %} no branch de destino, estes serão relatados como resultados de verificação no pull request. Os alertas também são exibidos como anotações na aba **Arquivos alterados** do pull request. Se você tiver permissão de gravação no repositório, você poderá ver qualquer alerta de {% data variables.product.prodname_code_scanning %} existente na aba **Segurança**. Para obter informações sobre os alertas do repositório, consulte "[Gerenciar alertas de {% data variables.product.prodname_code_scanning %} do repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)". -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Em repositórios em que {% data variables.product.prodname_code_scanning %} está configurado para digitalizar sempre que o código é enviado por push, o {% data variables.product.prodname_code_scanning %} também mapeará os resultados com qualquer solicitação de pull pull aberto e irá adicionar os alertas como anotações nos mesmos lugares que as outras verificações de pull request. Para obter mais informações, consulte "[Digitalizando ao enviar por push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)". {% endif %} @@ -42,7 +42,7 @@ Há muitas opções para configurar {% data variables.product.prodname_code_scan Para todas as configurações de {% data variables.product.prodname_code_scanning %}, a verificação que contém os resultados de {% data variables.product.prodname_code_scanning %} é: **resultados de {% data variables.product.prodname_code_scanning_capc %}**. Os resultados de cada ferramenta de análise utilizada são mostrados separadamente. Todos os novos alertas gerados por alterações no pull request são exibidos como anotações. -{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 or ghec %} Para ver o conjunto completo de alertas para o branch analisado, clique em **Ver todos os alertas do branch**. Isso abre a visualização completa de alerta onde você pode filtrar todos os alertas sobre o branch por tipo, gravidade, tag, etc. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts). " +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. Isso abre a visualização completa de alerta onde você pode filtrar todos os alertas sobre o branch por tipo, gravidade, tag, etc. Para obter mais informações, consulte "[Gerenciar alertas de varredura de código para seu repositório](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts). " ![Verificação de resultados de {% data variables.product.prodname_code_scanning_capc %} em um pull request](/assets/images/help/repository/code-scanning-results-check.png) {% 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 0ee34c0564..eb8c5093dd 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 @@ -396,7 +396,7 @@ codeql database analyze <database> --format=<format> \ - Opcional. Use if you want to include CodeQL query packs in your analysis. For more information, see "Downloading and using {% data variables.product.prodname_codeql %} packs." + Opcional. Use se você quiser incluir pacotes de consultas do CodeQL na sua análise. Para obter mais informações, consulte "Fazer o download e usar pacotes de {% data variables.product.prodname_codeql %}." @@ -409,7 +409,7 @@ codeql database analyze <database> --format=<format> \ - Opcional. Use if some of your CodeQL query packs are not yet on disk and need to be downloaded before running queries.{% endif %} + Opcional. Use se alguns de seus pacotes de consulta do CodeQL ainda não estiverem em disco e precisarem ser baixados antes de executar consultas.{% endif %} @@ -597,7 +597,7 @@ Não há saída deste comando a menos que o upload não tenha sido bem-sucedido. O pacote de {% data variables.product.prodname_codeql_cli %} inclui consultas mantidas por especialistas de {% data variables.product.company_short %}, pesquisadores de segurança e contribuidores da comunidade. Se você quiser executar consultas desenvolvidas por outras organizações, os pacotes de consulta de {% data variables.product.prodname_codeql %} fornecem uma forma eficiente e confiável de fazer o download e executar consultas. Para obter mais informações, consulte "[Sobre digitalização de código com o CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)". -Before you can use a {% data variables.product.prodname_codeql %} pack to analyze a database, you must download any packages you require from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}. This can be done either by using the `--download` flag as part of the `codeql database analyze` command. Se um pacote não estiver disponível publicamente, você precisará usar um {% data variables.product.prodname_github_app %} ou um token de acesso pessoal para efetuar a autenticação. Para obter mais informações e um exemplo, consulte "[o Fazer upload dos resultados para {% data variables.product.product_name %}](#uploading-results-to-github)" acima. +Antes de poder usar um pacote de {% data variables.product.prodname_codeql %} para analisar um banco de dados, você deve fazer o download de todos os pacotes que necessitar no {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}. Isso pode ser feito usando o sinalizador `--download` como parte do comando `codeql database analyze`. Se um pacote não estiver disponível publicamente, você precisará usar um {% data variables.product.prodname_github_app %} ou um token de acesso pessoal para efetuar a autenticação. Para obter mais informações e um exemplo, consulte "[o Fazer upload dos resultados para {% data variables.product.product_name %}](#uploading-results-to-github)" acima. @@ -624,7 +624,7 @@ Before you can use a {% data variables.product.prodname_codeql %} pack to analyz @@ -644,12 +644,12 @@ Before you can use a {% data variables.product.prodname_codeql %} pack to analyz ### Exemplo básico -This example runs the `codeql database analyze` command with the `--download` option to: +Este exemplo executa o comando `codeql database analyze` com a opção `--download` para: -1. Download the latest version of the `octo-org/security-queries` pack. -2. Download a version of the `octo-org/optional-security-queries` pack that is *compatible* with version 1.0.1 (in this case, it is version 1.0.2). For more information on semver compatibility, see [npm's semantic version range documentation](https://github.com/npm/node-semver#ranges). -3. Run all the default queries in `octo-org/security-queries`. -4. Run only the query `queries/csrf.ql` from `octo-org/optional-security-queries` +1. Faça o download do pacote `octo-org/security-queries`. +2. Faça o download de uma versão do pacote `octo-org/optional-security-queries` que é *compatível* com a versão 1.0.1 (nesse caso, é a versão 1.0.2). Para obter mais informações sobre a compatibilidade de semver, consulte [documentação da intervalo da versão semântica do npm](https://github.com/npm/node-semver#ranges). +3. Executar todas as consultas padrão em `octo-org/security-queries`. +4. Execute apenas a consulta `queries/csrf.ql` a partir de `octo-org/opcional-security-queries` ``` $ echo $OCTO-ORG_ACCESS_TOKEN | codeql database analyze --download /codeql-dbs/example-repo \ @@ -672,9 +672,9 @@ $ echo $OCTO-ORG_ACCESS_TOKEN | codeql database analyze --download /codeql-dbs/e > Interpreting results. ``` -### Direct download of {% data variables.product.prodname_codeql %} packs +### Download direto dos pacotes de {% data variables.product.prodname_codeql %} -If you want to download a {% data variables.product.prodname_codeql %} pack without running it immediately, then you can use the `codeql pack download` command. This is useful if you want to avoid accessing the internet when running {% data variables.product.prodname_codeql %} queries. When you run the {% data variables.product.prodname_codeql %} analysis, you can specify packs, versions, and paths in the same way as in the previous example: +Se você quiser fazer o download de um pacote de {% data variables.product.prodname_codeql %} sem executá-lo imediatamente, você pode usar o comando `codeql pack download`. Isso é útil se você quiser evitar acessar a internet quando executar consultas de {% data variables.product.prodname_codeql %}. Ao executar a análise {% data variables.product.prodname_codeql %}, você pode especificar pacotes, versões e caminhos da mesma forma como no exemplo anterior: ```shell echo $OCTO-ORG_ACCESS_TOKEN | codeql pack download <scope/name@version:path> <scope/name@version:path> ... diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index 199bba4572..c9b5bf0732 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -10,7 +10,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -85,7 +85,7 @@ Para repositórios em que {% data variables.product.prodname_dependabot_security É possível ver todos os alertas que afetam um determinado projeto{% ifversion fpt or ghec %} na aba Segurança do repositório ou{% endif %} no gráfico de dependências do repositório. Para obter mais informações, consulte "[Visualizando {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)." -Por padrão, notificamos as pessoas com permissões de administrador nos repositórios afetados sobre os novos {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas para qualquer repositório. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working with repositories that you own or have admin permissions for. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". +Por padrão, notificamos as pessoas com permissões de administrador nos repositórios afetados sobre os novos {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas para qualquer repositório. Você também pode tornar o {% data variables.product.prodname_dependabot_alerts %} visível para pessoas ou repositórios de trabalho de equipes adicionais que você possui ou para os quais tem permissões de administrador. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". {% endif %} {% data reusables.notifications.vulnerable-dependency-notification-enable %} diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md index 83bbc87f3d..c3024fc356 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md @@ -5,7 +5,7 @@ shortTitle: Configurar alertas Dependabot versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md index f2b4d4e400..3d1389aabb 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -31,7 +31,7 @@ Quando {% data variables.product.prodname_dependabot %} detecta dependências vu {% ifversion fpt or ghec %}Se você é proprietário de uma organização, você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} para todos os repositórios da sua organização com um clique. Você também pode definir se a detecção de dependências vulneráveis será habilitada ou desabilitada para repositórios recém-criados. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)". {% endif %} -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} Por padrão, se o proprietário da sua empresa configurou e-mail para notificações na sua empresa, você receberá {% data variables.product.prodname_dependabot_alerts %} por e-mail. Os proprietários das empresas também podem habilitar {% data variables.product.prodname_dependabot_alerts %} sem notificações. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md index d2a0d7fd90..115465a04b 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md @@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md index fdc0582a50..986639d2ca 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md @@ -11,7 +11,7 @@ shortTitle: Ver alertas do Dependabot versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -55,7 +55,7 @@ Para as linguagens compatíveis, {% data variables.product.prodname_dependabot % {% note %} -**Observação:** Durante a versão beta, esse recurso está disponível apenas para novas consultorias do Python criadas *depois de* 14 de abril de 2022 e para um subconjunto de consultorias históricas do Python. O GitHub está trabalhando para preencher dados de backfill através de consultorias históricas no Python, que são adicionadas regularmente. As chamadas vulneráveis são destacadas apenas nas páginas de {% data variables.product.prodname_dependabot_alerts %}. +**Observação:** Durante a versão beta, esse recurso está disponível apenas para novas consultorias do Python criadas *depois de* 14 de abril de 2022 e para um subconjunto de consultorias históricas do Python. {% data variables.product.prodname_dotcom %} is working to backfill data across additional historical Python advisories, which are added on a rolling basis. As chamadas vulneráveis são destacadas apenas nas páginas de {% data variables.product.prodname_dependabot_alerts %}. {% endnote %} @@ -65,7 +65,7 @@ Você pode filtrar a visualização para mostrar apenas alertas em que {% data v Para alertas quando chamadas vulneráveis forem detectadas, a página de detalhes de alerta mostra informações adicionais: -- Um bloco de código que mostra onde a função é usada ou, onde houver várias chamadas, a primeira chamada para a função. +- One or more code blocks showing where the function is used. - Uma anotação que lista a função em si, com um link para a linha onde a função é chamada. ![Captura de tela que mostra a página de detalhes de alerta para um alerta com uma etiqueta "chamada vulnerável"](/assets/images/help/repository/review-calls-to-vulnerable-functions.png) diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md index 2fd22eb3f2..eb2b34ac23 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md @@ -63,7 +63,7 @@ Se as atualizações de segurança não estiverem habilitadas para o seu reposit Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para um repositório individual (veja abaixo). -Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para todos os repositórios pertencentes à sua conta pessoal ou organização. Para mais informações consulte "[Gerenciar as configurações de segurança e análise da sua conta pessoal](/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)". +Você também pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_security_updates %} para todos os repositórios pertencentes à sua conta pessoal ou organização. For more information, see "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." O {% data variables.product.prodname_dependabot_security_updates %} exige configurações específicas do repositório. Para obter mais informações, consulte "[Repositórios compatíveis](#supported-repositories)". diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md index 20ebeef41d..6646217d48 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md @@ -30,7 +30,7 @@ shortTitle: Atualizações de versão do Dependabot O {% data variables.product.prodname_dependabot %} facilita a manutenção de suas dependências. Você pode usá-lo para garantir que seu repositório se mantenha atualizado automaticamente com as versões mais recentes dos pacotes e aplicações do qual ele depende. -You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_configuration file into your repository. O arquivo de configuração especifica a localização do manifesto ou de outros arquivos de definição de pacote, armazenados no seu repositório. O {% data variables.product.prodname_dependabot %} usa essas informações para verificar pacotes e aplicativos desatualizados. {% data variables.product.prodname_dependabot %} determina se há uma nova versão de uma dependência observando a versão semântica ([semver](https://semver.org/)) da dependência para decidir se deve atualizar para essa versão. Para certos gerentes de pacote, {% data variables.product.prodname_dependabot_version_updates %} também é compatível com armazenamento. Dependências de vendor (ou armazenadas) são dependências registradas em um diretório específico em um repositório, em vez de referenciadas em um manifesto. Dependências de vendor estão disponíveis no tempo de criação, ainda que os servidores de pacote estejam indisponíveis. {% data variables.product.prodname_dependabot_version_updates %} pode ser configurado para verificar as dependências de vendor para novas versões e atualizá-las, se necessário. +You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_ configuration file into your repository. O arquivo de configuração especifica a localização do manifesto ou de outros arquivos de definição de pacote, armazenados no seu repositório. O {% data variables.product.prodname_dependabot %} usa essas informações para verificar pacotes e aplicativos desatualizados. {% data variables.product.prodname_dependabot %} determina se há uma nova versão de uma dependência observando a versão semântica ([semver](https://semver.org/)) da dependência para decidir se deve atualizar para essa versão. Para certos gerentes de pacote, {% data variables.product.prodname_dependabot_version_updates %} também é compatível com armazenamento. Dependências de vendor (ou armazenadas) são dependências registradas em um diretório específico em um repositório, em vez de referenciadas em um manifesto. Dependências de vendor estão disponíveis no tempo de criação, ainda que os servidores de pacote estejam indisponíveis. {% data variables.product.prodname_dependabot_version_updates %} pode ser configurado para verificar as dependências de vendor para novas versões e atualizá-las, se necessário. Quando {% data variables.product.prodname_dependabot %} identifica uma dependência desatualizada, ele cria uma pull request para atualizar o manifesto para a última versão da dependência. Para dependências de vendor, {% data variables.product.prodname_dependabot %} levanta um pull request para substituir diretamente a dependência desatualizada pela nova versão. Você verifica se os seus testes passam, revisa o changelog e lança observações incluídas no resumo do pull request e, em seguida, faz a mesclagem. Para obter mais informações, consulte "[Configurando 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)". diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md index 9d487e1c2a..b8948582cd 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md @@ -322,7 +322,7 @@ Para obter mais informações sobre os comandos `@dependabot ignore`, consulte [ Você pode usar a opção `ignore` para personalizar quais dependências são atualizadas. A opção `ignore` suporta as seguintes opções. -- `dependency-name`—use para ignorar atualizações para dependências com nomes correspondentes, opcionalmente usando `*` para corresponder a zero ou mais caracteres. Para dependências do Java, o formato do atributo `dependency-name` é: `groupId:artifactId` (por exemplo: `org.kohsuke:github-api`). {% if dependabot-grouped-dependencies %} To prevent {% data variables.product.prodname_dependabot %} from automatically updating TypeScript type definitions from DefinitelyTyped, use `@types/*`.{% endif %} +- `dependency-name`—use para ignorar atualizações para dependências com nomes correspondentes, opcionalmente usando `*` para corresponder a zero ou mais caracteres. Para dependências do Java, o formato do atributo `dependency-name` é: `groupId:artifactId` (por exemplo: `org.kohsuke:github-api`). {% if dependabot-grouped-dependencies %} Para evitar que {% data variables.product.prodname_dependabot %} atualize automaticamente as definições do tipo TypeScript a partir de DefinitelyType, use `@types/*`.{% endif %} - `versions`—use para ignorar versões específicas ou intervalos de versões. Se você deseja definir um intervalo, use o padrão pattern para o gerenciador de pacotes (por exemplo: `^1.0.0` para npm, ou `~> 2.0` para o Bundler). - `update-types`—use para ignorar tipos de atualizações, como semver `major`, `minor` ou `atualizações de atualização de versão` (por exemplo: `version-update:semver-patch` ignorará atualizações de patch). Você pode combinar isso com a `dependency-name: "*"` para ignorar em `update-types` específicos para todas as dependências. Atualmente, `version-update:semver-major`, `version-update:semver-minor` e `version-update:semver-patch` são as únicas opções compatíveis. As atualizações de segurança não afetadas por esta configuração. diff --git a/translations/pt-BR/content/code-security/dependabot/index.md b/translations/pt-BR/content/code-security/dependabot/index.md index e080f0eaef..94193e40a4 100644 --- a/translations/pt-BR/content/code-security/dependabot/index.md +++ b/translations/pt-BR/content/code-security/dependabot/index.md @@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md index bdf9847a41..6038a6d436 100644 --- a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md +++ b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md @@ -452,9 +452,9 @@ jobs: ### Habilitar o merge automático em um pull request -If you want to allow maintainers to mark certain pull requests for auto-merge, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. Isto permite que o pull request seja mesclado quando todos os testes e aprovações forem cumpridos com sucesso. Para obter mais informações sobre merge automático, consulte "[Fazer merge automático de um pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)". +Se você quiser permitir que os mantenedores marquem certos pull requests para o merge automático, você pode usar a funcionalidade de merge automático de {% data variables.product.prodname_dotcom %}. Isto permite que o pull request seja mesclado quando todos os testes e aprovações forem cumpridos com sucesso. Para obter mais informações sobre merge automático, consulte "[Fazer merge automático de um pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)". -You can instead use {% data variables.product.prodname_actions %} and the {% data variables.product.prodname_cli %}. Here is an example that auto merges all patch updates to `my-dependency`: +Em vez disso, você pode usar {% data variables.product.prodname_actions %} e {% data variables.product.prodname_cli %}. Aqui está um exemplo que faz o merge automático de todas as atualizações do patch para `my-dependency`: {% ifversion ghes = 3.3 %} diff --git a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index d9dc0f05af..3760f3d8cc 100644 --- a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -36,7 +36,7 @@ O {% data variables.product.prodname_dotcom %} gera e exibe dados de dependênci * {% data variables.product.prodname_dependabot %} verifica qualquer push, para o branch-padrão, que contém um arquivo de manifesto. Quando um novo registro de vulnerabilidade é adicionado, ele verifica todos os repositórios existentes e gera um alerta para cada repositório vulnerável. {% data variables.product.prodname_dependabot_alerts %} são agregados ao nível do repositório, em vez de criar um alerta por vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". * {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} são acionados quando você recebe um alerta sobre uma dependência vulnerável no repositório. Sempre que possível, {% data variables.product.prodname_dependabot %} cria um pull request no repositório para atualizar a dependência vulnerável à versão mínima segura necessária para evitar a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" e "[Solução de problemas de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)". - {% endif %}{% data variables.product.prodname_dependabot %} não pesquisa repositórios com relação a dependências vulneráveis de uma programação, mas o faz quando algo muda. Por exemplo, aciona-se uma varredura quando uma nova dependência é adicionada ({% data variables.product.prodname_dotcom %} verifica isso em cada push), ou quando uma nova vulnerabilidade é adicionada ao banco de dados da consultoria{% ifversion ghes or ghae-issue-4864 %} e sincronizado com {% data variables.product.product_location %}{% endif %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)". + {% endif %}{% data variables.product.prodname_dependabot %} não pesquisa repositórios com relação a dependências vulneráveis de uma programação, mas o faz quando algo muda. Por exemplo, aciona-se uma varredura quando uma nova dependência é adicionada ({% data variables.product.prodname_dotcom %} verifica isso em cada push), ou quando uma nova vulnerabilidade é adicionada ao banco de dados da consultoria{% ifversion ghes or ghae %} e sincronizado com {% data variables.product.product_location %}{% endif %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)". ## {% data variables.product.prodname_dependabot_alerts %} só está relacionado a dependências vulneráveis nos manifestos e arquivos de bloqueio? 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 6c4d6c538f..262b392eea 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 @@ -20,7 +20,7 @@ topics: O {% data variables.product.prodname_advisory_database %} contém uma lista de vulnerabilidades de segurança que você pode visualizar, pesquisar e filtrar. {% data reusables.security-advisory.link-browsing-advisory-db %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Disponível para todos os repositórios {% endif %} ### Política de segurança @@ -40,7 +40,7 @@ Discute em particular e corrige vulnerabilidades de segurança no código do seu Ver alertas sobre dependências conhecidas por conter vulnerabilidades de segurança e escolher se deseja gerar pull requests para atualizar essas dependências automaticamente. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" e "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". {% endif %} -{% ifversion ghes < 3.3 or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae %} ### {% data variables.product.prodname_dependabot_alerts %} {% data reusables.dependabot.dependabot-alerts-beta %} @@ -54,7 +54,7 @@ Exibir alertas sobre dependências conhecidas por conter vulnerabilidades de seg Use {% data variables.product.prodname_dependabot %} para levantar automaticamente os pull requests a fim de manter suas dependências atualizadas. Isso ajuda a reduzir a exposição a versões mais antigas de dependências. Usar versões mais recentes facilita a aplicação de patches, caso as vulnerabilidades de segurança sejam descobertas e também torna mais fácil para {% data variables.product.prodname_dependabot_security_updates %} levantar, com sucesso, os pull requests para atualizar as dependências vulneráveis. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)". {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ### Gráfico de dependências O gráfico de dependências permite explorar os ecossistemas e pacotes dos quais o repositório depende e os repositórios e pacotes que dependem do seu repositório. @@ -99,13 +99,13 @@ Disponível apenas com uma licença para {% data variables.product.prodname_GH_a Detectar automaticamente tokens ou credenciais que foram verificados em um repositório. Você pode visualizar alertas para quaisquer segredos que {% data variables.product.company_short %} encontrar no seu código, para que você saiba quais tokens ou credenciais tratar como comprometidas. Para obter mais informações, consulte "[Sobre a varredura de segredos](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ### Revisão de dependência 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 or ghae-issue-4554 %} +{% ifversion ghec or ghes > 3.1 or ghae %} ### Visão geral de segurança das organizações{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}, empresas,{% endif %} e equipes {% ifversion ghec %} 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 40b97834a4..e12a57947b 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 @@ -33,7 +33,7 @@ Você pode criar uma política de segurança padrão que será exibida em qualqu {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Gerenciar {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências {% 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. @@ -51,7 +51,7 @@ Você pode criar uma política de segurança padrão que será exibida em qualqu Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" "[Explorando as dependências de um repositório](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" e "[Gerenciando 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)". {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Gerenciando revisão de dependências @@ -138,7 +138,7 @@ Você pode visualizar e gerenciar alertas de funcionalidades de segurança para {% ifversion fpt or ghec %}Se você tiver uma vulnerabilidade de segurança, você poderá criar uma consultoria de segurança para discutir em privado e corrigir a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" e " "[Criar uma consultoria de segurança](/code-security/security-advisories/creating-a-security-advisory)". {% endif %} -{% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4554 %}{% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}Você{% elsif fpt %}As organizações que usam {% data variables.product.prodname_ghe_cloud %}{% endif %} podem visualizar, filtrar e ordenar alertas de seguranla para repositórios pertencentes à {% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}sua{% elsif fpt %}their{% endif %} organização na visão geral de segurança. Para obter mais informações, consulte{% ifversion ghes or ghec or ghae-issue-4554 %} "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview).{% elsif fpt %} "[Sobre a visão geral de segurança](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" na documentação de {% data variables.product.prodname_ghe_cloud %} .{% endif %}{% endif %} +{% ifversion fpt or ghes > 3.1 or ghec or ghae %}{% ifversion ghes > 3.1 or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %} {% ifversion ghec %} diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md b/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md index 3c73c0e21a..7c4fe8cbae 100644 --- a/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md +++ b/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md @@ -44,7 +44,7 @@ Na página principal do seu repositório, clique em **{% octicon "gear" aria-lab Para obter mais informações, consulte "[Adicionar uma política de segurança ao seu repositório](/code-security/getting-started/adding-a-security-policy-to-your-repository)". -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Gerenciar o gráfico de dependências {% ifversion fpt or ghec %} @@ -61,7 +61,7 @@ Para obter mais informações, consulte "[Explorar as dependências de um reposi {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Gerenciar {% data variables.product.prodname_dependabot_alerts %} {% data variables.product.prodname_dependabot_alerts %} são gerados quando {% data variables.product.prodname_dotcom %} identifica uma dependência no gráfico de dependências com uma vulnerabilidade. {% ifversion fpt or ghec %}Você pode habilitar {% data variables.product.prodname_dependabot_alerts %} para qualquer repositório.{% endif %} @@ -75,11 +75,11 @@ Para obter mais informações, consulte "[Explorar as dependências de um reposi {% data reusables.dependabot.dependabot-alerts-beta %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" e "[Gerenciando configurações de segurança e análise da sua conta pessoal](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account){% endif %}". +For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account){% endif %}." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Gerenciando revisão de dependências A revisão de dependências permite visualizar alterações de dependência em pull requests antes de serem mescladas nos seus repositórios. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)". 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 e4c74991cf..380b010919 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 @@ -143,8 +143,8 @@ Antes de definir um padrão personalizado, você deverá garantir que você habi {% if secret-scanning-enterprise-dry-runs %} **Notas:** -- At the enterprise level, only the creator of a custom pattern can edit the pattern, and use it in a dry run. -- Enterprise owners can only make use of dry runs on repositories that they have access to, and enterprise owners do not necessarily have access to all the organizations or repositories within the enterprise. +- No nível corporativo, apenas o criador de um padrão personalizado pode editar o padrão e usá-lo em um teste. +- Os proprietários de empresas só podem usar testes em repositórios aos quais têm acesso, e os proprietários de empresas não têm necessariamente acesso a todas as organizações ou repositórios da empresa. {% else %} **Observação:** Como não há nenhuma funcionalidade de teste, recomendamos que você teste seus padrões personalizados em um repositório antes de defini-los para toda sua empresa. Dessa forma, você pode evitar criar alertas falsos-positivos de {% data variables.product.prodname_secret_scanning %}. diff --git a/translations/pt-BR/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md index af4fdf7245..378b254540 100644 --- a/translations/pt-BR/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md +++ b/translations/pt-BR/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md @@ -84,19 +84,19 @@ Se você confirmar que um segredo é real e pretender corrigi-lo mais tarde, voc 2. Tente novamente na linha de comando em três horas. Se não enviou por push em três horas, você terá de repetir este processo. {% if secret-scanning-push-protection-web-ui %} -## Using secret scanning as a push protection from the web UI +## Usando a digitalização de segredo como uma proteção de push da interface de usuário web -When you use the web UI to attempt to commit a supported secret to a repository or organization with secret scanning as a push protection enabled, {% data variables.product.prodname_dotcom %} will block the commit. You will see a banner at the top of the page with information about the secret's location, and the secret will also be underlined in the file so you can easily find it. +Ao usar a interface de usuário web para tentar confirmar um segredo suportado para um repositório ou organização com digitalização de segredo como uma proteção de push habilitada {% data variables.product.prodname_dotcom %} bloqueará o commit. Você verá um banner no topo da página com informações sobre a localização do segredo, e o segredo também será sublinhado no arquivo para que você possa encontrá-lo facilmente. - ![Screenshot showing commit in web ui blocked because of secret scanning push protection](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-blocked-banner.png) + ![Captura de tela que mostra o commit na interface de usuário da web bloqueado devido à proteção de push da digitalização de segredo](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-blocked-banner.png) -{% data variables.product.prodname_dotcom %} will only display one detected secret at a time in the web UI. Se um segredo específico já foi detectado no repositório e um alerta já existe, {% data variables.product.prodname_dotcom %} não bloqueará esse segredo. +{% data variables.product.prodname_dotcom %} só exibirá um segredo detectado por vez na interface do usuário. Se um segredo específico já foi detectado no repositório e um alerta já existe, {% data variables.product.prodname_dotcom %} não bloqueará esse segredo. -You can remove the secret from the file using the web UI. Once you remove the secret, the banner at the top of the page will change and tell you that you can now commit your changes. +Você pode remover o segredo do arquivo usando a interface de usuário da web. Depois de remover o segredo, o banner no topo da página mudará e dirá que agora você pode fazeer commit das suas alterações. - ![Screenshot showing commit in web ui allowed after secret fixed](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-allowed.png) + ![Captura de tela que mostra o commit na interface de usuário da web, permitido após correção do segredo](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-allowed.png) -### Bypassing push protection for a secret +### Ignorando a proteção de push para um segredo Se {% data variables.product.prodname_dotcom %} bloquear um segredo que você acredita ser seguro enviar por push, você poderá permitir o segredo e especificar a razão pela qual ele deve ser permitido. Se você confirmar que um segredo é real e pretender corrigi-lo mais tarde, você deverá procurar remediar o segredo o mais rápido possível. @@ -104,11 +104,11 @@ Se {% data variables.product.prodname_dotcom %} bloquear um segredo que você ac Se você confirmar que um segredo é real e pretender corrigi-lo mais tarde, você deverá procurar remediar o segredo o mais rápido possível. -1. In the banner that appeared at the top of the page when {% data variables.product.prodname_dotcom %} blocked your commit, click **Bypass protection**. +1. No banner que apareceu na parte suérior da página quando {% data variables.product.prodname_dotcom %} bloqueou o seu commit, clique em **Ignorar proteção**. {% data reusables.secret-scanning.push-protection-choose-allow-secret-options %} ![Captura de tela que mostra o formulário com opções para desbloquear o push de um segredo](/assets/images/help/repository/secret-scanning-push-protection-web-ui-allow-secret-options.png) -1. Click **Allow secret**. +1. Clique **Permitir segredo**. {% endif %} diff --git a/translations/pt-BR/content/code-security/secret-scanning/secret-scanning-patterns.md b/translations/pt-BR/content/code-security/secret-scanning/secret-scanning-patterns.md index 91c1a531ac..58d5c7ff34 100644 --- a/translations/pt-BR/content/code-security/secret-scanning/secret-scanning-patterns.md +++ b/translations/pt-BR/content/code-security/secret-scanning/secret-scanning-patterns.md @@ -42,7 +42,7 @@ O {% data variables.product.product_name %} atualmente verifica repositórios p Quando {% data variables.product.prodname_secret_scanning_GHAS %} está habilitado, {% data variables.product.prodname_dotcom %} digitalia os segredos emitidos pelos seguintes prestadores de serviços. {% ifversion ghec %}Para obter mais informações sobre {% data variables.product.prodname_secret_scanning_GHAS %}, consulte "[Sobre {% data variables.product.prodname_secret_scanning_GHAS %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)."{% endif %} -If you use the REST API for secret scanning, you can use the `Secret type` to report on secrets from specific issuers. Para obter mais informações, consulte "[Verificação de segredo](/enterprise-cloud@latest/rest/secret-scanning)". +Se você usar a API REST para a digitalização de segredo, você pode usar o tipo `tipo de segredo` para relatar segredos de emissores específicos. Para obter mais informações, consulte "[Verificação de segredo](/enterprise-cloud@latest/rest/secret-scanning)". {% ifversion ghes > 3.1 or ghae or ghec %} {% note %} 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 6616eef464..3a58cd7b19 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 @@ -1,13 +1,13 @@ --- title: Sobre a visão geral de segurança intro: 'Você pode visualizar, filtrar e classificar alertas de segurança para repositórios pertencentes à sua organização ou equipe em um só lugar: a página de Visão Geral de Segurança.' -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' redirect_from: - /code-security/security-overview/exploring-security-alerts versions: fpt: '*' - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' type: how_to @@ -22,7 +22,7 @@ topics: shortTitle: Sobre a visão geral de segurança --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} @@ -69,7 +69,7 @@ A nível da organização, a visão geral de segurança exibe informações de s {% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} ### Sobre a visão geral de segurança do nível da empresa -A nível da empresa, a visão geral de segurança exibe informações de segurança agregadas e específicas ao repositório para sua empresa. Você pode visualizar repositórios pertencentes à sua empresa que tenham alertas de segurança ou ver todos os alertas de {% data variables.product.prodname_secret_scanning %} de toda a sua empresa. +A nível da empresa, a visão geral de segurança exibe informações de segurança agregadas e específicas ao repositório para sua empresa. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise. Os proprietários da organização e os gerentes de segurança das organizações da sua empresa também têm acesso limitado à visão geral de segurança no nível da empresa. Eles só podem ver repositórios e alertas das organizações aos quais têm acesso total. diff --git a/translations/pt-BR/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index 4548816e2f..d0847f93aa 100644 --- a/translations/pt-BR/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/translations/pt-BR/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -1,10 +1,10 @@ --- title: Filtrando alertas na visão geral de segurança intro: Use os filtros para ver categorias específicas de alertas -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' versions: - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' type: how_to @@ -17,7 +17,7 @@ topics: shortTitle: Filtrando alertas --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} diff --git a/translations/pt-BR/content/code-security/security-overview/index.md b/translations/pt-BR/content/code-security/security-overview/index.md index 8c520114b9..22642f1d50 100644 --- a/translations/pt-BR/content/code-security/security-overview/index.md +++ b/translations/pt-BR/content/code-security/security-overview/index.md @@ -5,7 +5,7 @@ intro: 'Visualize, ordene e filtre os alertas de segurança de toda a sua organi product: '{% data reusables.gated-features.security-center %}' versions: fpt: '*' - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' topics: 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 e490537313..1a08c9984f 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 @@ -1,7 +1,7 @@ --- title: Visualizando a visão geral de segurança intro: Acesse as diferentes visualizações disponíveis na visão geral de segurança -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' versions: ghae: issue-5503 @@ -17,7 +17,7 @@ topics: shortTitle: Ver visão geral de segurança --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} @@ -28,7 +28,8 @@ 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. 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) +{% data reusables.organizations.security-overview-feature-specific-page %} + ![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 @@ -42,6 +43,9 @@ shortTitle: Ver visão geral de segurança {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} 1. Na barra lateral esquerda, clique em {% octicon "shield" aria-label="The shield icon" %} **Código de Segurança**. +{% if security-overview-feature-specific-alert-page %} +{% data reusables.organizations.security-overview-feature-specific-page %} +{% endif %} {% endif %} ## Visualizando alertas de um repositório diff --git a/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md b/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md index a46fa05837..be16d4e818 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md @@ -19,6 +19,8 @@ topics: Basicamente, a segurança de abastecimento de software de ponta a ponta consiste em garantir que o código que você distribui não tenha sido adulterado. Anteriormente, os invasores focaram em direcionar as dependências que você usa, por exemplo, bibliotecas e estruturas. Os invasores agora expandiram o seu foco para incluir as contas de usuários direcionadas e criar processos. Portanto, esses sistemas também devem ser defendidos. +For information about features in {% data variables.product.prodname_dotcom %} that can help you secure dependencies, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." + ## Sobre estes guias Esta série de guias explica como pensar em proteger sua cadeia de suprimentos de ponta a ponta: conta pessoal, código e processos de criação. Cada guia explica o risco para essa área e introduz as funcionalidades de {% data variables.product.product_name %} que podem ajudar você a resolver esse risco. diff --git a/translations/pt-BR/content/code-security/supply-chain-security/index.md b/translations/pt-BR/content/code-security/supply-chain-security/index.md index 613365f18f..a0949a1be6 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/index.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/index.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot 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 c530ab3754..73e0f80c88 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 @@ -6,7 +6,7 @@ shortTitle: Revisão de dependência versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -37,6 +37,8 @@ Para obter mais informações sobre como configurar uma revisão de dependência A revisão de dependências é compatível com as mesmas linguagens e os mesmos ecossistemas de gestão de pacotes do gráfico de dependência. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)". +For more information on supply chain features available on {% data variables.product.product_name %}, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." + {% ifversion ghec or ghes %} ## Habilitar revisão de dependências diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md index f4569b1322..3b692d1fa2 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -54,6 +54,10 @@ As outras funcionalidades da cadeia de suprimentos em {% data variables.product. Os dados de dependência de referência cruzada de {% data variables.product.prodname_dependabot %} fornecidos pelo gráfico de dependências com a lista de vulnerabilidades conhecidas publicadas no {% data variables.product.prodname_advisory_database %}, verifica suas dependências e gera {% data variables.product.prodname_dependabot_alerts %} quando uma potencial vulnerabilidade é detectada. {% endif %} +{% ifversion fpt or ghec or ghes %} +For best practice guides on end-to-end supply chain security including the protection of personal accounts, code, and build processes, see "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)." +{% endif %} + ## Visão geral de recursos ### Qual é o gráfico de dependências @@ -128,7 +132,7 @@ Para obter mais informações sobre {% data variables.product.prodname_dependabo Repositórios públicos: - **Gráfico de dependência**—habilitado por padrão e não pode ser desabilitado. - **Revisão de dependência**—habilitado por padrão e não pode ser desabilitado. -- **{% data variables.product.prodname_dependabot_alerts %}**—não habilitado por padrão. {% data variables.product.prodname_dotcom %} detecta dependências vulneráveis e exibe informações no gráfico de dependência, mas não gera {% data variables.product.prodname_dependabot_alerts %} por padrão. Os proprietários do repositório ou pessoas com acesso de administrador podem habilitar {% data variables.product.prodname_dependabot_alerts %}. Você também pode habilitar ou desabilitar alertas do Dependabot para todos os repositórios pertencentes à sua conta de usuário ou organização. Para obter mais informações, consulte "[Gerenciando configurações de segurança e análise da sua conta de usuário](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account)" ou "[Gerenciando configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)". +- **{% data variables.product.prodname_dependabot_alerts %}**—não habilitado por padrão. {% data variables.product.prodname_dotcom %} detecta dependências vulneráveis e exibe informações no gráfico de dependência, mas não gera {% data variables.product.prodname_dependabot_alerts %} por padrão. Os proprietários do repositório ou pessoas com acesso de administrador podem habilitar {% data variables.product.prodname_dependabot_alerts %}. Você também pode habilitar ou desabilitar alertas do Dependabot para todos os repositórios pertencentes à sua conta de usuário ou organização. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." Repositórios privados: - **Gráfico de dependência**—não habilitado por padrão. O recurso pode ser habilitado pelos administradores do repositório. Para obter mais informações, consulte "[Explorar as dependências de um repositório](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)". @@ -137,7 +141,7 @@ Repositórios privados: {% elsif ghec %} - **Revisão de dependência**— disponível em repositórios privados pertencentes a organizações, desde que você tenha uma licença para {% data variables.product.prodname_GH_advanced_security %} e o gráfico de dependências habilitado. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" e "[Explorando as dependências de um repositório](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)". {% endif %} -- **{% data variables.product.prodname_dependabot_alerts %}**—não habilitado 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. Você também pode habilitar ou desabilitar alertas do Dependabot para todos os repositórios pertencentes à sua conta de usuário ou organização. Para obter mais informações, consulte "[Gerenciando configurações de segurança e análise da sua conta de usuário](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account)" ou "[Gerenciando configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)". +- **{% data variables.product.prodname_dependabot_alerts %}**—não habilitado 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. Você também pode habilitar ou desabilitar alertas do Dependabot para todos os repositórios pertencentes à sua conta de usuário ou organização. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." Qualquer tipo de repositório: - **{% data variables.product.prodname_dependabot_security_updates %}**—não habilitado por padrão. É possível habilitar o {% data variables.product.prodname_dependabot_security_updates %} para qualquer repositório que use {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. Para obter mais informações sobre habilitar atualizações de segurança, consulte "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)." 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 aa1401c472..55c2f326f8 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 @@ -7,7 +7,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -45,6 +45,8 @@ O gráfico de dependências inclui todas as dependências de um repositório det O gráfico de dependências identifica as dependências indiretas{% ifversion fpt or ghec %} explicitamente a partir de um arquivo de bloqueio ou verificando as dependências das suas dependências diretas. Para o gráfico mais confiável, você deve usar os arquivos de bloqueio (ou o equivalente deles), pois definem exatamente quais versões das dependências diretas e indiretas você usa atualmente. Se você usar arquivos de bloqueio, você também terá certeza de que todos os contribuidores do repositório usarão as mesmas versões, o que facilitará para você testar e depurar o código{% else %} dos arquivos de bloqueio{% endif %}. +For more information on how {% data variables.product.product_name %} helps you understand the dependencies in your environment, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." + {% ifversion fpt or ghec %} ## Dependentes incluídos diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md index 1a4c7ee249..c5514279a6 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md @@ -5,7 +5,7 @@ shortTitle: Configurar a revisão de dependências versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -35,7 +35,7 @@ Revisão de dependências está incluída em {% data variables.product.product_n {% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %} 1. Se "{% data variables.product.prodname_GH_advanced_security %} não estiver ativado, clique em **Habilitar ** ao lado do recurso. ![Captura de tela do recurso do GitHub Advanced Security com o botão "Habilitar" destacado](/assets/images/help/security/enable-ghas-private-repo.png) -{% elsif ghes or ghae %} +{% elsif ghes %} A revisão de dependências está disponível quando o gráfico de dependências está habilitado para {% data variables.product.product_location %} e {% data variables.product.prodname_advanced_security %} está habilitado para a organização ou repositório. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_GH_advanced_security %} para a sua empresa](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)." ### Verificando se o gráfico de dependências está habilitado diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md index ff240dd8cb..9849069a9d 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md @@ -6,7 +6,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -25,7 +25,7 @@ Para obter mais informações, consulte "[Sobre o gráfico de dependência](/cod {% ifversion fpt or ghec %} ## Sobre a configuração do gráfico de dependências {% endif %} {% ifversion fpt or ghec %}Para gerar um gráfico de dependência, o {% data variables.product.product_name %} precisa de acesso somente leitura ao manifesto dependência e aos arquivos de bloqueio em um repositório. O gráfico de dependências é gerado automaticamente para todos os repositórios públicos e você pode optar por habilitá-lo para repositórios privados. Para obter mais informações sobre a visualização do gráfico de dependências, consulte "[Explorando as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)".{% endif %} -{% ifversion ghes or ghae %} ## Habilitando o gráfico de dependências +{% ifversion ghes %} ## Habilitando o gráfico de dependências {% data reusables.dependabot.ghes-ghae-enabling-dependency-graph %}{% endif %}{% ifversion fpt or ghec %} ### Habilitar e desabilitar o gráfico de dependências para um repositório privado diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index a2926385db..d0c9686095 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -12,7 +12,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md index 2f80b39d41..dfc92f360b 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md @@ -3,7 +3,7 @@ title: Entender sua cadeia de suprimentos de software versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependency graph diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md index a20d9100f4..3873c3458d 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md @@ -5,7 +5,7 @@ shortTitle: Solucionar problemas do gráfico de dependências versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md index 78c4d2743c..ec256a7367 100644 --- a/translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md @@ -42,7 +42,7 @@ Embora esta opção não configure um ambiente de desenvolvimento para você, el ## Opção 4: Usar contêineres remotos e o Docker para um ambiente contêinerizado local -Se seu repositório tiver um `devcontainer.json`, considere o uso da [extensão Remote-Containers](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) no Visual Studio Code para criar e anexar a um contêiner de desenvolvimento local para seu repositório. O tempo de configuração desta opção irá variar dependendo das suas especificações locais e da complexidade da configuração do seu contêiner de desenvolvimento. +If your repository has a `devcontainer.json`, consider using the [Remote-Containers extension](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) in {% data variables.product.prodname_vscode %} to build and attach to a local development container for your repository. O tempo de configuração desta opção irá variar dependendo das suas especificações locais e da complexidade da configuração do seu contêiner de desenvolvimento. {% note %} diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/security-in-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/security-in-codespaces.md index 0dc1008dee..f783922601 100644 --- a/translations/pt-BR/content/codespaces/codespaces-reference/security-in-codespaces.md +++ b/translations/pt-BR/content/codespaces/codespaces-reference/security-in-codespaces.md @@ -34,7 +34,7 @@ Cada codespace tem a sua própria rede virtual isolada. Usamos firewalls para bl ### Autenticação -Você pode se conectar a um codespace usando um navegador da web ou o Visual Studio Code. Se você se conectar a partir do Visual Studio Code, será solicitado que você efetue a autenticação com {% data variables.product.product_name %}. +You can connect to a codespace using a web browser or from {% data variables.product.prodname_vscode %}. If you connect from {% data variables.product.prodname_vscode_shortname %}, you are prompted to authenticate with {% data variables.product.product_name %}. Toda vez que um codespace é criado ou reiniciado, atribui-se um novo token de {% data variables.product.company_short %} com um período de vencimento automático. Este período permite que você trabalhe no código sem precisar efetuar a autenticação novamente durante um dia de trabalho típico, mas reduz a chance de deixar uma conexão aberta quando você parar de usar o codespace. @@ -109,4 +109,4 @@ Certos recursos de desenvolvimento podem potencialmente adicionar risco ao seu a #### Usando extensões -Qualquer extensão adicional de {% data variables.product.prodname_vscode %} que você tenha instalado pode potencialmente introduzir mais risco. Para ajudar a mitigar esse risco, certifique-se de que você só instale extensões confiáveis, e que elas sejam sempre atualizadas. +Qualquer extensão adicional de {% data variables.product.prodname_vscode_shortname %} que você tenha instalado pode potencialmente introduzir mais risco. Para ajudar a mitigar esse risco, certifique-se de que você só instale extensões confiáveis, e que elas sejam sempre atualizadas. diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md index e8e99ffe56..a88957477f 100644 --- a/translations/pt-BR/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md +++ b/translations/pt-BR/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md @@ -17,7 +17,7 @@ redirect_from: ## Usar {% data variables.product.prodname_copilot %} -[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), um programador de par de IA pode ser usado em qualquer codespace. Para começar a usar {% data variables.product.prodname_copilot_short %} em {% data variables.product.prodname_codespaces %}, instale a [ extensão de {% data variables.product.prodname_copilot_short %} a partir do marketplace de {% data variables.product.prodname_vscode %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). +[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), um programador de par de IA pode ser usado em qualquer codespace. To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). Para incluir o {% data variables.product.prodname_copilot_short %}, ou outras extensões, em todos os seus codespaces, habilite a sincronização de Configurações. Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)". Além disso, para incluir {% data variables.product.prodname_copilot_short %} em um determinado projeto para todos os usuários, você pode especificar `GitHub.copilot` como uma extensão no seu arquivo `devcontainer.json`. Para obter informações sobre a configuração de um arquivo `devcontainer.json`, consulte "[Introdução aos contêineres de desenvolvimento](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)". diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md index b6d17c4612..61b803cc11 100644 --- a/translations/pt-BR/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md +++ b/translations/pt-BR/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md @@ -15,13 +15,13 @@ redirect_from: - /codespaces/codespaces-reference/using-the-command-palette-in-codespaces --- -## Sobre a Paleta de Comando de {% data variables.product.prodname_vscode %} +## Sobre o {% data variables.product.prodname_vscode_command_palette %} -A Paleta de Comando é uma das funcionalidades principais de {% data variables.product.prodname_vscode %} e está disponível para uso em codespaces. O {% data variables.product.prodname_vscode_command_palette %} permite que você acesse muitos comandos para {% data variables.product.prodname_codespaces %} e {% data variables.product.prodname_vscode %}. Para obter mais informações sobre como usar o {% data variables.product.prodname_vscode_command_palette %}, consulte "[Interface do usuário](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" na documentação do Visual Studio Code. +A Paleta de Comando é uma das funcionalidades principais de {% data variables.product.prodname_vscode %} e está disponível para uso em codespaces. O {% data variables.product.prodname_vscode_command_palette %} permite que você acesse muitos comandos para {% data variables.product.prodname_codespaces %} e {% data variables.product.prodname_vscode_shortname %}. For more information on using the {% data variables.product.prodname_vscode_command_palette_shortname %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the {% data variables.product.prodname_vscode_shortname %} documentation. -## Acessando o {% data variables.product.prodname_vscode_command_palette %} +## Acessando o {% data variables.product.prodname_vscode_command_palette_shortname %} -Você pode acessar o {% data variables.product.prodname_vscode_command_palette %} de várias maneiras. +Você pode acessar o {% data variables.product.prodname_vscode_command_palette_shortname %} de várias maneiras. - Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux). @@ -33,7 +33,7 @@ Você pode acessar o {% data variables.product.prodname_vscode_command_palette % ## Comandos para {% data variables.product.prodname_github_codespaces %} -Para ver todos os comandos relacionados a {% data variables.product.prodname_github_codespaces %}, [acesse o {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette) e, em seguida, comece a digitar "Codespaces". +Para ver todos os comandos relacionados a {% data variables.product.prodname_github_codespaces %}, [acesse o {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette) e, em seguida, comece a digitar "Codespaces". ![Uma lista de todos os comandos que se referem a codespaces](/assets/images/help/codespaces/codespaces-command-palette.png) @@ -41,13 +41,13 @@ Para ver todos os comandos relacionados a {% data variables.product.prodname_git Se você adicionar um novo segredo ou alterar o tipo de máquina, você terá que parar e reiniciar o codespace para que aplique suas alterações. -Para suspender ou interromper o contêiner do seu codespace, [acesse o {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette)e, em seguida, comece a digitar "parar". Selecione **Codespaces: Parar o codespace atual**. +Para suspender ou interromper o contêiner do seu codespace, [acesse o {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette)e, em seguida, comece a digitar "parar". Selecione **Codespaces: Parar o codespace atual**. ![Comando para parar um codespace](/assets/images/help/codespaces/codespaces-stop.png) ### Adicionando um contêiner de desenvolvimento a partir de um modelo -Para adicionar um contêiner de desenvolvimento a partir de um modelo, [acesse o {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette) e, em seguida, comece a digitar "dev container". Selecione **Codespaces: Adicionar arquivos de configuração de Contêiner do Desenvolvimento...** +Para adicionar um contêiner de desenvolvimento a partir de um modelo, [acesse o {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette) e, em seguida, comece a digitar "dev container". Selecione **Codespaces: Adicionar arquivos de configuração de Contêiner do Desenvolvimento...** ![Comando para adicionar um contêiner de desenvolvimento](/assets/images/help/codespaces/add-prebuilt-container-command.png) @@ -55,14 +55,14 @@ Para adicionar um contêiner de desenvolvimento a partir de um modelo, [acesse o Se você adicionar um contêiner de desenvolvimento ou editar qualquer um dos arquivos de configuração (`devcontainer.json` e `arquivo Docker`), você terá que reconstruir seu codespace para aplicar suas alterações. -Para reconstruir seu contêiner, [acesse o {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette)e, em seguida, comece a digitar "recriar". Selecione **Codespaces: Reconstruir Contêiner**. +Para reconstruir seu contêiner, [acesse o {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette)e, em seguida, comece a digitar "recriar". Selecione **Codespaces: Reconstruir Contêiner**. ![Comando para reconstruir um codespace](/assets/images/help/codespaces/codespaces-rebuild.png) ### Registros de codespaces -Você pode usar o {% data variables.product.prodname_vscode_command_palette %} para acessar os registros de criação do codespace ou você pode usá-lo para exportar todos os registros. +Você pode usar o {% data variables.product.prodname_vscode_command_palette_shortname %} para acessar os registros de criação do codespace ou você pode usá-lo para exportar todos os registros. -Para recuperar os registros para os codespaces, [acesse o {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette)e, em seguida, comece a digitar "registro". Selecione **Codespaces: Exportar registros** para exportar todos os registros relacionados aos codespaces ou selecione **Codespaces: Visualizar o registro de criação** para visualizar os registros relacionados à configuração. +Para recuperar os registros para os codespaces, [acesse o {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette)e, em seguida, comece a digitar "registro". Selecione **Codespaces: Exportar registros** para exportar todos os registros relacionados aos codespaces ou selecione **Codespaces: Visualizar o registro de criação** para visualizar os registros relacionados à configuração. ![Comando para acessar os registros](/assets/images/help/codespaces/codespaces-logs.png) diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md index a2f6f49239..25637208e5 100644 --- a/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md @@ -12,7 +12,7 @@ shortTitle: Definir o tempo limite Um codespace irá parar de funcionar após um período de inatividade. Você pode especificar a duração deste período de tempo limite. A configuração atualizada será aplicada a qualquer código recém-criado. -Some organizations may have a maximum idle timeout policy. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting, and you will be notified of this after the codespace is created. For more information, see "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." +Algumas organizações podem ter uma política máxima de tempo ocioso. Se a política de uma organização definir um tempo limite máximo que seja menor do que o tempo limite padrão definido o tempo limite da organização será usado em vez da sua configuração, e você será notificado disso após a criação do codespace. Para obter mais informações, consulte "[Restringindo o período de tempo ocioso de](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)". {% warning %} diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 1082dfd203..07886721b7 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -35,7 +35,7 @@ Para obter mais informações sobre o que acontece quando você cria um codespac Para obter mais informações sobre o ciclo de vida de um codespace, consulte "[Ciclo de vida dos codespaces](/codespaces/developing-in-codespaces/codespaces-lifecycle)". -Se você quiser usar hooks do Git para o seu código, você deverá configurar hooks usando os scritps do ciclo de vida do de [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), como `postCreateCommand`, durante a etapa 4. Uma vez que o seu contêiner de codespace é criado depois que o repositório é clonado, qualquer [diretório de template do git](https://git-scm.com/docs/git-init#_template_directory) configurado na imagem do contêiner não será aplicado ao seu codespace. Os Hooks devem ser instalados depois que o codespace for criado. Para obter mais informações sobre como usar `postCreateCommand`, consulte a referência [`devcontainer.json` ](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) na documentação do Visual Studio Code. +Se você quiser usar hooks do Git para o seu código, você deverá configurar hooks usando os scritps do ciclo de vida do de [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), como `postCreateCommand`, durante a etapa 4. Uma vez que o seu contêiner de codespace é criado depois que o repositório é clonado, qualquer [diretório de template do git](https://git-scm.com/docs/git-init#_template_directory) configurado na imagem do contêiner não será aplicado ao seu codespace. Os Hooks devem ser instalados depois que o codespace for criado. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.codespaces.use-visual-studio-features %} diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md index fe80043687..bc4e24bf1d 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md @@ -33,7 +33,7 @@ shortTitle: Desenvolver em um codespace 4. Painéis - É aqui que você pode visualizar as informações de saída e depuração, bem como o local padrão para o Terminal integrado. 5. Barra de Status - Esta área fornece informações úteis sobre seu codespace e projeto. Por exemplo, o nome da agência, portas configuradas e muito mais. -Para obter mais informações sobre como usar {% data variables.product.prodname_vscode %}, consulte o [Guia da Interface do Usuário](https://code.visualstudio.com/docs/getstarted/userinterface) na documentação de {% data variables.product.prodname_vscode %} +Para obter mais informações sobre como usar {% data variables.product.prodname_vscode_shortname %}, consulte o [Guia da Interface do Usuário](https://code.visualstudio.com/docs/getstarted/userinterface) na documentação de {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.connect-to-codespace-from-vscode %} @@ -54,7 +54,7 @@ Para obter mais informações sobre como usar {% data variables.product.prodname ### Usando o {% data variables.product.prodname_vscode_command_palette %} -O {% data variables.product.prodname_vscode_command_palette %} permite que você acesse e gerencie muitas funcionalidades para {% data variables.product.prodname_codespaces %} e {% data variables.product.prodname_vscode %}. Para obter mais informações, consulte "[Usando o {% data variables.product.prodname_vscode_command_palette %} em {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)". +O {% data variables.product.prodname_vscode_command_palette %} permite que você acesse e gerencie muitas funcionalidades para {% data variables.product.prodname_codespaces %} e {% data variables.product.prodname_vscode_shortname %}. Para obter mais informações, consulte "[Usando o {% data variables.product.prodname_vscode_command_palette_shortname %} em {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)". ## Acessar um codespace existente diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md index c6bc888387..470dc14044 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md @@ -20,17 +20,17 @@ shortTitle: Visual Studio Code ## Sobre {% data variables.product.prodname_codespaces %} em {% data variables.product.prodname_vscode %} -Você pode usar sua instalação local de {% data variables.product.prodname_vscode %} para criar, gerenciar, trabalhar e excluir codespaces. Para usar {% data variables.product.prodname_codespaces %} em {% data variables.product.prodname_vscode %}, você deverá instalar a extensão de {% data variables.product.prodname_github_codespaces %}. Para obter mais informações sobre a configuração de codespaces em {% data variables.product.prodname_vscode %}, consulte "[pré-requisitos](#prerequisites)". +Você pode usar sua instalação local de {% data variables.product.prodname_vscode %} para criar, gerenciar, trabalhar e excluir codespaces. Para usar {% data variables.product.prodname_codespaces %} em {% data variables.product.prodname_vscode_shortname %}, você deverá instalar a extensão de {% data variables.product.prodname_github_codespaces %}. Para obter mais informações sobre a configuração de codespaces em {% data variables.product.prodname_vscode_shortname %}, consulte "[pré-requisitos](#prerequisites)". -Por padrão, se você criar um novo codespace em {% data variables.product.prodname_dotcom_the_website %}, ele será aberto no navegador. Se você preferir abrir qualquer codespace novo em {% data variables.product.prodname_vscode %} automaticamente, você pode definir seu editor padrão como {% data variables.product.prodname_vscode %}. Para obter mais informações, consulte "[Definindo seu editor padrão para {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)". +Por padrão, se você criar um novo codespace em {% data variables.product.prodname_dotcom_the_website %}, ele será aberto no navegador. Se você preferir abrir qualquer codespace novo em {% data variables.product.prodname_vscode_shortname %} automaticamente, você pode definir seu editor padrão como {% data variables.product.prodname_vscode_shortname %}. Para obter mais informações, consulte "[Definindo seu editor padrão para {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)". -Se você preferir trabalhar no navegador, mas deseja continuar usando suas extensões de {% data variables.product.prodname_vscode %} temas e atalhos existentes, você poderá ativar as Configurações Sincronizadas. Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)". +Se você preferir trabalhar no navegador, mas deseja continuar usando suas extensões de {% data variables.product.prodname_vscode_shortname %} temas e atalhos existentes, você poderá ativar as Configurações Sincronizadas. Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)". ## Pré-requisitos -Para desenvolver-se em uma plataforma de codespace diretamente em {% data variables.product.prodname_vscode %}, você deverá instalar e efetuar o login na extensão {% data variables.product.prodname_github_codespaces %} com as suas credenciais de {% data variables.product.product_name %}. A extensão de {% data variables.product.prodname_github_codespaces %} exige a versão de outubro de 2020 1.51 ou posterior de {% data variables.product.prodname_vscode %}. +Para desenvolver-se em uma plataforma de codespace diretamente em {% data variables.product.prodname_vscode_shortname %}, você deverá instalar e efetuar o login na extensão {% data variables.product.prodname_github_codespaces %} com as suas credenciais de {% data variables.product.product_name %}. A extensão de {% data variables.product.prodname_github_codespaces %} exige a versão de outubro de 2020 1.51 ou posterior de {% data variables.product.prodname_vscode_shortname %}. -Use o {% data variables.product.prodname_vs %} Marketplace para instalar a extensão [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). Para obter mais informações, consulte [Extensão do Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) na documentação do {% data variables.product.prodname_vscode %}. +Use the {% data variables.product.prodname_vscode_marketplace %} to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. Para obter mais informações, consulte [Extensão do Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) na documentação do {% data variables.product.prodname_vscode_shortname %}. {% mac %} @@ -40,8 +40,8 @@ Use o {% data variables.product.prodname_vs %} Marketplace para instalar a exten ![Registrar-se para visualizar {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -1. Para autorizar o {% data variables.product.prodname_vscode %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**. -1. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão. +2. Para autorizar o {% data variables.product.prodname_vscode_shortname %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**. +3. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão. {% endmac %} @@ -56,28 +56,28 @@ Use o {% data variables.product.prodname_vs %} Marketplace para instalar a exten ![Registrar-se para visualizar {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -1. Para autorizar o {% data variables.product.prodname_vscode %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**. +1. Para autorizar o {% data variables.product.prodname_vscode_shortname %} a acessar sua conta no {% data variables.product.product_name %}, clique em **Permitir**. 1. Registre-se e, {% data variables.product.product_name %} para aprovar a extensão. {% endwindows %} -## Criar um codespace em {% data variables.product.prodname_vscode %} +## Criar um codespace em {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.creating-a-codespace-in-vscode %} -## Abrir um codespace em {% data variables.product.prodname_vscode %} +## Abrir um codespace em {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 1. Em "Codedespaces", clique no código que você deseja desenvolver. 1. Clique no ícone Conectar-se ao Codespace. - ![Ícone de conectar-se a um Codespace em {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) + ![Ícone de conectar-se a um Codespace em {% data variables.product.prodname_vscode_shortname %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) -## Alterar o tipo da máquina em {% data variables.product.prodname_vscode %} +## Alterar o tipo da máquina em {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.codespaces-machine-types %} Você pode alterar o tipo de máquina do seu codespace a qualquer momento. -1. Em {% data variables.product.prodname_vscode %}, abra a Paleta de Comando (`shift comando P` / `shift control P`). +1. Em {% data variables.product.prodname_vscode_shortname %}, abra a Paleta de Comando (`shift comando P` / `shift control P`). 1. Pesquise e selecione "Codespaces: Alterar tipo de máquina." ![Pesquisar um branch para criar um novo {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png) @@ -100,13 +100,13 @@ Use o {% data variables.product.prodname_vs %} Marketplace para instalar a exten Se você clicar em **Não**, ou se o código não estiver em execução, a alteração entrará em vigor na próxima vez que o codespace for reiniciado. -## Excluir um codespace em {% data variables.product.prodname_vscode %} +## Excluir um codespace em {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.deleting-a-codespace-in-vscode %} -## Alternando para a compilação de Insiders de {% data variables.product.prodname_vscode %} +## Alternando para a compilação de Insiders de {% data variables.product.prodname_vscode_shortname %} -Você pode usar o [Insiders Build do Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) em {% data variables.product.prodname_codespaces %}. +You can use the [Insiders Build of {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_codespaces %}. 1. Na parte inferior esquerda da sua janela {% data variables.product.prodname_codespaces %}, selecione **Configurações de {% octicon "gear" aria-label="The settings icon" %}**. 2. Na lista, selecione "Alternar para Versão de Insiders". diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md index 9b886c0f41..8ef08fc4f5 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md @@ -24,6 +24,7 @@ Você pode trabalhar com {% data variables.product.prodname_codespaces %} em {% - [Excluir um codespace](#delete-a-codespace) - [SSH em um codespace](#ssh-into-a-codespace) - [Abrir um codespace em {% data variables.product.prodname_vscode %}](#open-a-codespace-in-visual-studio-code) +- [Open a codespace in JupyterLab](#open-a-codespace-in-jupyterlab) - [Copiar um arquivo de/para um codespace](#copy-a-file-tofrom-a-codespace) - [Modificar portas em um codespace](#modify-ports-in-a-codespace) - [Acessar registros de codespaces](#access-codespace-logs) @@ -109,6 +110,12 @@ gh codespace code -c codespace-name Para obter mais informações, consulte "[Usando {% data variables.product.prodname_codespaces %} em {% data variables.product.prodname_vscode %}de](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code)". +### Open a codespace in JupyterLab + +```shell +gh codespace jupyter -c codespace-name +``` + ### Copiar um arquivo de/para um codespace ```shell diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md index 87ff35dfd8..8ef15630fa 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md @@ -19,7 +19,7 @@ shortTitle: controle de origem Você pode executar todas as ações do Git necessárias diretamente no seu codespace. Por exemplo, é possível obter alterações do repositório remoto, alternar os branches, criar um novo branch, fazer commit, fazer push e criar um pull request. Você pode usar o terminal integrado dentro do seu codespace para inserir nos comandos do Git, ou você pode clicar em ícones e opções de menu para realizar todas as tarefas mais comuns do Git. Este guia explica como usar a interface gráfica de usuário para controle de origem. -O controle de origem em {% data variables.product.prodname_github_codespaces %} usa o mesmo fluxo de trabalho que {% data variables.product.prodname_vscode %}. Para obter mais informações, consulte a documentação {% data variables.product.prodname_vscode %}"[Usando Controle de Versão no Código VS](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)". +O controle de origem em {% data variables.product.prodname_github_codespaces %} usa o mesmo fluxo de trabalho que {% data variables.product.prodname_vscode %}. For more information, see the {% data variables.product.prodname_vscode_shortname %} documentation "[Using Version Control in {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)." Um fluxo de trabalho típico para atualizar um arquivo que usa {% data variables.product.prodname_github_codespaces %} seria: diff --git a/translations/pt-BR/content/codespaces/getting-started/deep-dive.md b/translations/pt-BR/content/codespaces/getting-started/deep-dive.md index 7d6e1cee13..49fab2e9af 100644 --- a/translations/pt-BR/content/codespaces/getting-started/deep-dive.md +++ b/translations/pt-BR/content/codespaces/getting-started/deep-dive.md @@ -46,13 +46,13 @@ Uma vez que seu repositório é clonado na VM de host antes da criação do cont ### Etapa 3: Conectando-se ao codespace -Quando seu contêiner for criado e qualquer outra inicialização for executada, você estará conectado ao seu codespace. Você pode conectar-se por meio da web ou via [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), ou ambos, se necessário. +Quando seu contêiner for criado e qualquer outra inicialização for executada, você estará conectado ao seu codespace. You can connect to it through the web or via [{% data variables.product.prodname_vscode_shortname %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed. ### Passo 4: Configuração de pós-criação Uma vez que você estiver conectado ao seu codespace, a sua configuração automatizada poderá continuar compilando com base na configuração que você especificou no seu arquivo `devcontainer.json`. Você pode ver `postCreateCommand` e `postAttachCommand` serem executados. -Se vocÊ quiser usar os hooks do Git no seu codespace, configure os hooks usando os scripts do ciclo de vida do [`devcontainer.json` ](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts) como, por exemplo, `postCreateCommand`. Para obter mais informações, consulte o [`devcontainer.json` referência](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) na documentação do Visual Studio Code. +Se vocÊ quiser usar os hooks do Git no seu codespace, configure os hooks usando os scripts do ciclo de vida do [`devcontainer.json` ](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts) como, por exemplo, `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. Se você tiver um repositório de dotfiles público para {% data variables.product.prodname_codespaces %}, você poderá habilitá-lo para uso com novos codespaces. Quando habilitado, seus dotfiles serão clonados para o contêiner e o script de instalação será invocado. Para obter mais informações, consulte "[Personalizar {% data variables.product.prodname_codespaces %} para sua conta](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)". @@ -67,7 +67,7 @@ Durante a configuração de pós-criação, você ainda poderá usar o terminal {% note %} -**Observação:** As mudanças em um codespace em {% data variables.product.prodname_vscode %} não são salvas automaticamente, a menos que você tenha habilitado o [Salvamento automático](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). +**Observação:** As mudanças em um codespace em {% data variables.product.prodname_vscode_shortname %} não são salvas automaticamente, a menos que você tenha habilitado o [Salvamento automático](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). {% endnote %} ### Fechando ou interrompendo seu codespace @@ -93,7 +93,7 @@ A execução do seu aplicativo ao chegar pela primeira vez no seu codespace pode ## Enviando e fazendo push das suas alterações -O Git está disponível por padrão no seu codespace. Portanto, você pode confiar no fluxo de trabalho do Git existente. Você pode trabalhar com o Git no seu codespace por meio do Terminal ou usando a interface de usuário do controle de origem do [do Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol). Para obter mais informações, consulte "[Usando controle de origem no seu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" +O Git está disponível por padrão no seu codespace. Portanto, você pode confiar no fluxo de trabalho do Git existente. You can work with Git in your codespace either via the Terminal or by using [{% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. Para obter mais informações, consulte "[Usando controle de origem no seu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" ![Executando o status do git no terminal do codespaces](/assets/images/help/codespaces/git-status.png) @@ -107,9 +107,9 @@ Você pode criar um codespace a partir de qualquer branch, commit ou pull reques ## Personalizando seu codespace com extensões -Usar {% data variables.product.prodname_vscode %} no seu codespace dá acesso ao Marketplace de {% data variables.product.prodname_vscode %} para que você possa adicionar todas as extensões de que precisar. Para obter informações de como as extensões são executadas em {% data variables.product.prodname_codespaces %}, consulte [Suporte ao Desenvolvimento Remoto e aos codespaces do GitHub](https://code.visualstudio.com/api/advanced-topics/remote-extensions) na documentação de {% data variables.product.prodname_vscode %}. +Using {% data variables.product.prodname_vscode_shortname %} in your codespace gives you access to the {% data variables.product.prodname_vscode_marketplace %} so that you can add any extensions you need. Para obter informações de como as extensões são executadas em {% data variables.product.prodname_codespaces %}, consulte [Suporte ao Desenvolvimento Remoto e aos codespaces do GitHub](https://code.visualstudio.com/api/advanced-topics/remote-extensions) na documentação de {% data variables.product.prodname_vscode_shortname %}. -Se você já usa o {% data variables.product.prodname_vscode %}, você pode usar as [Sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync) para sincronizar automaticamente as extensões, configurações, temas, e atalhos de teclado entre sua instância local e todos {% data variables.product.prodname_codespaces %} que você criar. +Se você já usa o {% data variables.product.prodname_vscode_shortname %}, você pode usar as [Sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync) para sincronizar automaticamente as extensões, configurações, temas, e atalhos de teclado entre sua instância local e todos {% data variables.product.prodname_codespaces %} que você criar. ## Leia mais diff --git a/translations/pt-BR/content/codespaces/getting-started/quickstart.md b/translations/pt-BR/content/codespaces/getting-started/quickstart.md index 862cc4ff01..e439816d58 100644 --- a/translations/pt-BR/content/codespaces/getting-started/quickstart.md +++ b/translations/pt-BR/content/codespaces/getting-started/quickstart.md @@ -72,7 +72,7 @@ Agora que você fez algumas alterações, você poderá usar o terminal integrad ## Personalizando com uma extensão -Dentro de um codespace, você tem acesso ao Marketplace do Visual Studio Code. Para este exemplo, você instalará uma extensão que altera o tema, mas você pode instalar qualquer extensão que seja útil para o seu fluxo de trabalho. +Within a codespace, you have access to the {% data variables.product.prodname_vscode_marketplace %}. Para este exemplo, você instalará uma extensão que altera o tema, mas você pode instalar qualquer extensão que seja útil para o seu fluxo de trabalho. 1. Na barra lateral esquerda, clique no ícone Extensões. @@ -84,7 +84,7 @@ Dentro de um codespace, você tem acesso ao Marketplace do Visual Studio Code. P ![Selecionar tema fairyfloss](/assets/images/help/codespaces/fairyfloss.png) -4. As alterações feitas na configuração do seu ditor editor no codespace atual, como ligações de tema e teclado, são sincronizadas automaticamente por meio da [Sincronização das Configurações](https://code.visualstudio.com/docs/editor/settings-sync) para qualquer outro codespace que você abrir e quaisquer instâncias do Visual Studio Code que estiverem conectadas à sua conta do GitHub. +4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to any other codespaces you open and any instances of {% data variables.product.prodname_vscode %} that are signed into your GitHub account. ## Próximos passos diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md index 6c4acf22e1..f438c97607 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md @@ -35,7 +35,7 @@ Por padrão, um codespace só pode acessar o repositório no qual ele foi criado {% ifversion fpt %} {% note %} -**Note:** If you are a verified educator or a teacher, you must enable {% data variables.product.prodname_codespaces %} from a {% data variables.product.prodname_classroom %} to use your {% data variables.product.prodname_codespaces %} Education benefit. For more information, see "[Using GitHub Codespaces with GitHub Classroom](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#about-the-codespaces-education-benefit-for-verified-teachers)." +**Nota:** Se você for um educador ou professor verificado, você deverá habilitar {% data variables.product.prodname_codespaces %} a partir de um {% data variables.product.prodname_classroom %} para usar o seu benefício de educação de {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Usando os codespaces do GitHub com GitHub Classroom](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#about-the-codespaces-education-benefit-for-verified-teachers)". {% endnote %} {% endif %} 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 882dc68f3a..f18687ac03 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 @@ -41,7 +41,7 @@ Você também pode limitar os usuários individuais que podem usar {% data varia ## Excluindo codespaces não utilizados -Seus usuários podem excluir seus codespaces em https://github.com/codespaces e no Visual Studio Code. Para reduzir o tamanho de um codespace, os usuários podem excluir arquivos manualmente usando o terminal ou no Visual Studio Code. +Your users can delete their codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, users can manually delete files using the terminal or from within {% data variables.product.prodname_vscode_shortname %}. {% note %} 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 12d9944b12..3498a509c6 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 @@ -1,6 +1,6 @@ --- title: Restringindo o acesso aos tipos de máquina -shortTitle: Restrict machine types +shortTitle: Restringir tipos de máquinas intro: Você pode definir restrições sobre os tipos de máquinas que os usuários podem escolher ao criarem os codespaces na sua organização. product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage access to machine types for the repositories in an organization, you must be an owner of the organization.' @@ -57,11 +57,11 @@ Se você adicionar uma política para toda a organização, você deverá config ![Editar a restrição de tipo de máquina](/assets/images/help/codespaces/edit-machine-constraint.png) {% data reusables.codespaces.codespaces-policy-targets %} -1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." -1. After you have finished adding constraints to your policy, click **Save**. +1. Se você quiser adicionar outra restrição à política, clique em **Adicionar restrição** e escolha outra restrição. Para informações sobre outras restrições, consulte "[Restringindo a visibilidade das portas encaminhadas](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" e "[Restringindo o período de tempo ocioso](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period). " +1. Após terminar de adicionar restrições à sua política, clique em **Salvar**. ## Editando uma política -You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. +Você pode editar uma política existente. Por exemplo, você deve adicionar ou remover restrições de uma política. 1. Exibir a página "Políticas de codespaces". Para obter mais informações, consulte "[Adicionar uma política para limitar os tipos de máquina disponíveis](#adding-a-policy-to-limit-the-available-machine-types)". 1. Clique no nome da política que você deseja editar. diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md index 15a27bbf8e..773e0bba5f 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md @@ -1,7 +1,7 @@ --- -title: Restricting the idle timeout period -shortTitle: Restrict timeout periods -intro: You can set a maximum timeout period for any codespaces owned by your organization. +title: Restringindo o período de tempo limite ocioso +shortTitle: Restringir períodos de tempo limite +intro: Você pode definir um período máximo de tempo limite para quaisquer codespaces pertencentes à sua organização. product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage timeout constraints for an organization''s codespaces, you must be an owner of the organization.' versions: @@ -14,66 +14,66 @@ topics: ## Visão Geral -By default, codespaces time out after 30 minutes of inactivity. When a codespace times out it is stopped and will no longer incur charges for compute usage. +Por padrão, os códigos vencem após 30 minutos de inatividade. Quando um tempo de um codespace se esgota, ele é interrompido e deixa de se cobrar pelo uso de computação. -The personal settings of a {% data variables.product.prodname_dotcom %} user allow them to define their own timeout period for codespaces they create. This may be longer than the default 30-minute period. For more information, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)." +As configurações pessoais de um usuário {% data variables.product.prodname_dotcom %} permitem que ele defina seu próprio período de tempo limite para os codespaces que cria. Este período pode ser maior do que o período padrão de 30 minutos. Para obter mais informações, consulte "[Definindo seu período de tempo limite para os codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)". -As an organization owner, you may want to configure constraints on the maximum idle timeout period for codespaces owned by your organization. This can help you limit costs associated with codespaces that are left to timeout after long periods of inactivity. You can set a maximum timeout for all codespaces owned by your organization, or for the codespaces of specific repositories. +Como proprietário da organização, você deve configurar restrições sobre o período máximo de tempo ocioso para codespaces pertencentes à sua organização. Isso pode ajudar você a limitar os custos associados aos codespaces que ficam em tempo limite após longos períodos de inatividade. É possível definir o tempo limite máximo para todos os codespaces pertencentes à sua organização ou para os codespaces de repositórios específicos. {% note %} -**Note**: Maximum idle timeout constraints only apply to codespaces that are owned by your organization. +**Observação**: Máximo de restrições de tempo limite só se aplica a codespaces que pertencem à sua organização. {% endnote %} -For more information about pricing for {% data variables.product.prodname_codespaces %} compute usage, see "[About billing for Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)." +Para obter mais informações sobre os preços para uso de computação de {% data variables.product.prodname_codespaces %}, consulte "[Sobre cobrança para os codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)". -### Behavior when you set a maximum idle timeout constraint +### Comportamento ao definir uma restrição de tempo limite máximo -If someone sets the default idle timeout to 90 minutes in their personal settings and they then start a codespace for a repository with a maximum idle timeout constraint of 60 minutes, the codespace will time out after 60 minutes of inactivity. When codespace creation completes, a message explaining this will be displayed: +Se alguém definir o tempo ocioso padrão como 90 minutos nas suas configurações pessoais e iniciar um codespace para um repositório com uma restrição de tempo limite máximo de 60 minutos o tempo do codespace irá esgotar-se após 60 minutos de inatividade. Após a conclusão da criação do codespace, será exibida uma mensagem com a seguinte explicação: -> Idle timeout for this codespace is set to 60 minutes in compliance with your organization’s policy. +> O tempo limite de espera para este codespace é definido como 60 minutos, de acordo com a política da sua organização. ### Definindo políticas específicas da organização e do repositório -When you create a policy, you choose whether it applies to all repositories in your organization, or only to specified repositories. If you create an organization-wide policy with a timeout constraint, then the timeout constraints in any policies that are targeted at specific repositories must fall within the restriction configured for the entire organization. The shortest timeout period - in an organization-wide policy, a policy targeted at specified repositories, or in someone's personal settings - is applied. +Ao criar uma política, você define se ela se aplica a todos os repositórios da organização ou apenas a repositórios específicos. Se você criar uma política para toda a organização com restrição de tempo limite, as restrições de tempo limite em todas as políticas direcionadas a repositórios específicos devem estar dentro da restrição configurada para toda a organização. Aplica-se o período de tempo limite mais curto, em uma política para toda a organização, uma política orientada a determinados repositórios ou em configurações pessoais de alguém. -If you add an organization-wide policy with a timeout constraint, you should set the timeout to the longest acceptable period. You can then add separate policies that set the maximum timeout to a shorter period for specific repositories in your organization. +Se você adicionar uma política para toda a organização com uma restrição de tempo limite, você deverá definir o tempo limite como o período de tempo mais longo. Em seguida, é possível adicionar políticas separadas que definam o tempo limite máximo para um período mais curto para repositórios específicos na sua organização. -## Adding a policy to set a maximum idle timeout period +## Adicionando uma política para definir um período máximo de tempo ocioso {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.codespaces.codespaces-org-policies %} -1. Click **Add constraint** and choose **Maximum idle timeout**. +1. Clique **Adicionar restrição** e escolha **Tempo máximo de espera**. - ![Add a constraint for idle timeout](/assets/images/help/codespaces/add-constraint-dropdown-timeout.png) + ![Adicionar restrição ao tempo ocioso](/assets/images/help/codespaces/add-constraint-dropdown-timeout.png) 1. Clique {% octicon "pencil" aria-label="The edit icon" %} para editar a restrição. - ![Edit the timeout constraint](/assets/images/help/codespaces/edit-timeout-constraint.png) + ![Editar a restrição de tempo limite](/assets/images/help/codespaces/edit-timeout-constraint.png) -1. Enter the maximum number of minutes codespaces can remain inactive before they time out, then click **Save**. +1. Insira o número máximo de minutos que os codespaces podem permanecer inativos antes do tempo limite e, em seguida, clique em **Salvar**. ![Escolha as opções de visibilidade da porta](/assets/images/help/codespaces/maximum-minutes-timeout.png) {% data reusables.codespaces.codespaces-policy-targets %} -1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)." -1. After you have finished adding constraints to your policy, click **Save**. +1. Se você quiser adicionar outra restrição à política, clique em **Adicionar restrição** e escolha outra restrição. Para informações sobre outras restrições, consulte "[Restringindo o acesso aos tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" e "[Restringindo a visibilidade das portas encaminhadas](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)". +1. Após terminar de adicionar restrições à sua política, clique em **Salvar**. -The policy will be applied to all new codespaces that are created, and to existing codespaces the next time they are started. +A política será aplicada a todos os novos codespaces que forem criados e a codespaces existentes na próxima vez que forem iniciados. ## Editando uma política -You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. +Você pode editar uma política existente. Por exemplo, você deve adicionar ou remover restrições de uma política. -1. Exibir a página "Políticas de codespaces". For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)." +1. Exibir a página "Políticas de codespaces". Para obter mais informações, consulte "[Adicionando uma política para definir um período máximo de tempo limite ocioso](#adding-a-policy-to-set-a-maximum-idle-timeout-period)." 1. Clique no nome da política que você deseja editar. 1. Faça as alterações necessárias e, em seguida, clique em **Salvar**. ## Excluindo uma política -1. Exibir a página "Políticas de codespaces". For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)." +1. Exibir a página "Políticas de codespaces". Para obter mais informações, consulte "[Adicionando uma política para definir um período máximo de tempo limite ocioso](#adding-a-policy-to-set-a-maximum-idle-timeout-period)." 1. Clique no botão excluir à direita da política que você deseja excluir. ![O botão de excluir uma política](/assets/images/help/codespaces/policy-delete.png) diff --git a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md index 692f0f4887..93ad86453d 100644 --- a/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md +++ b/translations/pt-BR/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md @@ -1,6 +1,6 @@ --- title: Restringindo a visibilidade das portas encaminhadas -shortTitle: Restrict port visibility +shortTitle: Restringir visibilidade da porta intro: Você pode definir as restrições das opções de visibilidade que os usuários podem escolher quando encaminham portas em codespaces na sua organização. product: '{% data reusables.gated-features.codespaces %}' permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an owner of the organization.' @@ -54,11 +54,11 @@ Se você adicionar uma política para toda a organização, você deverá defini ![Escolha as opções de visibilidade da porta](/assets/images/help/codespaces/choose-port-visibility-options.png) {% data reusables.codespaces.codespaces-policy-targets %} -1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)." -1. After you have finished adding constraints to your policy, click **Save**. +1. Se você quiser adicionar outra restrição à política, clique em **Adicionar restrição** e escolha outra restrição. Para obter informações sobre outras restrições, consulte "[Restringindo o acesso aos tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" e "[Restringindo o período de tempo limite ocioso](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period). " +1. Após terminar de adicionar restrições à sua política, clique em **Salvar**. ## Editando uma política -You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy. +Você pode editar uma política existente. Por exemplo, você deve adicionar ou remover restrições de uma política. 1. Exibir a página "Políticas de codespaces". Para obter mais informações, consulte "[Adicionando uma política para limitar as opções de visibilidade da porta](#adding-a-policy-to-limit-the-port-visibility-options)". 1. Clique no nome da política que você deseja editar. diff --git a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md index d2e7d697af..ecdbcbd3fa 100644 --- a/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md +++ b/translations/pt-BR/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md @@ -25,7 +25,7 @@ Quando as permissões são listadas no arquivo `devcontainer.json`, será solici Para criar codespaces com permissões personalizadas definidas, você deve usar um dos seguintes: * A interface de usuário web do {% data variables.product.prodname_dotcom %} * [CLI de {% data variables.product.prodname_dotcom %}](https://github.com/cli/cli/releases/latest) 2.5.2 ou posterior -* [Extensão do Visual Studio Code de{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 ou superior +* [{% data variables.product.prodname_github_codespaces %} {% data variables.product.prodname_vscode %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 or later ## Configurando permissões adicionais do repositório @@ -87,7 +87,7 @@ Para criar codespaces com permissões personalizadas definidas, você deve usar } ``` - To set all permissions for a given repository, use `"permissions": "read-all"` or `"permissions": "write-all"` in the repository object. + Para definir todas as permissões para um determinado repositório, use `"permissions": "read-all"` ou `"permissions": "write-all"` no objeto repositório. ```json { diff --git a/translations/pt-BR/content/codespaces/overview.md b/translations/pt-BR/content/codespaces/overview.md index 1e6ce1566d..6866957425 100644 --- a/translations/pt-BR/content/codespaces/overview.md +++ b/translations/pt-BR/content/codespaces/overview.md @@ -34,7 +34,7 @@ Para personalizar os tempos de execução e ferramentas no seu codespace, é pos Se você não adicionar uma configuração de contêiner de desenvolvimento, o {% data variables.product.prodname_codespaces %} clonará seu repositório em um ambiente com a imagem de código padrão que inclui muitas ferramentas, linguagens e ambientes de tempo de execução. Para obter mais informações, consulte "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". -Você também pode personalizar aspectos do ambiente do seu codespace usando um repositório público do [dotfiles](https://dotfiles.github.io/tutorials/) e [Sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync). A personalização pode incluir preferências de shell, ferramentas adicionais, configurações de editor e extensões de código VS. Para obter mais informações, consulte[Personalizando seu codespace](/codespaces/customizing-your-codespace)". +Você também pode personalizar aspectos do ambiente do seu codespace usando um repositório público do [dotfiles](https://dotfiles.github.io/tutorials/) e [Sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and {% data variables.product.prodname_vscode_shortname %} extensions. Para obter mais informações, consulte[Personalizando seu codespace](/codespaces/customizing-your-codespace)". ## Sobre a cobrança do {% data variables.product.prodname_codespaces %} diff --git a/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md index b0b5f32897..1aaa699884 100644 --- a/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md +++ b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md @@ -94,7 +94,7 @@ Os segredos de {% data variables.product.prodname_codespaces %} que você criar ## Configurando tarefas demoradas a serem incluídas na pré-compilação -Você pode usar os comandos `onCreateCommand` e `updateContentCommand` no seu `devcontainer.json` paraa incluir processos demorados como parte da criação de template de pré-compilação. Para obter mais informações, consulte a documentação do Visual Studio "[referência do devcontainer.json](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)". +Você pode usar os comandos `onCreateCommand` e `updateContentCommand` no seu `devcontainer.json` paraa incluir processos demorados como parte da criação de template de pré-compilação. For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)." `onCreateCommand` é executado apenas uma vez, quando o modelo de pré-compilação é criado, enquanto `updateContentCommand` é executado na criação do modelos e em subsequentes atualizações dos modelos. As compilações incrementais devem ser incluídas em `updateContentCommand` uma vez que representam a fonte do seu projeto e devem ser incluídas para cada atualização de um modelo de pré-compilação. diff --git a/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md index 5a2261f8df..3689bf9671 100644 --- a/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md +++ b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md @@ -58,20 +58,20 @@ Exibe o histórico de execução de fluxo de trabalho para pré-compilações pa 1. Faça as alterações necessárias na configuração de pré-compilação e, em seguida, clique em **Atualizar**. -### Disabling a prebuild configuration +### Desabilitando configuração de pré-compilação -To pause the update of prebuild templates for a configuration, you can disable workflow runs for the configuration. Disabling the workflow runs for a prebuild configuration does not delete any previously created prebuild templates for that configuration and, as a result, codespaces will continue to be generated from an existing prebuild template. +Para pausar a atualização dos modelos de pré-compilação para uma configuração, você pode desabilitar as execuções de fluxo de trabalho para a configuração. Desabilitar as execuções de fluxo de trabalho para uma configuração de pré-compilação não exclui nenhum modelo de pré-compilação previamente criado para essa configuração e, como resultado, os codespaces continuarão sendo gerados a partir de um modelo de pré-compilação existente. -Disabling the workflow runs for a prebuild configuration is useful if you need to investigate template creation failures. +Desabilitar as execuções de fluxo de trabalho para uma configuração de pré-compilação é útil se você precisar investigar as falhas de criação de modelo. -1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to disable. -1. In the dropdown menu, click **Disable runs**. +1. Na página de {% data variables.product.prodname_codespaces %} das configurações do repositório, clique nas reticências à direita da configuração de pré-compilação que você deseja desabilitar. +1. No menu suspenso, clique em **Desabilitar execuções**. - ![The 'Disable runs' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-disable.png) + ![A opção "Desabilitar execuções" no menu suspenso](/assets/images/help/codespaces/prebuilds-disable.png) -1. To confirm that you want to disable this configuration, click **OK**. +1. Para confirmar que você deseja desabilitar esta configuração, clique em **OK**. -### Deleting a prebuild configuration +### Excluindo a configuração de uma pré-compilação A exclusão de uma configuração de pré-compilação também exclui todos os modelos de pré-compilação criados anteriormente para essa configuração. Como resultado, logo após você excluir uma configuração, as pré-compilações geradas por essa configuração não estarão disponíveis ao criar um novo codespace. diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md index 95de7f8801..ce3629c19d 100644 --- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md +++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md @@ -53,7 +53,7 @@ Para obter informações sobre como escolher sua configuração preferida de con It's useful to think of the `devcontainer.json` file as providing "customization" rather than "personalization." Você só deve incluir coisas que todos que trabalham em sua base de código precisam como elementos padrão do ambiente de desenvolvimento, não coisas que são preferências pessoais. Coisas como os linters estão corretas para padronizar e exigir que todos realizaram a instalação. Portanto, são boas para incluir no seu arquivo `devcontainer.json`. Coisas como decoradores ou temas de interface de usuário são escolhas pessoais que não devem ser colocadas no arquivo `devcontainer.json`. -You can personalize your codespaces by using dotfiles and Settings Sync. Para obter mais informações, consulte "[Personalizando os codespaces para a sua conta](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account). " +Você pode personalizar seus codespaces usando dotfiles e Settings Sync. Para obter mais informações, consulte "[Personalizando os codespaces para a sua conta](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account). " ### arquivo Docker @@ -110,19 +110,19 @@ Para usar um arquivo Dockerfile como parte de uma configuração de contêiner d } ``` -Para obter mais informações sobre como usar um arquivo Docker em uma configuração de contêiner de desenvolvimento, consulte a documentação de {% data variables.product.prodname_vscode %} "[Criar um contêiner de desenvolvimento](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile). " +For more information about using a Dockerfile in a dev container configuration, see the {% data variables.product.prodname_vscode_shortname %} documentation "[Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)." ## Usando a configuração padrão do contêiner de desenvolvimento -Se você não definir uma configuração no repositório, o {% data variables.product.prodname_dotcom %} criará um codespace que usa uma imagem padrão do Linux. This Linux image includes a number of runtime versions for popular languages like Python, Node, PHP, Java, Go, C++, Ruby, and .NET Core/C#. The latest or LTS releases of these languages are used. There are also tools to support data science and machine learning, such as JupyterLab and Conda. The image also includes other developer tools and utilities like Git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the URL that the command outputs. +Se você não definir uma configuração no repositório, o {% data variables.product.prodname_dotcom %} criará um codespace que usa uma imagem padrão do Linux. Esta imagem do Linux inclui um número de versões de tempo de execução para linguagens populares como Python, Node, PHP, Java, Go, C++, Ruby e .NET Core/C#. São utilizadas as versões mais recentes ou LTS dessas linguagens. Além disso, há ferramentas para apoiar a ciência de dados e a aprendizagem de máquinas, como JupyterLab e Conda. A imagem também inclui outras ferramentas e utilitários para desenvolvedores como Git, CLI do GitHub, yarn, openssh e vim. Para ver todas as linguagens, tempos de execução e as ferramentas que são incluídas, use o comando `devcontainer-info content-url` dentro do seu terminal de código e siga o URL que o comando emite. -Alternatively, for more information about everything that's included in the default Linux image, see the latest file in the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) repository. +Como alternativa, para obter mais informações sobre tudo o que está incluído na imagem padrão do Linux, consulte o arquivo mais recente no repositório [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux). -The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_github_codespaces %} provides. +A configuração padrão é uma boa opção se você estiver trabalhando em um pequeno projeto que usa as linguagens e ferramentas que {% data variables.product.prodname_github_codespaces %} fornece. -## Using a predefined dev container configuration +## Usando uma configuração de contêiner predefinida -É possível escolher uma lista de configurações predefinidas para criar uma configuração de contêiner de desenvolvimento para o seu repositório. Essas configurações fornecem configurações comuns para determinados tipos de projeto e podem ajudar você rapidamente a começar com uma configuração que já tem as opções de contêiner apropriadas, configurações do {% data variables.product.prodname_vscode %} e extensões do {% data variables.product.prodname_vscode %} que devem ser instaladas. +É possível escolher uma lista de configurações predefinidas para criar uma configuração de contêiner de desenvolvimento para o seu repositório. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode_shortname %} settings, and {% data variables.product.prodname_vscode_shortname %} extensions that should be installed. Usar uma configuração predefinida é uma ótima ideia se você precisa de uma extensão adicional. Você também pode começar com uma configuração predefinida e alterá-la conforme necessário para o seu projeto. @@ -138,7 +138,7 @@ Usar uma configuração predefinida é uma ótima ideia se você precisa de uma ![Botão OK](/assets/images/help/codespaces/prebuilt-container-ok-button.png) -1. Se você estiver trabalhando em um codespace, aplique suas alterações clicando em **Reconstruir agora** na mensagem na parte inferior direita da janela. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-configuration-changes-to-a-codespace)." +1. Se você estiver trabalhando em um codespace, aplique suas alterações clicando em **Reconstruir agora** na mensagem na parte inferior direita da janela. Para obter mais informações sobre a reconstrução do seu contêiner, consulte "[Aplicar alterações na sua configuração](#applying-configuration-changes-to-a-codespace)". !["Códigos: Recriar contêiner" em {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/rebuild-prompt.png) @@ -163,7 +163,7 @@ Você pode adicionar algumas das características mais comuns selecionando-as na ![O menu de seleção de funcionalidades adicionais durante a configuração do contêiner](/assets/images/help/codespaces/select-additional-features.png) -1. Para aplicar as alterações, no canto inferior direito da tela, clique em **Reconstruir agora**. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-configuration-changes-to-a-codespace)." +1. Para aplicar as alterações, no canto inferior direito da tela, clique em **Reconstruir agora**. Para obter mais informações sobre a reconstrução do seu contêiner, consulte "[Aplicar alterações na sua configuração](#applying-configuration-changes-to-a-codespace)". !["Codespaces: Reconstruir contêiner" na paleta de comandos](/assets/images/help/codespaces/rebuild-prompt.png) @@ -171,7 +171,7 @@ Você pode adicionar algumas das características mais comuns selecionando-as na Se nenhuma das configurações predefinidas atender às suas necessidades, você poderá criar uma configuração personalizada escrevendo seu próprio arquivo `devcontainer.json`. -* If you're adding a single `devcontainer.json` file that will be used by everyone who creates a codespace from your repository, create the file within a `.devcontainer` directory at the root of the repository. +* Se você estiver adicionando um único arquivo `devcontainer.json` que será usado por todos que criarem um código a partir do seu repositório, crie o arquivo dentro de um diretório `.devcontainer` na raiz do repositório. * If you want to offer users a choice of configuration, you can create multiple custom `devcontainer.json` files, each located within a separate subdirectory of the `.devcontainer` directory. {% note %} @@ -192,9 +192,9 @@ If `.devcontainer/devcontainer.json` or `.devcontainer.json` exists, it will be ### Editando o arquivo devcontainer.json -Você pode adicionar e editar as chaves de configuração compatíveis no arquivo `devcontainer.json` para especificar aspectos do ambiente do codespace como, por exemplo, quais extensões de {% data variables.product.prodname_vscode %} serão instaladas. {% data reusables.codespaces.more-info-devcontainer %} +You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode_shortname %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %} -The `devcontainer.json` file is written using the JSONC format. Isso permite que você inclua comentários no arquivo de configuração. For more information, see "[Editing JSON with Visual Studio Code](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode %} documentation. +The `devcontainer.json` file is written using the JSONC format. Isso permite que você inclua comentários no arquivo de configuração. For more information, see "[Editing JSON with {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% note %} @@ -202,11 +202,11 @@ The `devcontainer.json` file is written using the JSONC format. Isso permite que {% endnote %} -### Editor settings for Visual Studio Code +### Editor settings for {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.vscode-settings-order %} -Você pode definir as configurações de editor-padrão para {% data variables.product.prodname_vscode %} em dois lugares. +You can define default editor settings for {% data variables.product.prodname_vscode_shortname %} in two places. * Editor settings defined in the `.vscode/settings.json` file in your repository are applied as _Workspace_-scoped settings in the codespace. * Editor settings defined in the `settings` key in the `devcontainer.json` file are applied as _Remote [Codespaces]_-scoped settings in the codespace. diff --git a/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md b/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md index bd04f82b77..8cc2dad801 100644 --- a/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md +++ b/translations/pt-BR/content/codespaces/the-githubdev-web-based-editor.md @@ -27,7 +27,7 @@ O {% data variables.product.prodname_serverless %} introduz uma experiência lev O {% data variables.product.prodname_serverless %} está disponível para todos gratuitamente em {% data variables.product.prodname_dotcom_the_website %}. -O {% data variables.product.prodname_serverless %} fornece muitos dos benefícios de {% data variables.product.prodname_vscode %}, como pesquisa, destaque de sintaxe e uma visão de controle de origem. Você também pode usar a sincronização de configuração para compartilhar suas próprias configurações {% data variables.product.prodname_vscode %} com o editor. Para obter mais informações, consulte "[Sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync)" na documentação de {% data variables.product.prodname_vscode %}. +O {% data variables.product.prodname_serverless %} fornece muitos dos benefícios de {% data variables.product.prodname_vscode %}, como pesquisa, destaque de sintaxe e uma visão de controle de origem. Você também pode usar a sincronização de configuração para compartilhar suas próprias configurações {% data variables.product.prodname_vscode_shortname %} com o editor. Para obter mais informações, consulte "[Sincronização de configurações](https://code.visualstudio.com/docs/editor/settings-sync)" na documentação de {% data variables.product.prodname_vscode_shortname %}. O {% data variables.product.prodname_serverless %} é executado inteiramente no sandbox do seu navegador. O editor não clona o repositório, mas usa a [Extensão de repositórios do GitHub](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) para realizar a maior parte das funcionalidades que você usará. Seu trabalho é salvo no armazenamento local do navegador até que você faça commit dele. Você deve fazer commit das alterações regularmente para garantir que estejam sempre acessíveis. @@ -49,7 +49,7 @@ Tanto o {% data variables.product.prodname_serverless %} quanto o {% data variab | **Inicialização** | O {% data variables.product.prodname_serverless %} abre instantaneamente com um toque de tecla e você pode começar a usá-lo imediatamente, sem ter que esperar por uma configuração ou instalação adicional. | Ao criar ou retomar um codespace, o código é atribuído a uma VM e o contêiner é configurado com base no conteúdo de um arquivo `devcontainer.json`. Essa configuração pode levar alguns minutos para criar o ambiente. Para obter mais informações, consulte "[Criando um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". | | **Calcular** | Não há nenhum computador associado. Portanto você não conseguirá criar e executar o seu código ou usar o terminal integrado. | Com {% data variables.product.prodname_codespaces %}, você obtém o poder da VM dedicada na qual você pode executar e depurar seu aplicativo. | | **Acesso ao terminal** | Nenhum. | {% data variables.product.prodname_codespaces %} fornece um conjunto comum de ferramentas por padrão, o que significa que você pode usar o Terminal exatamente como você faria no seu ambiente local. | -| **Extensões** | Apenas um subconjunto de extensões que podem ser executadas na web aparecerão na visualização de extensões e podem ser instaladas. Para obter mais informações, consulte "[Usando as extensões](#using-extensions)." | Com codespaces, você pode utilizar a maioria das extensões do Marketplace do Visual Studio Code. | +| **Extensões** | Apenas um subconjunto de extensões que podem ser executadas na web aparecerão na visualização de extensões e podem ser instaladas. Para obter mais informações, consulte "[Usando as extensões](#using-extensions)." | With Codespaces, you can use most extensions from the {% data variables.product.prodname_vscode_marketplace %}. | ### Continue trabalhando em {% data variables.product.prodname_codespaces %} @@ -61,9 +61,9 @@ Para continuar seu trabalho em um codespace, clique em **Continuar trabalho em ## Usando controle de origem -Ao usar o {% data variables.product.prodname_serverless %}, todas as ações são gerenciadas por meio da Visualização de Controle de Origem, localizado na Barra de Atividades do lado esquerdo. Para obter mais informações sobre a Visualização de Controle de Origem, consulte "[Controle de Versão](https://code.visualstudio.com/docs/editor/versioncontrol)" na documentação de {% data variables.product.prodname_vscode %}. +Ao usar o {% data variables.product.prodname_serverless %}, todas as ações são gerenciadas por meio da Visualização de Controle de Origem, localizado na Barra de Atividades do lado esquerdo. Para obter mais informações sobre a Visualização de Controle de Origem, consulte "[Controle de Versão](https://code.visualstudio.com/docs/editor/versioncontrol)" na documentação de {% data variables.product.prodname_vscode_shortname %}. -Como o editor da web usa a extensão dos repositórios do GitHub para melhorar suas funcionalidades, você pode alternar entre branches sem precisar ocultar alterações. Para obter mais informações, consulte "[Repositórios no GitHub](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" na documentação do {% data variables.product.prodname_vscode %}. +Como o editor da web usa a extensão dos repositórios do GitHub para melhorar suas funcionalidades, você pode alternar entre branches sem precisar ocultar alterações. Para obter mais informações, consulte "[Repositórios no GitHub](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" na documentação do {% data variables.product.prodname_vscode_shortname %}. ### Criar um branch @@ -88,9 +88,9 @@ Você pode usar o {% data variables.product.prodname_serverless %} para trabalha ## Usando extensões -O {% data variables.product.prodname_serverless %} é compatível com extensões de {% data variables.product.prodname_vscode %} que foram especificamente criadas ou atualizadas para serem executadas na web. Essas extensões são conhecidas como "extensões da web". Para saber como criar uma extensão da web ou atualizar sua extensão existente para funcionar na web, consulte "[Extensões da web](https://code.visualstudio.com/api/extension-guides/web-extensions)" na documentação de {% data variables.product.prodname_vscode %}. +O {% data variables.product.prodname_serverless %} é compatível com extensões de {% data variables.product.prodname_vscode_shortname %} que foram especificamente criadas ou atualizadas para serem executadas na web. Essas extensões são conhecidas como "extensões da web". Para saber como criar uma extensão da web ou atualizar sua extensão existente para funcionar na web, consulte "[Extensões da web](https://code.visualstudio.com/api/extension-guides/web-extensions)" na documentação de {% data variables.product.prodname_vscode_shortname %}. -As extensões que podem ser executadas no {% data variables.product.prodname_serverless %} aparecerão na vista de Extensões e poderão ser instaladas. Se você usar a Sincronização de Configurações, todas as extensões compatíveis também são instaladas automaticamente. Para obter informações, consulte "[Sincronização de Configurações](https://code.visualstudio.com/docs/editor/settings-sync)" na documentação de {% data variables.product.prodname_vscode %}. +As extensões que podem ser executadas no {% data variables.product.prodname_serverless %} aparecerão na vista de Extensões e poderão ser instaladas. Se você usar a Sincronização de Configurações, todas as extensões compatíveis também são instaladas automaticamente. Para obter informações, consulte "[Sincronização de Configurações](https://code.visualstudio.com/docs/editor/settings-sync)" na documentação de {% data variables.product.prodname_vscode_shortname %}. ## Solução de Problemas @@ -104,5 +104,5 @@ Se você tiver problemas ao abrir {% data variables.product.prodname_serverless ### Limitações conhecidas - O {% data variables.product.prodname_serverless %} atualmente é compatível com o Chrome (e vários outros navegadores baseados no Chromium), Edge, Firefox e Safari. Recomendamos que você use as versões mais recentes desses navegadores. -- Algumas teclas de atalho podem não funcionar, dependendo do navegador que você estiver usando. Essas limitações de atalhos de tecla estão documentadas na seção "[Limitações e adaptações conhecidas](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" da documentação de {% data variables.product.prodname_vscode %}. +- Algumas teclas de atalho podem não funcionar, dependendo do navegador que você estiver usando. Essas limitações de atalhos de tecla estão documentadas na seção "[Limitações e adaptações conhecidas](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" da documentação de {% data variables.product.prodname_vscode_shortname %}. - `.` pode não funcionar para abrir o {% data variables.product.prodname_serverless %} de acordo com o layout local do teclado. Nesse caso, você pode abrir qualquer repositório {% data variables.product.prodname_dotcom %} em {% data variables.product.prodname_serverless %} alterando o URL de `github.com` para `github.dev`. diff --git a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md index e48bc35b96..7034e18b8e 100644 --- a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md +++ b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -22,11 +22,11 @@ Ao criar um codespace, você pode escolher o tipo de máquina virtual que deseja ![Uma lista dos tipos de máquina disponíveis](/assets/images/help/codespaces/choose-custom-machine-type.png) -Se você tiver sua preferência de editor de {% data variables.product.prodname_codespaces %} definida como "Visual Studio Code para Web", a página "Configurando seu codespace" mostrará a mensagem "Prebuilt codespace found" se uma pré-compilação estiver sendo utilizada. +If you have your {% data variables.product.prodname_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used. ![A mensagem "codespaces da pre-criação encontrados"](/assets/images/help/codespaces/prebuilt-codespace-found.png) -Da mesma forma, se sua preferência de editor for "Visual Studio Code", o terminal integrado conterá a mensagem "Você está em um codespace pré-compilado efinido pela configuração de pré-compilação do seu repositório" ao criar um novo codespace. Para obter mais informações, consulte "[Definindo seu editor padrão para codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)". +Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. Para obter mais informações, consulte "[Definindo seu editor padrão para codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)". Depois de criar um codespace, você pode verificar se ele foi criado a partir de uma pré-compilação executando o seguinte comando {% data variables.product.prodname_cli %} no terminal: diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md index 156eb247b3..d8e5bfa621 100644 --- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md +++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md @@ -44,7 +44,7 @@ Os wikis fazem parte dos repositórios Git, de modo que é possível fazer alter ### Clonar wikis para seu computador -Cada wiki fornece uma maneira fácil de clonar o respectivo conteúdo para seu computador. Once you've created an initial page on {% data variables.product.product_name %}, you can clone the repository to your computer with the provided URL: +Cada wiki fornece uma maneira fácil de clonar o respectivo conteúdo para seu computador. Depois de criar uma página inicial em {% data variables.product.product_name %}, você pode clonar o repositório para o seu computador com o URL fornecido: ```shell $ git clone https://github.com/YOUR_USERNAME/YOUR_REPOSITORY.wiki.git diff --git a/translations/pt-BR/content/communities/moderating-comments-and-conversations/index.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/index.md index 0cacf37e75..c27079b79b 100644 --- a/translations/pt-BR/content/communities/moderating-comments-and-conversations/index.md +++ b/translations/pt-BR/content/communities/moderating-comments-and-conversations/index.md @@ -16,7 +16,7 @@ children: - /managing-disruptive-comments - /locking-conversations - /limiting-interactions-in-your-repository - - /limiting-interactions-for-your-user-account + - /limiting-interactions-for-your-personal-account - /limiting-interactions-in-your-organization - /tracking-changes-in-a-comment - /managing-how-contributors-report-abuse-in-your-organizations-repository diff --git a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md similarity index 93% rename from translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md rename to translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md index 2fc6593414..ca7211b63c 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-personal-account.md @@ -1,5 +1,5 @@ --- -title: Limitar interações para sua conta de usuário +title: Limitando interações para a sua conta pessoal intro: Você pode aplicar temporariamente um período de atividade limitada para certos usuários em todos os repositórios públicos pertencentes à sua conta pessoal. versions: fpt: '*' @@ -7,6 +7,7 @@ versions: permissions: Anyone can limit interactions for their own personal account. redirect_from: - /github/building-a-strong-community/limiting-interactions-for-your-user-account + - /communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account topics: - Community shortTitle: Limitar interações na conta 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 58aceccc82..918ecc7690 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 @@ -22,7 +22,7 @@ shortTitle: Limitar interações no repositório {% data reusables.community.types-of-interaction-limits %} -Você também pode habilitar limitações de atividade em todos os repositórios pertencentes à sua conta pessoal ou a uma organização. Se o limite de um usuário ou organização estiver habilitado, não será possível limitar a atividade para repositórios individuais pertencentes à conta. Para obter mais informações, consulte "[Limitar interações para a sua conta pessoal](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account)" e "[Limitar interações na sua organização](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)". +Você também pode habilitar limitações de atividade em todos os repositórios pertencentes à sua conta pessoal ou a uma organização. Se o limite de um usuário ou organização estiver habilitado, não será possível limitar a atividade para repositórios individuais pertencentes à conta. Para obter mais informações, consulte "[Limitar interações para a sua conta pessoal](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account)" e "[Limitar interações na sua organização](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)". ## Restringir interações no repositório diff --git a/translations/pt-BR/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md index 24f381969d..cb3d4ac7a8 100644 --- a/translations/pt-BR/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md +++ b/translations/pt-BR/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md @@ -47,13 +47,13 @@ Qualquer pessoa com acesso de gravação em um repositório pode editar comentá Considera-se apropriado editar um comentário e remover o conteúdo que não contribui para a conversa e viole o código de conduta da sua comunidade{% ifversion fpt or ghec %} ou as diretrizes [da Comunidade do GitHub](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}. -Sometimes it may make sense to clearly indicate edits and their justification. +Por vezes, pode fazer sentido indicar claramente as edições e a sua justificativa. -That said, anyone with read access to a repository can view a comment's edit history. O menu suspenso **edited** (editado) na parte superior do comentário tem um histório de edições mostrando o usuário e o horário de cada edição. +Dito isso, qualquer pessoa com acesso de leitura a um repositório pode ver o histórico de edição de um comentário. O menu suspenso **edited** (editado) na parte superior do comentário tem um histório de edições mostrando o usuário e o horário de cada edição. ![Comentário com observação adicional que o conteúdo foi redacted (suprimido)](/assets/images/help/repository/content-redacted-comment.png) -## Redacting sensitive information +## Redação de informações confidenciais Autores do comentário e pessoas com acesso de gravação a um repositório podem excluir informações confidenciais do histórico de edição de um comentário. Para obter mais informações, consulte "[Controlar as alterações em um comentário](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)". @@ -81,7 +81,7 @@ Excluir um comentário cria um evento na linha do tempo visível a qualquer um c {% endnote %} -### Steps to delete a comment +### Etapas para excluir um comentário 1. Navegue até o comentário que deseja excluir. 2. No canto superior direito do comentário, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e em **Delete** (Excluir). ![Ícone horizontal kebab e menu comment moderation (moderação de comentários) mostrando as opções edit, hide, delete e report (editar, ocultar, excluir e denunciar)](/assets/images/help/repository/comment-menu.png) diff --git a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md index 5c7c244aaa..da20ca5fe9 100644 --- a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md +++ b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md @@ -36,9 +36,7 @@ Usando o construtor de modelo, você pode especificar um titulo e a descrição Com formulários de problemas, você pode criar modelos que têm campos de formulário web usando o esquema de formulário de {% data variables.product.prodname_dotcom %}. Quando um contribuidor abre um problema usando um formulário de problema, as entradas de formulário são convertidas em um comentário de markdown padrão. É possível especificar diferentes tipos de entrada e definir as entradas necessárias para ajudar os colaboradores a abrir problemas acionáveis no seu repositório. Para obter mais informações, consulte "[Configurar templates de problemas para o seu repositório](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)" e "[Sintaxe para formulários de problemas](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)". {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} {% data reusables.repositories.issue-template-config %} Para obter mais informações, consulte "[Configurando modelos de problemas para seu repositório](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser)." -{% endif %} Os modelos de problema são armazenados no branch padrão do repositório, em um diretório `.github/ISSUE_TEMPLATE` oculto. Se você criar um modelo em outro branch, ele não estará disponível para uso dos colaboradores. Os nomes dos arquivos dos modelos de problema não diferenciam maiúsculas e precisam de uma extensão *.md*.{% ifversion fpt or ghec %} Modelos de problemas criados com formulários precisam de uma extensão *.yml*.{% endif %} {% data reusables.repositories.valid-community-issues %} diff --git a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md index 28ad58a43f..bd87e45a05 100644 --- a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md +++ b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md @@ -21,12 +21,8 @@ shortTitle: Configurar {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} - ## Criando modelos de problemas -{% endif %} - {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 3. Na seção "Features" (Recursos), em "Issues" (Problemas), clique em **Set up templates** (Configurar modelos). ![Botão Start template setup (Iniciar configuração do modelo)](/assets/images/help/repository/set-up-templates.png) @@ -62,7 +58,6 @@ Aqui está a versão renderizada do formulário de problema. ![Um formulário de {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} ## Configurando o seletor de modelos {% data reusables.repositories.issue-template-config %} @@ -99,7 +94,6 @@ Seu arquivo de configuração customizará o seletor de modelos quando o arquivo {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -{% endif %} ## Leia mais diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md index ff6925595a..7da45269bc 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md @@ -124,10 +124,10 @@ Ao concluir as alterações que você decidiu fazer no commit, escreva a mensage ![Aviso de branch protegido](/assets/images/help/desktop/protected-branch-warning.png) {% data reusables.desktop.push-origin %} -6. If you have a pull request based off the branch you are working on, {% data variables.product.prodname_desktop %} will display the status of the checks that have run for the pull request. For more information about checks, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." +6. Se você tiver um pull request baseado no branch no qual você está trabalhando, {% data variables.product.prodname_desktop %} irá exibir o status das verificações que foram executadas para o pull request. Para obter mais informações sobre verificações, consulte "[Visualização e reexecução de verificações no GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)". - ![Checks display next to branch name](/assets/images/help/desktop/checks-dialog.png) + ![Exibição das verificações ao lado do nome do branch](/assets/images/help/desktop/checks-dialog.png) - If a pull request has not been created for the current branch, {% data variables.product.prodname_desktop %} will give you the option to create one. Para obter mais informações, consulte "[Criando um problema ou um pull request](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request)." + Se um pull request não tiver sido criado para o branch atual, {% data variables.product.prodname_desktop %} dará a você a opção de criar um. Para obter mais informações, consulte "[Criando um problema ou um pull request](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request)." ![Criar um pull request](/assets/images/help/desktop/mac-create-pull-request.png) diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md index 1532d735b1..3bd9dc5883 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md @@ -1,63 +1,63 @@ --- -title: Configuring notifications in GitHub Desktop +title: Configurando notificações no GitHub Desktop shortTitle: Configurar notificações -intro: '{% data variables.product.prodname_desktop %} will keep you up-to-date with notifications about events that occur in your pull request branch.' +intro: '{% data variables.product.prodname_desktop %} manterá você atualizado com notificações sobre eventos que ocorram no branch do seu pull request.' versions: fpt: '*' --- -## About notifications in {% data variables.product.prodname_desktop %} +## Sobre notificações em {% data variables.product.prodname_desktop %} -{% data variables.product.prodname_desktop %} will show a system notification for events that occur in the currently selected repository. Notifications will be shown when: +{% data variables.product.prodname_desktop %} mostrará uma notificação de sistema para eventos que ocorrem no repositório selecionado atualmente. As notificações serão exibidas quando: -- Pull request checks have failed. -- A pull request review is left with a comment, approval, or requested changes. +- Ocorreu uma falha nas verificações de pull request. +- Deixou-se um comentário, aprovação ou alterações solicitadas em uma uma revisão do pull request. -Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more detailed information. +Clicar na notificação mudará o foco do aplicativo para {% data variables.product.prodname_desktop %} e fornecerá informações mais detalhadas. -## Notifications about pull request check failures +## Notificações sobre falhas de verificação de pull request -When changes are made to a pull request branch, you will receive a notification if the checks fail. +Quando forem feitas alterações em um branch de pull request, você receberá uma notificação se a verificação falhar. -![pull request checks failed notification](/assets/images/help/desktop/pull-request-checks-failed-notification.png) +![o pull request verifica a notificação falha](/assets/images/help/desktop/pull-request-checks-failed-notification.png) -Clicking the notification will display a dialog with details about the checks. Once you've reviewed why the checks have failed, you can re-run the checks, or quickly switch to the pull request branch to get started on fixing the errors. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." +Clicar na notificação irá exibir uma caixa de diálogo com detalhes sobre as verificações. Depois de analisar por que as verificações falharam, você pode voltar a executar a verificação, ou mudar rapidamente para o branch de pull request para começar a corrigir os erros. Para obter mais informações, consulte "[Visualização e reexecução de verificações no GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)". -![checks failed dialog](/assets/images/help/desktop/checks-failed-dialog.png) -## Notifications for pull request reviews +![diálogo de verificações falhou](/assets/images/help/desktop/checks-failed-dialog.png) +## Notificações para revisões de pull request -{% data variables.product.prodname_desktop %} will surface a system notification when a teammate has approved, commented, or requested changes in your pull request. See "[About pull request reviews](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)" for more information on pull request reviews. +O {% data variables.product.prodname_desktop %} irá mostrar uma notificação do sistema quando um colega de equipe tiver aprovado, comentado ou solicitado alteralçoes no seu pull request. Consulte "[Sobre revisões de pull request](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)" para obter mais informações sobre análises de pull request. -![Pull request review notification](/assets/images/help/desktop/pull-request-review-notification.png) +![Notificação de revisão de pull request](/assets/images/help/desktop/pull-request-review-notification.png) -Clicking the notification will switch application focus to {% data variables.product.prodname_desktop %} and provide more context for the pull request review comment. +Clicar na notificação mudará o foco do aplicativo para {% data variables.product.prodname_desktop %} e fornecerá mais contexto para o comentário de revisão de pull request. -![pull request review dialog](/assets/images/help/desktop/pull-request-review-dialog.png) -## Enabling notifications +![diálogo da revisão de pull request](/assets/images/help/desktop/pull-request-review-dialog.png) +## Habilitando notificações -If system notifications are disabled for {% data variables.product.prodname_desktop %} you can follow the steps below to enable them. +Se as notificações do sistema estiverem desabilitadas para {% data variables.product.prodname_desktop %} você pode seguir as etapas abaixo para habilitá-las. {% mac %} -1. Click the **Apple** menu, then select **System Preferences**. -2. Select **Notifications & Focus**. -3. Select **{% data variables.product.prodname_desktop %}** from the list of applications. -4. Click **Allow Notifications**. +1. Clique no menu de **Apple** e, em seguida, selecione **Sistema de Preferências**. +2. Selecione **Notificações & Foco**. +3. Selecione **{% data variables.product.prodname_desktop %}** na lista de aplicativos. +4. Clique em **permitir notificações**. -![macOS Notifications & Focus](/assets/images/help/desktop/mac-enable-notifications.png) +![Notificações do macOS & Foco](/assets/images/help/desktop/mac-enable-notifications.png) -For more information about macOS system notifications, see "[Use notifications on your Mac](https://support.apple.com/en-us/HT204079)." +Para obter mais informações sobre as notificações do sistema macOS, consulte "[Usar as notificações no seu Mac](https://support.apple.com/en-us/HT204079)". {% endmac %} {% windows %} -1. Open the **Start** menu, then select **Settings**. -2. Select **System**, then click **Notifications**. -3. Find **{% data variables.product.prodname_desktop %}** in the application list and click **On**. +1. Abra o menu **Iniciar** e, em seguida, selecione **Configurações**. +2. Selecione **Sistema** e, em seguida, clique em **Notificações**. +3. Encontre **{% data variables.product.prodname_desktop %}** na lista de aplicativos e clique **On**. -![Enable Windows Notifications](/assets/images/help/desktop/windows-enable-notifications.png) +![Habilitar notificações do Windows](/assets/images/help/desktop/windows-enable-notifications.png) -For more information about Windows system notifications, see "[Change notification settings in Windows](https://support.microsoft.com/en-us/windows/change-notification-settings-in-windows-8942c744-6198-fe56-4639-34320cf9444e)." +Para obter mais informações sobre as notificações do sistema do Windows, consulte "[Alterar configurações de notificação no Windows](https://support.microsoft.com/en-us/windows/change-notification-settings-in-windows-8942c744-6198-fe56-4639-34320cf9444e)". {% endwindows %} diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md index 95c25d770f..7bec853c67 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md @@ -15,7 +15,7 @@ Você pode visualizar os pull requests que você ou seus colaboradores propusera Ao visualizar um pull request no {% data variables.product.prodname_desktop %}, você poderá ver um histórico de commits feitos pelos contribuidores. Você também pode ver quais arquivos os commits modificaram, adicionaram ou excluíram. A partir do {% data variables.product.prodname_desktop %}, você pode abrir repositórios no seu editor de texto preferido para visualizar quaisquer alterações ou fazer alterações adicionais. Após revisar alterações em um pull request, você poderá dar um feedback em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre merges do pull request](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)". -If checks have been enabled in your repository, {% data variables.product.prodname_desktop %} will show the status of the checks on the pull request and allow you to re-run checks. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)." +Se as verificações tiverem sido habilitadas no seu repositório, {% data variables.product.prodname_desktop %} mostrará o status das verificações no pull request e permitirá que você execute as verificações novamente. Para obter mais informações, consulte "[Visualização e reexecução de verificações no GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)". ## Visualizar um pull request em {% data variables.product.prodname_desktop %} {% data reusables.desktop.current-branch-menu %} diff --git a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md index b64026f492..1e4046dabb 100644 --- a/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md +++ b/translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md @@ -1,25 +1,25 @@ --- -title: Viewing and re-running checks in GitHub Desktop -shortTitle: Viewing and re-running checks -intro: 'You can view the status of checks and re-run them in {% data variables.product.prodname_desktop %}.' +title: Visualizando e executando novamente as verificações no GitHub Desktop +shortTitle: Visualizando e executando novamente as verificações +intro: 'Você pode visualizar o status de verificações e executá-las novamente em {% data variables.product.prodname_desktop %}.' versions: fpt: '*' --- -## About checks in {% data variables.product.prodname_desktop %} +## Sobre as verificações em {% data variables.product.prodname_desktop %} -{% data variables.product.prodname_desktop %} displays the status of checks that have run in your pull request branches. The checks badge next to the branch name will display the *pending, passing,* or *failing* state of the checks. You can also re-run all, failed, or individual checks when viewing the status of the checks in {% data variables.product.prodname_desktop %}. For more information on setting up checks in your repository, see "[About status checks](/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." +{% data variables.product.prodname_desktop %} exibe o status das verificações que executaram em seus branches de pull request. O selo de verificação ao lado do nome do branch exibirá o status de *pendente, passando,* ou *falhando* das verificações. Você também pode executar novamente todas falhas, ou verificações individuais ao visualizar o status das verificações em {% data variables.product.prodname_desktop %}. Para obter mais informações sobre como configurar verificações no seu repositório, consulte "[Sobre verificações de status](/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)". -{% data variables.product.prodname_desktop %} will also show a system notification when checks fail. For more information on enabling notifications, see "[Configuring notifications in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop)." +O {% data variables.product.prodname_desktop %} também mostrará uma notificação do sistema quando a verificação falhar. Para obter mais informações sobre notificações de habilitação, consulte "[Configurando notificações no GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop)". -## Viewing and re-running checks +## Visualizando e executando novamente as verificações {% data reusables.desktop.current-branch-menu %} {% data reusables.desktop.click-pull-requests %} ![Guia Pull requests no menu suspenso Branch atual](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png) {% data reusables.desktop.choose-pr-from-list %} ![Lista de pull requests em aberto no repositório](/assets/images/help/desktop/click-pull-request.png) -4. Click on the pull request number, to the right of the pull request branch name. ![Checks display next to branch name](/assets/images/help/desktop/checks-dialog.png) -5. To re-run failed checks, click **{% octicon "sync" aria-label="The sync icon" %} Re-run** and select **Re-run Failed Checks**. ![Re-run failed checks](/assets/images/help/desktop/re-run-failed-checks.png) -6. To re-run individual checks, hover over the individual check you want to re-run and select the {% octicon "sync" aria-label="The sync icon" %} icon to re-run the check. ![Re-run individual checks](/assets/images/help/desktop/re-run-individual-checks.png) -7. You will see a confirmation dialog with the summary of the checks that will be re-run. Click **Re-run Checks** to confirm that you want to perform the re-run. ![Re-run confirmation dialog](/assets/images/help/desktop/re-run-confirmation-dialog.png) +4. Clique no número do pull request, à direita do nome do branch do pull request. ![Exibição das verificações ao lado do nome do branch](/assets/images/help/desktop/checks-dialog.png) +5. Para executar novamente as verificações que falharam, clique em **{% octicon "sync" aria-label="The sync icon" %} Re-executar** e selecione **Executar novamente as verificações que falharam**. ![Executar novamente verificações falhadas](/assets/images/help/desktop/re-run-failed-checks.png) +6. Para executar novamente as verificações individuais, passe o mouse sobre a verificação individual que você deseja executar novamente e selecione o ícone {% octicon "sync" aria-label="The sync icon" %} para executar a verificação novamente. ![Executar novamente as verificações individuais](/assets/images/help/desktop/re-run-individual-checks.png) +7. Você verá uma caixa de diálogo com o resumo das verificações que serão executadas novamente. Clique em **Verificações da nova execução** para confirmar que você deseja executar a nova execução. ![Executar o diálogo de confirmação novamente](/assets/images/help/desktop/re-run-confirmation-dialog.png) diff --git a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md index 91a4d97265..4625830d96 100644 --- a/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md +++ b/translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md @@ -17,7 +17,7 @@ O {% data variables.product.prodname_desktop %} é compatível com os seguintes - [Atom](https://atom.io/) - [MacVim](https://macvim-dev.github.io/macvim/) -- [Visual Studio Code](https://code.visualstudio.com/) +- [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) - [Visual Studio Codium](https://vscodium.com/) - [Sublime Text](https://www.sublimetext.com/) - [BBEdit](http://www.barebones.com/products/bbedit/) @@ -44,7 +44,7 @@ O {% data variables.product.prodname_desktop %} é compatível com os seguintes {% windows %} - [Atom](https://atom.io/) -- [Visual Studio Code](https://code.visualstudio.com/) +- [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) - [Visual Studio Codium](https://vscodium.com/) - [Sublime Text](https://www.sublimetext.com/) - [ColdFusion Builder](https://www.adobe.com/products/coldfusion-builder.html) diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md index 231aa9af8d..23e44738f6 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md @@ -89,7 +89,7 @@ Você pode selecionar permissões em uma string de consultas usando o nome da pe | [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Concede acesso à [API de conteúdo](/rest/reference/repos#contents). Pode ser: `nenhum`, `leitura` ou `gravação`. | | [`estrela`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Concede acesso à [API estrelada](/rest/reference/activity#starring). Pode ser: `nenhum`, `leitura` ou `gravação`. | | [`Status`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Concede acesso à [API de status](/rest/reference/commits#commit-statuses). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Concede acesso à [API de discussões de equipe](/rest/reference/teams#discussions) e à [API de comentários de discussão de equipe](/rest/reference/teams#discussion-comments). Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Concede acesso à [API de discussões de equipe](/rest/reference/teams#discussions) e à [API de comentários de discussão de equipe](/rest/reference/teams#discussion-comments). Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghes or ghae or ghec %} | `vulnerability_alerts` | Concede acesso para receber {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis em um repositório. Consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" para saber mais. Pode ser: `none` ou `read`.{% endif %} | `inspecionando` | Concede acesso à lista e alterações de repositórios que um usuário assinou. Pode ser: `nenhum`, `leitura` ou `gravação`. | diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index 1a7c1c2f40..a37000fa48 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -239,8 +239,8 @@ Embora a maior parte da interação da sua API deva ocorrer usando os tokens de * [Listar implementações](/rest/reference/deployments#list-deployments) * [Criar uma implementação](/rest/reference/deployments#create-a-deployment) -* [Obter uma implementação](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %} -* [Excluir um deploy](/rest/reference/deployments#delete-a-deployment){% endif %} +* [Get a deployment](/rest/reference/deployments#get-a-deployment) +* [Delete a deployment](/rest/reference/deployments#delete-a-deployment) #### Eventos @@ -422,14 +422,12 @@ Embora a maior parte da interação da sua API deva ocorrer usando os tokens de * [Remover a aplicação do hook pre-receive para uma organização](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} #### Projetos da aquipe da organização * [Listar projetos da equipe](/rest/reference/teams#list-team-projects) * [Verificar permissões da equipe para um projeto](/rest/reference/teams#check-team-permissions-for-a-project) * [Adicionar ou atualizar as permissões do projeto da equipe](/rest/reference/teams#add-or-update-team-project-permissions) * [Remover um projeto de uma equipe](/rest/reference/teams#remove-a-project-from-a-team) -{% endif %} #### Repositórios da equipe da organização @@ -575,7 +573,7 @@ Embora a maior parte da interação da sua API deva ocorrer usando os tokens de #### Reações -{% ifversion fpt or ghes or ghae or ghec %}* [Excluir uma reação](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [Excluir uma reação](/rest/reference/reactions#delete-a-reaction){% endif %} +* [Delete a reaction](/rest/reference/reactions) * [Listar reações para um comentário de commit](/rest/reference/reactions#list-reactions-for-a-commit-comment) * [Criar reação para um comentário de commit](/rest/reference/reactions#create-reaction-for-a-commit-comment) * [Listar reações para um problema](/rest/reference/reactions#list-reactions-for-an-issue) @@ -587,13 +585,13 @@ Embora a maior parte da interação da sua API deva ocorrer usando os tokens de * [Listar reações para um comentário de discussão de equipe](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) * [Criar reação para um comentário de discussão em equipe](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) * [Listar reações para uma discussão de equipe](/rest/reference/reactions#list-reactions-for-a-team-discussion) -* [Criar reação para uma discussão de equipe](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %} +* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion) * [Excluir uma reação de comentário de commit](/rest/reference/reactions#delete-a-commit-comment-reaction) * [Excluir uma reação do problema](/rest/reference/reactions#delete-an-issue-reaction) * [Excluir uma reação a um comentário do commit](/rest/reference/reactions#delete-an-issue-comment-reaction) * [Excluir reação de comentário do pull request](/rest/reference/reactions#delete-a-pull-request-comment-reaction) * [Excluir reação para discussão em equipe](/rest/reference/reactions#delete-team-discussion-reaction) -* [Excluir reação de comentário para discussão de equipe](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} +* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction) #### Repositórios @@ -707,11 +705,9 @@ Embora a maior parte da interação da sua API deva ocorrer usando os tokens de * [Obter um README do repositório](/rest/reference/repos#get-a-repository-readme) * [Obter a licença para um repositório](/rest/reference/licenses#get-the-license-for-a-repository) -{% ifversion fpt or ghes or ghae or ghec %} #### Envio de eventos do repositório * [Criar um evento de envio de repositório](/rest/reference/repos#create-a-repository-dispatch-event) -{% endif %} #### Hooks do repositório 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 536a60b8f8..b44bc852bf 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 @@ -333,7 +333,7 @@ Para criar esse vínculo, você precisará do `client_id` dos aplicativos OAuth, * "[Solucionando erros de solicitação de autorização](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" * "[Solucionando erros na requisição de token de acesso do aplicativo OAuth](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" -* "[Erros de fluxo do dispositivo](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +* "[Erros de fluxo do dispositivo](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} * "[Vencimento e revogação do Token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} ## Leia mais diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md index e3a6e23d85..a211c5a565 100644 --- a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md @@ -48,7 +48,7 @@ X-Accepted-OAuth-Scopes: user |  `repo_deployment` | Concede acesso aos [status da implementação](/rest/reference/repos#deployments) para {% ifversion not ghae %}público{% else %}interno{% endif %} e repositórios privados. Este escopo só é necessário para conceder a outros usuários ou serviços acesso aos status de implantação, *sem* conceder acesso ao código.{% ifversion not ghae %} |  `public_repo` | Limita o acesso a repositórios públicos. Isso inclui acesso de leitura/gravação em código, status de commit, projetos de repositório, colaboradores e status de implantação de repositórios e organizações públicos. Também é necessário para repositórios públicos marcados como favoritos.{% endif %} |  `repo:invite` | Concede habilidades de aceitar/recusar convites para colaborar em um repositório. Este escopo só é necessário para conceder a outros usuários ou serviços acesso a convites *sem* conceder acesso ao código.{% ifversion fpt or ghes or ghec %} -|  `security_events` | Grants:
read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) {%- ifversion ghec %}
read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning){%- endif %}
This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %} +|  `security_events` | Concede:
acesso de leitura e gravação aos eventos de segurança na [API de {% data variables.product.prodname_code_scanning %}](/rest/reference/code-scanning) {%- ifversion ghec %}
acesso de leitura e gravação aos eventos de segurança na [API de {% data variables.product.prodname_secret_scanning %}](/rest/reference/secret-scanning){%- endif %}
Esse escopo é somente necessário para conceder aos outros usuários ou serviços acesso aos eventos de segurança *sem* conceder acesso ao código.{% endif %} | **`admin:repo_hook`** | Concede acesso de leitura, gravação, fixação e exclusão aos hooks do repositório em {% ifversion fpt %}repositórios públicos, privados ou internos{% elsif ghec or ghes %}públicos, ou internos{% elsif ghae %}privados ou internos{% endif %}. O escopos do `repo` {% ifversion fpt or ghec or ghes %}e `public_repo` concedem{% else %}o escopo concede{% endif %} o acesso total aos repositórios, incluindo hooks de repositório. Use o escopo `admin:repo_hook` para limitar o acesso apenas a hooks de repositório. | |  `write:repo_hook` | Concede acesso de leitura, gravação e fixação aos hooks em {% ifversion fpt %}repositórios públicos ou privados{% elsif ghec or ghes %}público, privado ou interno{% elsif ghae %}privado ou interno{% endif %}. | |  `read:repo_hook` | Concede acesso de leitura e fixação aos hooks em {% ifversion fpt %}repositórios públicos ou privados{% elsif ghec or ghes %}público, privado ou interno{% elsif ghae %}privado ou interno{% endif %}. | @@ -67,9 +67,9 @@ X-Accepted-OAuth-Scopes: user |  `user:follow` | Concede acesso para seguir ou deixar de seguir outros usuários. | | **`delete_repo`** | Concede acesso para excluir repositórios administráveis. | | **`write:discussion`** | Permite acesso de leitura e gravação para discussões da equipe. | -|  `leia:discussion` | Allows read access for team discussions. | +|  `leia:discussion` | Permite acesso de leitura para discussões em equipe. | | **`write:packages`** | Concede acesso ao para fazer o upload ou publicação de um pacote no {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Publicar um pacote](/github/managing-packages-with-github-packages/publishing-a-package)". | -| **`read:packages`** | Concede acesso ao download ou instalação de pacotes do {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)".{% ifversion fpt or ghec or ghes > 3.1 or ghae %} +| **`read:packages`** | Concede acesso ao download ou instalação de pacotes do {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Instalando um pacote](/github/managing-packages-with-github-packages/installing-a-package)".{% ifversion fpt or ghec or ghes > 3.1 or ghae %} | **`delete:packages`** | Concede acesso para excluir pacotes de {% data variables.product.prodname_registry %}. Para obter mais informações, consulte "[Excluindo e restaurando um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %} | **`admin:gpg_key`** | Gerenciar totalmente as chaves GPG. | |  `write:gpg_key` | Criar, listar e visualizar informações das chaves GPG. | diff --git a/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md index faf692b415..fbd2ee7079 100644 --- a/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md +++ b/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md @@ -85,7 +85,7 @@ Tenha em mente essas ideias ao usar os tokens de acesso pessoais: * Você pode realizar solicitações de cURL únicas. * Você pode executar scripts pessoais. * Não configure um script para toda a sua equipe ou empresa usá-lo. -* Não configure uma conta pessoal compartilhada para agir atuar um usuário bot.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %} +* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} * Defina um vencimento para os seus tokens de acesso pessoais para ajudar a manter suas informações seguras.{% endif %} ## Determinar qual integração criar diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md index ab35ae9809..99b6df1b91 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md @@ -89,4 +89,4 @@ A sua linguagem e implementações do servidor podem ser diferentes deste códig * Não **se recomenda** usar um operador simples de`==`. Um método como [`secure_compare`][secure_compare] executa uma comparação de strings "tempo constante", o que ajuda a mitigar certos ataques de tempo contra operadores de igualdade regular. -[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare +[secure_compare]: https://rubydoc.info/github/rack/rack/main/Rack/Utils:secure_compare diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 05211df4f9..fe433b49be 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -353,10 +353,10 @@ Os eventos de webhook são acionados com base na especificidade do domínio que ### Objeto da carga do webhook -| Tecla | Tipo | Descrição | -| ------------- | ------------------------------------------- | -------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} -| `Ação` | `string` | A ação realizada. Pode ser `criado`.{% endif %} -| `implantação` | `objeto` | A [implantação](/rest/reference/deployments#list-deployments). | +| Tecla | Tipo | Descrição | +| ------------- | -------- | -------------------------------------------------------------- | +| `Ação` | `string` | A ação realizada. Pode ser `criado`. | +| `implantação` | `objeto` | A [implantação](/rest/reference/deployments#list-deployments). | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -378,14 +378,14 @@ Os eventos de webhook são acionados com base na especificidade do domínio que ### Objeto da carga do webhook -| Tecla | Tipo | Descrição | -| ---------------------------------- | ------------------------------------------- | ------------------------------------------------------------------------------------------------ |{% ifversion fpt or ghes or ghae or ghec %} -| `Ação` | `string` | A ação realizada. Pode ser `criado`.{% endif %} -| `implantação_status` | `objeto` | O [status da implantação](/rest/reference/deployments#list-deployment-statuses). | -| `deployment_status["state"]` | `string` | O novo estado. Pode ser `pendente`, `sucesso`, `falha` ou `erro`. | -| `deployment_status["target_url"]` | `string` | O link opcional adicionado ao status. | -| `deployment_status["description"]` | `string` | A descrição opcional legível para pessoas adicionada ao status. | -| `implantação` | `objeto` | A [implantação](/rest/reference/deployments#list-deployments) à qual este status está associado. | +| Tecla | Tipo | Descrição | +| ---------------------------------- | -------- | ------------------------------------------------------------------------------------------------ | +| `Ação` | `string` | A ação realizada. Pode ser `criado`. | +| `implantação_status` | `objeto` | O [status da implantação](/rest/reference/deployments#list-deployment-statuses). | +| `deployment_status["state"]` | `string` | O novo estado. Pode ser `pendente`, `sucesso`, `falha` ou `erro`. | +| `deployment_status["target_url"]` | `string` | O link opcional adicionado ao status. | +| `deployment_status["description"]` | `string` | A descrição opcional legível para pessoas adicionada ao status. | +| `implantação` | `objeto` | A [implantação](/rest/reference/deployments#list-deployments) à qual este status está associado. | {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} @@ -1154,7 +1154,6 @@ As entregas para eventos `review_requested` e `review_request_removed` terão um {{ webhookPayloadsForCurrentVersion.release.published }} -{% ifversion fpt or ghes or ghae or ghec %} ## repository_dispatch Este evento ocorre quando um {% data variables.product.prodname_github_app %} envia uma solicitação de `POST` para o "[Crie um evento de envio de repositório](/rest/reference/repos#create-a-repository-dispatch-event)" endpoint. @@ -1166,7 +1165,6 @@ Este evento ocorre quando um {% data variables.product.prodname_github_app %} en ### Exemplo de carga de webhook {{ webhookPayloadsForCurrentVersion.repository_dispatch }} -{% endif %} ## repositório @@ -1490,7 +1488,7 @@ Esse evento ocorre quando alguém aciona a execução de um fluxo de trabalho no {{ webhookPayloadsForCurrentVersion.workflow_dispatch }} {% endif %} -{% ifversion fpt or ghes > 3.2 or ghec or ghae-issue-4462 %} +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## workflow_job diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students.md index 5639c27608..632f4a27f2 100644 --- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students.md +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students.md @@ -15,7 +15,7 @@ shortTitle: Para alunos Usar o {% data variables.product.prodname_dotcom %} nos projetos da sua escola é uma maneira prática de colaborar com outras pessoas e de criar um portfólio que demonstra experiência no mundo real. -Cada pessoa com uma conta do {% data variables.product.prodname_dotcom %} pode colaborar em repositórios públicos e privados ilimitados com o {% data variables.product.prodname_free_user %}. As a student, you can also apply for GitHub Student benefits. Para obter mais informações, consulte "[Aplicar um pacote de desenvolvedor para estudante](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" e [{% data variables.product.prodname_education %}](https://education.github.com/). +Cada pessoa com uma conta do {% data variables.product.prodname_dotcom %} pode colaborar em repositórios públicos e privados ilimitados com o {% data variables.product.prodname_free_user %}. Como estudante, você também pode candidatar-se aos benefícios do GitHub Student. Para obter mais informações, consulte "[Aplicar um pacote de desenvolvedor para estudante](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)" e [{% data variables.product.prodname_education %}](https://education.github.com/). Se você for integrante de um clube de robótica FIRST, seu mentor poderá solicitar um desconto para educador para que sua equipe possa colaborar usando o {% data variables.product.prodname_team %}, que permite repositórios privados e de usuários ilimitados, gratuitamente. Para obter mais informações, consulte "[Aplicar um desconto para educador ou pesquisador](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)". diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md index e1fcf7cb48..83437b27ce 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md @@ -1,39 +1,39 @@ --- title: Sobre usar o Visual Studio Code com o GitHub Classroom shortTitle: Sobre o uso do Visual Studio Code -intro: 'Você pode configurar o Visual Studio Code como editor preferido para atividades em {% data variables.product.prodname_classroom %}.' +intro: 'You can configure {% data variables.product.prodname_vscode %} as the preferred editor for assignments in {% data variables.product.prodname_classroom %}.' versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/about-using-vs-code-with-github-classroom --- -## Sobre o Visual Studio Code +## Sobre o {% data variables.product.prodname_vscode %} -O Visual Studio Code é um editor de código leve, mas poderoso que é executado no seu computador e está disponível para Windows, macOS e Linux. Com a extensão [do GitHub Classroom para o Visual Studio Code](https://aka.ms/classroom-vscode-ext), os alunos podem facilmente navegar, editar, enviar, colaborar e testar suas atividades do Classroom. Para obter mais informações sobre IDEs e {% data variables.product.prodname_classroom %}, consulte "[Integrar {% data variables.product.prodname_classroom %} a um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". +{% data variables.product.prodname_vscode %} is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. With the [GitHub Classroom extension for {% data variables.product.prodname_vscode_shortname %}](https://aka.ms/classroom-vscode-ext), students can easily browse, edit, submit, collaborate, and test their Classroom Assignments. Para obter mais informações sobre IDEs e {% data variables.product.prodname_classroom %}, consulte "[Integrar {% data variables.product.prodname_classroom %} a um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". ### Editor da escolha do seu aluno -A integração ao Visual Studio Code no GitHub oferece aos alunos um pacote de extensões que contém: +The GitHub Classroom integration with {% data variables.product.prodname_vscode_shortname %} provides students with an extension pack which contains: 1. [Extensão GitHub Classroom](https://aka.ms/classroom-vscode-ext) com abstrações personalizadas que facilitam o início da navegação dos alunos. 2. A [Extensão do Visual Studio Live Share](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare-pack) foi integrada a uma visualização do aluno para facilitar o acesso a assistentes de ensino e colegas de classe para ajuda e colaboração. 3. A [Extensão do GitHub Pull Request](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) permite que os alunos vejam comentários de seus instrutores no editor. -### Como iniciar a atividade no Visual Studio Code -Ao criar uma atividade, o Visual Studio Code pode ser adicionado como editor preferido de uma atividade. Para obter mais informações consulte "[Integrar {% data variables.product.prodname_classroom %} a um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". +### How to launch the assignment in {% data variables.product.prodname_vscode_shortname %} +When creating an assignment, {% data variables.product.prodname_vscode_shortname %} can be added as the preferred editor for an assignment. Para obter mais informações consulte "[Integrar {% data variables.product.prodname_classroom %} a um IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)". -Isto incluirá um selo "Abrir no Visual Studio Code" em todos os repositórios de alunos. Este selo gerencia a instalação do Visual Studio Code, o pacote de extensões para o Classroom e a abertura da tarefa ativa com um clique. +This will include an "Open in {% data variables.product.prodname_vscode_shortname %}" badge in all student repositories. This badge handles installing {% data variables.product.prodname_vscode_shortname %}, the Classroom extension pack, and opening to the active assignment with one click. {% note %} -**Observação:** O aluno deve ter o Git instalado no seu computador para enviar o código do Visual Studio Code para o seu repositório. Isso não é instalado automaticamente ao clicar no botão **Abrir no Visual Studio Code**. O aluno pode fazer o download do Git em [aqui](https://git-scm.com/downloads). +**Note:** The student must have Git installed on their computer to push code from {% data variables.product.prodname_vscode_shortname %} to their repository. This is not automatically installed when clicking the **Open in {% data variables.product.prodname_vscode_shortname %}** button. O aluno pode fazer o download do Git em [aqui](https://git-scm.com/downloads). {% endnote %} ### Como usar o pacote de extensão GitHub Classroom A extensão GitHub Classroom tem dois componentes principais: a visualização "salas de aula" e a visualização "atividade ativa". -Quando o aluno lança a extensão pela primeira vez, ele é direcionado automaticamente para a aba Explorador no Visual Studio Code, onde ele pode ver a visualização de "atividade ativa" ao lado da exibição em árvore de arquivos no repositório. +When the student launches the extension for the first time, they are automatically navigated to the Explorer tab in {% data variables.product.prodname_vscode_shortname %}, where they can see the "Active Assignment" view alongside the tree-view of files in the repository. ![Visão da atividade ativa do GitHub Classroom](/assets/images/help/classroom/vs-code-active-assignment.png) diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md index 84eec97529..651a18f6cd 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md @@ -25,7 +25,7 @@ Depois que um aluno aceita um trabalho com um IDE, o arquivo README no repositó |:--------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | {% data variables.product.prodname_github_codespaces %} | "[Usando {% data variables.product.prodname_github_codespaces %} com {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)" | | Microsoft MakeCode Arcade | "[Sobre o uso do Arcade MakeCode com {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | -| Visual Studio Code | [Extensão de {% data variables.product.prodname_classroom %}](http://aka.ms/classroom-vscode-ext) no Marketplace do Visual Studio | +| {% data variables.product.prodname_vscode %} | [Extensão de {% data variables.product.prodname_classroom %}](http://aka.ms/classroom-vscode-ext) no Marketplace do Visual Studio | Sabemos que as integrações do IDE na nuvem são importantes para a sua sala de aula e que estão trabalhando para trazer mais opções. @@ -33,13 +33,13 @@ Sabemos que as integrações do IDE na nuvem são importantes para a sua sala de Você pode escolher o IDE que desejar usar para uma atividade quando criar uma atividade. Para aprender a criar uma nova atividade que utiliza um ID, consulte "[Criar uma atividade individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" ou "[Criar uma atividade em grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)". -## Setting up an assignment in a new IDE +## Configurando uma atividade em um novo IDE -The first time you configure an assignment using a different IDE, you must ensure that it is set up correctly. +A primeira vez que você configurar uma atividade usando um IDE diferente, você deve garantir que ela seja configurada corretamente. -Unless you use {% data variables.product.prodname_github_codespaces %}, you must authorize the OAuth app for the IDE for your organization. Para todos os repositórios, conceda acesso de **leitura** do aplicativo aos metadados, administração, código e acesso de **gravação** à administração e código. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/github/authenticating-to-github/authorizing-oauth-apps)". +A menos que você use {% data variables.product.prodname_github_codespaces %}, você deve autorizar o aplicativo OAuth para o IDE para sua organização. Para todos os repositórios, conceda acesso de **leitura** do aplicativo aos metadados, administração, código e acesso de **gravação** à administração e código. Para obter mais informações, consulte "[Autorizar aplicativos OAuth](/github/authenticating-to-github/authorizing-oauth-apps)". -{% data variables.product.prodname_github_codespaces %} does not require an OAuth app, but you need to enable {% data variables.product.prodname_github_codespaces %} for your organization to be able to configure an assignment with {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Usar o {% data variables.product.prodname_github_codespaces %} com o {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#enabling-codespaces-for-your-organization)". +{% data variables.product.prodname_github_codespaces %} não exige um aplicativo OAuth, mas você precisa habilitar {% data variables.product.prodname_github_codespaces %} para sua organização para poder configurar uma atividade com {% data variables.product.prodname_codespaces %}. Para obter mais informações, consulte "[Usar o {% data variables.product.prodname_github_codespaces %} com o {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#enabling-codespaces-for-your-organization)". ## Leia mais diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md index b79ce25212..d9bc1818a3 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md @@ -1,8 +1,8 @@ --- -title: Using GitHub Codespaces with GitHub Classroom -shortTitle: Using Codespaces with GitHub Classroom +title: Usando GitHub Codespaces com GitHub Classroom +shortTitle: Usando os codespaces com GitHub Classroom product: '{% data reusables.gated-features.codespaces-classroom-articles %}' -intro: 'You can use {% data variables.product.prodname_github_codespaces %} as the preferred editor in your assignments to give students access to a browser-based Visual Studio Code environment with one-click setup.' +intro: 'Você pode usar {% data variables.product.prodname_github_codespaces %} como editor preferido nas suas atividades para dar aos alunos acesso a um ambiente do Visual Studio Code baseado no navegador com configuração em um clique.' versions: fpt: '*' permissions: 'Organization owners who are admins for a classroom can enable {% data variables.product.prodname_github_codespaces %} for their organization and integrate {% data variables.product.prodname_github_codespaces %} as the supported editor for an assignment. {% data reusables.classroom.classroom-admins-link %}' @@ -10,78 +10,78 @@ permissions: 'Organization owners who are admins for a classroom can enable {% d ## Sobre o {% data variables.product.prodname_codespaces %} -{% data variables.product.prodname_github_codespaces %} é um ambiente de desenvolvimento instantâneo e baseado na nuvem que usa um recipiente para fornecer linguagens, ferramentas e utilitários de desenvolvimento comuns. {% data variables.product.prodname_codespaces %} is also configurable, allowing you to create a customized development environment that is the same for all users of your project. For more information, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)." +{% data variables.product.prodname_github_codespaces %} é um ambiente de desenvolvimento instantâneo e baseado na nuvem que usa um recipiente para fornecer linguagens, ferramentas e utilitários de desenvolvimento comuns. {% data variables.product.prodname_codespaces %} também pode ser configurado, o que permite que você crie um ambiente de desenvolvimento personalizado que é o mesmo para todos os usuários do seu projeto. Para obter mais informações, consulte "[Visão geral de {% data variables.product.prodname_github_codespaces %}](/codespaces/overview)". -Once {% data variables.product.prodname_codespaces %} is enabled in an organization or enterprise, users can create a codespace from any branch or commit in an organization or enterprise repository and begin developing using cloud-based compute resources. You can connect to a codespace from the browser or locally using Visual Studio Code. {% data reusables.codespaces.links-to-get-started %} +Uma vez que {% data variables.product.prodname_codespaces %} é habilitado em uma organização ou empresa, os usuários podem criar um codespace a partir de qualquer branch ou commit em uma organização ou repositório corporativo e começar a desenvolver recursos de computação baseados na nuvem. Você pode se conectar a um codespace do navegador ou localmente usando o Visual Studio Code. {% data reusables.codespaces.links-to-get-started %} -Setting {% data variables.product.prodname_codespaces %} as the preferred editor for an assignment in GitHub Classroom assignments, is beneficial for both students and teachers. {% data variables.product.prodname_codespaces %} is a good option for students using loaned devices or without access to a local IDE setup, since each codespace is cloud-based and requires no local setup. Students can launch a codespace for an assignment repository in Visual Studio Code directly in their browser, and begin developing right away without needing any further configuration. +Definir {% data variables.product.prodname_codespaces %} como editor preferido para uma atividade nas atividades do GitHub Classroom é vantajoso para alunos e professores. {% data variables.product.prodname_codespaces %} é uma boa opção para alunos que usam dispositivos emprestados ou sem acesso a uma configuração local do IDE, já que cada codespace é baseado na nuvem e não exige nenhuma configuração local. Os alunos podem lançar um codespace para um repositório de atividade no Visual Studio Code diretamente em seu navegador e começar a desenvolver imediatamente, sem precisar de qualquer configuração adicional. -For assignments with complex setup environments, teachers can customize the dev container configuration for a repository's codespaces. This ensures that when a student creates a codespace, it automatically opens with the development environment configured by the teacher. Para obter mais informações sobre contêineres de desenvolvimento, consulte "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)". +Para atividades com ambientes de configuração complexos, os professores podem personalizar a configuração do contêiner de desenvolvimento para os codespaces de um repositório. Isto garante que, quando um aluno cria um codespace, ele será aberto automaticamente com o ambiente de desenvolvimento configurado pelo professor. Para obter mais informações sobre contêineres de desenvolvimento, consulte "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)". -## About the {% data variables.product.prodname_codespaces %} Education benefit for verified teachers +## Sobre o benefício de educação de {% data variables.product.prodname_codespaces %} para professores verificados -The {% data variables.product.prodname_codespaces %} Education benefit gives verified teachers a free monthly allowance of {% data variables.product.prodname_codespaces %} hours to use in {% data variables.product.prodname_classroom %}. The free allowance is estimated to be enough for a class of 50 with 5 assignments per month, on a 2 core machine with 1 codespace stored per student. +O benefício da educação de {% data variables.product.prodname_codespaces %} dá aos professores verificados um subsídio mensal gratuito de horas de {% data variables.product.prodname_codespaces %} para ser usado em {% data variables.product.prodname_classroom %}. Estima-se que o subsídio gratuito seja suficiente para uma classe de 50 com 5 atribuições por mês. em uma máquina central com 1 codespace armazenado por aluno. {% data reusables.classroom.free-limited-codespaces-for-verified-teachers-beta-note %} -To become a verified teacher, you need to be approved for an educator or teacher benefit. For more information, see "[Applying for an educator or teacher benefit](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount#applying-for-an-educator-or-researcher-discount)." +Para tornar-se um professor verificado, você precisa ser aprovado para obter um benefício de educador para o professor. Para obter mais informações, consulte "[Candidatando-se a um benefício de professor ou educador](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount#applying-for-an-educator-or-researcher-discount)." -After you have confirmation that you are a verified teacher, visit [Global Campus for Teachers](https://education.github.com/globalcampus/teacher) to upgrade the organization to GitHub Team. For more information, see [GitHub's products](/get-started/learning-about-github/githubs-products#github-team). +Depois de ter confirmado que você é um professor verificado, acesse [Campus global](https://education.github.com/globalcampus/teacher) para que os professores atualizem a organização para a equipe do GitHub. Para obter mais informações, consulte [Produtos do GitHub](/get-started/learning-about-github/githubs-products#github-team). -If you are eligible for the {% data variables.product.prodname_codespaces %} Education benefit, when you enable {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_classroom %} for your organization, GitHub automatically adds a Codespace policy to restrict machine types for all codespaces in the organization to 2 core machines. This helps you make the most of the free {% data variables.product.prodname_codespaces %} usage. However, you can change or remove these policies in your organization settings. Para obter mais informações, consulte "[Restringindo o acesso aos tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)." +Se você for elegível ao benefício de Educação de {% data variables.product.prodname_codespaces %}, ao habilitar {% data variables.product.prodname_codespaces %} em {% data variables.product.prodname_classroom %} para sua organização, o GitHub adiciona automaticamente uma política de codespace para restringir os tipos de máquina para todos os codespaces da organização a duas máquinas principais. Isso ajuda você a aproveitar ao máximo o uso gratuito de {% data variables.product.prodname_codespaces %}. No entanto, você pode alterar ou remover essas políticas nas configurações da sua organização. Para obter mais informações, consulte "[Restringindo o acesso aos tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)." -When the {% data variables.product.prodname_codespaces %} Education benefit moves out of beta, if your organization exceeds their free allowance for {% data variables.product.prodname_codespaces %} usage, your organization will be billed for additional usage. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#about-billing-for-codespaces)". +Quando o benefício da educação de {% data variables.product.prodname_codespaces %} sai do beta, se sua organização exceder o limite de uso gratuito de {% data variables.product.prodname_codespaces %}, a sua organização será cobrada por uso adicional. Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#about-billing-for-codespaces)". ## Habilitando {% data variables.product.prodname_codespaces %} para a sua organização -{% data variables.product.prodname_codespaces %} is available to use with {% data variables.product.prodname_classroom %} for organizations that use {% data variables.product.prodname_team %}. If you are eligible for the {% data variables.product.prodname_codespaces %} Education benefit, you must enable {% data variables.product.prodname_codespaces %} through {% data variables.product.prodname_classroom %}, instead of enabling it directly in your organization settings. Otherwise, your organization will be billed directly for all usage of {% data variables.product.prodname_codespaces %}. +{% data variables.product.prodname_codespaces %} está disponível para uso com {% data variables.product.prodname_classroom %} para as organizações que usam {% data variables.product.prodname_team %}. Se você for elegível para o benefício de educação de {% data variables.product.prodname_codespaces %}, você deverá habilitar {% data variables.product.prodname_codespaces %} por meio de {% data variables.product.prodname_classroom %} ao invés de habilitá-lo diretamente nas configurações da sua organização. Caso contrário, sua organização será cobrada diretamente por todo o uso de {% data variables.product.prodname_codespaces %}. -### Enabling Codespaces for an organization when creating a new classroom +### Habilitando codespaces para uma organização ao criar uma nova sala de aula {% data reusables.classroom.sign-into-github-classroom %} 1. Clique em **Nova sala de aula**. ![Botão "Nova sala de aula"](/assets/images/help/classroom/click-new-classroom-button.png) -1. Na lista de organizações, clique na organização que você gostaria de usar para a sua sala de aula. Organizations that are eligible for {% data variables.product.prodname_codespaces %} will have a note showing that they are eligible. Opcionalmente, você pode criar uma nova organização. Para obter mais informações, consulte "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". +1. Na lista de organizações, clique na organização que você gostaria de usar para a sua sala de aula. As organizações elegíveis para {% data variables.product.prodname_codespaces %} terão uma observação que mostrará que são elegíveis. Opcionalmente, você pode criar uma nova organização. Para obter mais informações, consulte "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". - ![Choose organization for classroom with codespaces eligibility](/assets/images/help/classroom/org-view-codespaces-eligibility.png) + ![Escolha uma organização para a sala de aula com elegibilidade de codespaces](/assets/images/help/classroom/org-view-codespaces-eligibility.png) -1. In the "Name your classroom" page, under "{% data variables.product.prodname_codespaces %} in your Classroom", click **Enable**. Note that this will enable {% data variables.product.prodname_codespaces %} for all repositories and users in the organization. +1. Na página "Nomeie sua sala de aula", embaixo de "{% data variables.product.prodname_codespaces %} na sua sala de aula, clique em **Habilitar**. Observe que isto irá habilitar {% data variables.product.prodname_codespaces %} para todos os repositórios e usuários da organização. - ![Enable Codespaces for org in "Setup classroom basics" page](/assets/images/help/classroom/setup-classroom-enable-codespaces-button.png) + ![Habilite codespaces para organizações na página "Configuração básica de sala de aula"](/assets/images/help/classroom/setup-classroom-enable-codespaces-button.png) -1. When you are ready to create the new classroom, click **Create classroom**. +1. Quando você estiver pronto para criar a nova sala de aula, clique em **Criar sala de aula**. -### Enabling Codespaces for an organization via an existing classroom +### Habilitando codespaces para uma organização por meio de uma sala de aula existente {% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-settings %} -1. Under "{% data variables.product.prodname_github_codespaces %}", click **Enable**. This will enable {% data variables.product.prodname_codespaces %} for all repositories and users in the organization. A new Codespace policy is also added to restrict machine types for all codespaces in the organization to 2 core machines. +1. Em "{% data variables.product.prodname_github_codespaces %}", clique em **Habilitar**. Isto habilitará {% data variables.product.prodname_codespaces %} para todos os repositórios e usuários da organização. Uma nova política de codespace também é adicionada para restringir tipos de máquinas para todos os codespaces da organização a duas máquinas principais. - ![Enable Codespaces for org in existing classroom settings](/assets/images/help/classroom/classroom-settings-enable-codespaces-button.png) + ![Havilite codespaces para organizações nas configurações existentes da sala de aula](/assets/images/help/classroom/classroom-settings-enable-codespaces-button.png) -You can use the same methods as above to disable {% data variables.product.prodname_codespaces %} for your organization as well. Note that this will disable {% data variables.product.prodname_codespaces %} for all users and repositories in the organization. +Você pode usar os mesmos métodos do método acima para desabilitar {% data variables.product.prodname_codespaces %} também para sua organização. Observe que isso irá desabilitar {% data variables.product.prodname_codespaces %} para todos os usuários e repositórios da organização. -## Configuring an assignment to use {% data variables.product.prodname_codespaces %} -To make {% data variables.product.prodname_codespaces %} available to students for an assignment, you can choose {% data variables.product.prodname_codespaces %} as the supported editor for the assignment. When creating a new assignment, in the "Add your starter code and choose your optional online IDE" page, under "Add a supported editor", select **{% data variables.product.prodname_github_codespaces %}** from the dropdown menu. +## Configurando uma atividade para usar {% data variables.product.prodname_codespaces %} +Para disponibilizar {% data variables.product.prodname_codespaces %} aos alunos para uma atividade, você pode escolher {% data variables.product.prodname_codespaces %} como o editor compatível para a atividade. Ao criar uma nova atividade, na página "Adicionar seu código inicial e escolher seu ID on-line opcional" em "Adicionar um editor compatível", selecione **{% data variables.product.prodname_github_codespaces %}** no menu suspenso. -![Select Codespaces as supported editor for assignment](/assets/images/help/classroom/select-supported-editor-including-codespaces.png) +![Selecione os codespaces como editor compatível para a atividade](/assets/images/help/classroom/select-supported-editor-including-codespaces.png) -If you use a template repository for an assignment, you can define a dev container in the repository to customize the tools and runtimes available to students when they launch a codespace to work on the assignment. If you do not define a dev container, {% data variables.product.prodname_github_codespaces %} will use a default configuration, which contains many of the common tools that your students might need for development. For more information on defining a dev container, see "[Add a dev container configuration to your repository](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)." +Se você usar o repositório de um modelo para uma atividade, você pode definir um contêiner de desenvolvimento no repositório para personalizar as ferramentas e tempos de execução disponíveis para os alunos quando executarem um codespace para trabalhar na atividade. Se você não definir um contêiner de desenvolvimento, {% data variables.product.prodname_github_codespaces %} usará uma configuração padrão, que contém muitas das ferramentas comuns que seus alunos podem precisar para o desenvolvimento. Para obter mais informações sobre a definição de um contêiner de desenvolvimento, consulte "[Adicionar uma configuração de contêiner de desenvolvimento ao seu repositório](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)." -## Launching an assignment using {% data variables.product.prodname_codespaces %} +## Iniciando uma atividade usando {% data variables.product.prodname_codespaces %} -When a student opens an assignment, the repository's README file includes their teacher's recommendation of the IDE they should use for the work. +Quando um aluno abre uma atividade, o arquivo LEIAME do repositório inclui a recomendação de seu professor sobre o IDE, que ele deve usar para o trabalho. -![Screenshot of the Codespaces note in the README for a student assignment repository](/assets/images/help/classroom/student-codespaces-readme-link.png) +![Captura de tela da observação dos codespaces no README para um repositório de atividade do aluno](/assets/images/help/classroom/student-codespaces-readme-link.png) -Students can launch a new or existing codespace by clicking the **{% octicon "code" aria-label="The code icon" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". +Os alunos podem iniciar um codespace novo ou existente, clicando no botão **Código de {% octicon "code" aria-label="The code icon" %}** na página principal do repositório de atividades e, em seguida, selecionando a aba **Codespaces**. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". -![Launch new codespace in assignment repository](/assets/images/help/classroom/student-launch-new-codespace.png) +![Iniciar novo codespace no repositório das atividades](/assets/images/help/classroom/student-launch-new-codespace.png) -Teachers can view each student's codespace for an assignment in the assignment overview page. You can click on the Codespaces icon on the right side of each student row to launch the codespace. +Os professores podem ver o codespace de cada aluno para uma atividade na página de visão geral da atividade. Você pode clicar no ícone de codespace no lado direito de cada linha do aluno para iniciar o codespace. -![Teacher assignment overview with student's codespaces](/assets/images/help/classroom/teacher-assignment-view-with-codespaces.png) +![Visão geral da atividade do professor com os codespaces do aluno](/assets/images/help/classroom/teacher-assignment-view-with-codespaces.png) -When you connect to a codespace through a browser, auto-save is enabled automatically. If you want to save changes to the repository, you will need to commit the changes and push them to a remote branch. If you leave your codespace running without interaction for 30 minutes by default, the codespace will timeout and stop running. Your data will be preserved from the last time you made a change. Para obter mais informações sobre o ciclo de vida de um codespace, consulte "[Ciclo de vida dos codespaces](/codespaces/developing-in-codespaces/codespaces-lifecycle)". +Ao conectar-se a um codespace por meio de um navegador, o salvamento automático é habilitado automaticamente. Se você quiser salvar as alterações no repositório, você deverá fazer um commit das alterações e enviá-las por push para um branch remoto. Se você deixar seu codespace em execução sem interação durante 30 minutos por padrão, o seu tempo de execução irá esgostar-se e parar de executar. Os dados da última vez que você fez uma alteração serão preservados. Para obter mais informações sobre o ciclo de vida de um codespace, consulte "[Ciclo de vida dos codespaces](/codespaces/developing-in-codespaces/codespaces-lifecycle)". diff --git a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md index d9a438986b..85c39a7f17 100644 --- a/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md +++ b/translations/pt-BR/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md @@ -47,7 +47,7 @@ Você deve autorizar o aplicativo OAuth {% data variables.product.prodname_class 1. Clique em **Nova sala de aula**. ![Botão "Nova sala de aula"](/assets/images/help/classroom/click-new-classroom-button.png) {% data reusables.classroom.guide-create-new-classroom %} -Depois de criar uma sala de aula, você pode começar a criar atividades para os alunos. For more information, see "[Use the Git and {% data variables.product.company_short %} starter assignment](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)," "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)," "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)," or "[Reuse an assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment)." +Depois de criar uma sala de aula, você pode começar a criar atividades para os alunos. Para obter mais informações, consulte "[Use o Git e as atividades iniciais de {% data variables.product.company_short %}](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)," "[Crie uma atividade individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)," "[Crie uma atividade em grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)," ou "[Reutilize uma atividade](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment)." ## Criando uma lista para sua sala de aula 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 324d48998a..9e431220d3 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 @@ -1,6 +1,6 @@ --- -title: GitHub extensions and integrations -intro: 'Use {% data variables.product.product_name %} extensions to work seamlessly in {% data variables.product.product_name %} repositories within third-party applications.' +title: Extensões e integrações do GitHub +intro: 'Use extensões {% data variables.product.product_name %} para trabalhar com facilidade nos repositórios {% data variables.product.product_name %} dentro de aplicativos de terceiros.' redirect_from: - /articles/about-github-extensions-for-third-party-applications - /articles/github-extensions-and-integrations @@ -9,48 +9,49 @@ redirect_from: versions: fpt: '*' ghec: '*' -shortTitle: Extensions & integrations +shortTitle: Extensões & integrações --- -## Editor tools -You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and Visual Studio. +## Ferramentas de edição -### {% data variables.product.product_name %} for Atom +You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and {% data variables.product.prodname_vs %}. -With the {% data variables.product.product_name %} for Atom extension, you can commit, push, pull, resolve merge conflicts, and more from the Atom editor. For more information, see the official [{% data variables.product.product_name %} for Atom site](https://github.atom.io/). +### {% data variables.product.product_name %} para Atom -### {% data variables.product.product_name %} for Unity +É possível fazer commits, push, pull, resolver conflitos de merge e mais no editor Atom, usando a extensão {% data variables.product.product_name %} para Atom. Para obter mais informações, consulte o site oficial [{% data variables.product.product_name %} para Atom](https://github.atom.io/). -With the {% data variables.product.product_name %} for Unity editor extension, you can develop on Unity, the open source game development platform, and see your work on {% data variables.product.product_name %}. For more information, see the official Unity editor extension [site](https://unity.github.com/) or the [documentation](https://github.com/github-for-unity/Unity/tree/master/docs). +### {% data variables.product.product_name %} para Unity -### {% data variables.product.product_name %} for Visual Studio +Você pode desenvolver em Unity, a plataforma de desenvolvimento de jogos de código aberto, e ver seu trabalho em {% data variables.product.product_name %}, usando a extensão de editor {% data variables.product.product_name %} para Unity. Para obter mais informações, consulte o [site](https://unity.github.com/) oficial da extensão de editor Unity ou a [documentação](https://github.com/github-for-unity/Unity/tree/master/docs). -With the {% data variables.product.product_name %} for Visual Studio extension, you can work in {% data variables.product.product_name %} repositories without leaving Visual Studio. For more information, see the official Visual Studio extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs). +### {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} -### {% data variables.product.prodname_dotcom %} for Visual Studio Code +With the {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} extension, you can work in {% data variables.product.product_name %} repositories without leaving {% data variables.product.prodname_vs %}. For more information, see the official {% data variables.product.prodname_vs %} extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs). -With the {% data variables.product.prodname_dotcom %} for Visual Studio Code extension, you can review and manage {% data variables.product.product_name %} pull requests in Visual Studio Code. For more information, see the official Visual Studio Code extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github). +### {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} -## Project management tools +With the {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} extension, you can review and manage {% data variables.product.product_name %} pull requests in {% data variables.product.prodname_vscode_shortname %}. For more information, see the official {% data variables.product.prodname_vscode_shortname %} extension [site](https://vscode.github.com/) or [documentation](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. +## Ferramentas de gerenciamento de projetos -### Jira Cloud and {% data variables.product.product_name %}.com integration +Você pode integrar a sua conta pessoal ou de organização no {% data variables.product.product_location %} com ferramentas de gerenciamento de projetos de terceiros, como o Jira. -You can integrate Jira Cloud with your personal or organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues. For more information, visit the [Jira integration app](https://github.com/marketplace/jira-software-github) in the marketplace. +### Integração Jira Cloud e {% data variables.product.product_name %}.com -## Team communication tools +É possível integrar o Jira Cloud à sua conta pessoal ou de sua organização para analisar commits e pull requests e criar metadados e hyperlinks relevantes em qualquer problema mencionado no Jira. Para obter mais informações, visite o [aplicativo de integração do Jira](https://github.com/marketplace/jira-software-github) no marketplace. -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. +## Ferramentas de comunicação de equipe -### Slack and {% data variables.product.product_name %} integration +Você pode integrar sua conta pessoal ou de organização no {% data variables.product.product_location %} com ferramentas de comunicação de equipes de terceiros, como o Slack ou o Microsoft Teams. -The Slack + {% data variables.product.prodname_dotcom %} app lets you 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 opening and closing issues, and you can see detailed references to issues and pull requests without leaving Slack. The app will also ping you personally in Slack if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats. +### Integração com Slack e {% data variables.product.product_name %} -The Slack + {% 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 + {% data variables.product.prodname_dotcom %} app](https://github.com/marketplace/slack-github) in the marketplace. +O aplicativo Slack + de {% data variables.product.prodname_dotcom %} permite que você assine seus repositórios ou organizações e obtenha atualizações em tempo real sobre problemas, pull requests, commits, discussões, versões, revisões de implantação e status da implantação. Você também pode executar atividades como abrir e fechar problemas, além de poder ver referências detalhadas para problemas e pull requests sem sair do Slack. O aplicativo também irá marcar você pessoalmente no Slack se você for mencionado como parte de quaisquer notificações de {% data variables.product.prodname_dotcom %} que você receber nos seus canais ou chats pessoais. -### Microsoft Teams and {% data variables.product.product_name %} integration +O aplicativo Slack + de {% data variables.product.prodname_dotcom %} também é compatível com a [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). Para obter mais informações, acesse o [o aplicativo Slack + de {% data variables.product.prodname_dotcom %}](https://github.com/marketplace/slack-github) no marketplace. -The {% data variables.product.prodname_dotcom %} for Teams app lets you 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 opening and closing issues, commenting on your issues and pull requests, and you can see detailed references to issues and pull requests without leaving Microsoft Teams. The app will also ping you personally in Teams if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats. +### Integração com o Microsoft Teams e {% data variables.product.product_name %} -For more information, visit the [{% data variables.product.prodname_dotcom %} for Teams app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource. +O {% data variables.product.prodname_dotcom %} para o aplicativo Teams permite que você assine seus repositórios ou organizações e obtenha atualizações em tempo real sobre problemas, pull requests, commits, discussões, versões, revisões de implantação e status da implantação. Você também pode realizar atividades como abrir e fechar problemas, comentar nos seus problemase pull requests, e você pode ver referências detalhadas a problemas e pull requests sem sair do Microsoft Teams. O aplicativo também irá marcar você pessoalmente no Teams se você for mencionado como parte de quaisquer notificações de {% data variables.product.prodname_dotcom %} que você receber nos seus canais ou chats pessoais. + +Para obter mais informações, acesse [{% data variables.product.prodname_dotcom %} para o aplicativo Teams](https://appsource.microsoft.com/en-us/product/office/WA200002077) no Microsoft AppSource. diff --git a/translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md index 878a144689..4ca8095cfa 100644 --- a/translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/pt-BR/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -25,7 +25,7 @@ Se houver um tópico específico que lhe interessa, visite `github.com/topics/ 3.1 or ghec or ghae-issue-4864 %} +{% ifversion fpt or ghes > 3.1 or ghec or ghae %} - **Revisão de dependências** - Mostra o impacto total das alterações nas dependências e vê detalhes de qualquer versão vulnerável antes de realizar o 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 %} diff --git a/translations/pt-BR/content/get-started/learning-about-github/about-versions-of-github-docs.md b/translations/pt-BR/content/get-started/learning-about-github/about-versions-of-github-docs.md index de8b8b7fbc..be86fc6687 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/about-versions-of-github-docs.md +++ b/translations/pt-BR/content/get-started/learning-about-github/about-versions-of-github-docs.md @@ -37,7 +37,7 @@ Na janela ampla de um navegador, não há texto que siga imediatamente o logotip Em {% data variables.product.prodname_dotcom_the_website %}, cada conta tem seu próprio plano. Cada conta pessoal tem um plano associado que oferece acesso a determinadas funcionalidades, e cada organização tem um plano associado diferente. Se a sua conta pessoal for integrante de uma organização em {% data variables.product.prodname_dotcom_the_website %}, você poderá ter acesso a diferentes funcionalidades quando usar recursos pertencentes a essa organização do que quando você usa recursos pertencentes à sua conta pessoal. Para obter mais informações, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)". -Se você não sabe se uma organização usa o {% data variables.product.prodname_ghe_cloud %}, pergunte ao proprietário de uma organização. Para obter mais informações, consulte "[Visualizando as funções das pessoas em uma organização](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)". +Se você não sabe se uma organização usa o {% data variables.product.prodname_ghe_cloud %}, pergunte ao proprietário de uma organização. Para obter mais informações, consulte "[Visualizando as funções das pessoas em uma organização](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)". ### {% data variables.product.prodname_ghe_server %} diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md index 0bd690ae58..5aaf1081eb 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -75,7 +75,7 @@ Para obter mais informações sobre como efetuar a autenticação em {% data var | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Acesse {% data variables.product.prodname_dotcom_the_website %} | Se você não precisar trabalhar com arquivos localmente, {% data variables.product.product_name %} permite que você realize a maioria das ações relacionadas ao Gits diretamente no navegador, da criação e bifurcação de repositórios até a edição de arquivos e abertura de pull requests. | Esse método é útil se você quiser uma interface visual e precisar fazer mudanças rápidas e simples que não requerem trabalho local. | | {% data variables.product.prodname_desktop %} | O {% data variables.product.prodname_desktop %} amplia e simplifica o fluxo de trabalho no {% data variables.product.prodname_dotcom_the_website %} com uma interface visual, em vez de comandos de texto na linha de comando. Para obter mais informações sobre como começar com {% data variables.product.prodname_desktop %}, consulte "[Primeiros passos com o {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)". | Este método é melhor se você precisa ou deseja trabalhar com arquivos localmente, mas preferir usar uma interface visual para usar o Git e interagir com {% data variables.product.product_name %}. | -| Editor de IDE ou de texto | Você pode definir um editor de texto padrão, curtir [Atom](https://atom.io/) ou [Visual Studio Code](https://code.visualstudio.com/) para abrir e editar seus arquivos com o Git, usar extensões e ver a estrutura do projeto. Para obter mais informações, consulte "[Associando editores de texto ao Git](/github/using-git/associating-text-editors-with-git)". | Isto é conveniente se você estiver trabalhando com arquivos e projetos mais complexos e quiser ter tudo em um só lugar, uma vez que os editores de texto ou IDEs muitas vezes permitem que você acesse diretamente a linha de comando no editor. | +| Editor de IDE ou de texto | You can set a default text editor, like [Atom](https://atom.io/) or [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. Para obter mais informações, consulte "[Associando editores de texto ao Git](/github/using-git/associating-text-editors-with-git)". | Isto é conveniente se você estiver trabalhando com arquivos e projetos mais complexos e quiser ter tudo em um só lugar, uma vez que os editores de texto ou IDEs muitas vezes permitem que você acesse diretamente a linha de comando no editor. | | Linha de comando, com ou sem {% data variables.product.prodname_cli %} | Para o controle e personalização mais granulares de como você usa o Git e interage com {% data variables.product.product_name %}, você pode usar a linha de comando. Para obter mais informações sobre como usar comandos do Git, consulte "[Folha de informações do Git](/github/getting-started-with-github/quickstart/git-cheatsheet).

{% data variables.product.prodname_cli %} é uma ferramenta separada de linha de comando separada que você pode instalar e que traz pull requests, problemas, {% data variables.product.prodname_actions %}, e outros recursos de {% data variables.product.prodname_dotcom %} para o seu terminal, para que você possa fazer todo o seu trabalho em um só lugar. Para obter mais informações, consulte "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)". | Isto é muito conveniente se você já estiver trabalhando na linha de comando, o que permite que você evite mudar o contexto, ou se você estiver mais confortável usando a linha de comando. | | {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} tem uma API REST e uma API do GraphQL que você pode usar para interagir com {% data variables.product.product_name %}. Para obter mais informações, consulte "[Primeiros passos com a API](/github/extending-github/getting-started-with-the-api)". | A API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} seria muito útil se você quisesse automatizar tarefas comuns, fazer backup dos seus dados ou criar integrações que estendem {% data variables.product.prodname_dotcom %}. | ### 4. Escrevendo em {% data variables.product.product_name %} diff --git a/translations/pt-BR/content/get-started/quickstart/communicating-on-github.md b/translations/pt-BR/content/get-started/quickstart/communicating-on-github.md index cdaa67dc5c..9aa5148716 100644 --- a/translations/pt-BR/content/get-started/quickstart/communicating-on-github.md +++ b/translations/pt-BR/content/get-started/quickstart/communicating-on-github.md @@ -117,7 +117,6 @@ Este exemplo mostra a postagem de boas-vindas de {% data variables.product.prodn Este mantenedor da comunidade iniciou uma discussão para dar as boas-vindas à comunidade e pedir aos integrantes que se apresentem. Esta postagem promove uma atmosfera de acolhedora para visitantes e contribuidores. A postagem também esclarece que a equipe tem o prazer em ajudar com as contribuições para o repositório. {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} ### Cenários para discussões em equipe - Tenho uma pergunta que não é necessariamente relacionada a arquivos específicos no repositório. @@ -140,8 +139,6 @@ O integrante da equipe do `octocat` publicou uma discussão sobre a equipe, info - Há uma postagem no blogue que descreve como as equipes usam {% data variables.product.prodname_actions %} para produzir sua documentação. - Material sobre a "All Hands" de Abril agora está disponível para ver todos os integrantes da equipe. -{% endif %} - ## Próximas etapas Estes exemplos mostraram como decidir qual é a melhor ferramenta para suas conversas em {% data variables.product.product_name %}. Mas esse é apenas o começo; há muito mais que você pode fazer para adaptar essas ferramentas às suas necessidades. diff --git a/translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md b/translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md index 87cfa7198a..38af8136a3 100644 --- a/translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md +++ b/translations/pt-BR/content/get-started/quickstart/git-and-github-learning-resources.md @@ -19,7 +19,7 @@ shortTitle: Recursos de aprendizagem ## Usar o Git -Familiarize-se com o Git acessando o [site oficial do projeto Git](https://git-scm.com) e lendo o [livro do ProGit](http://git-scm.com/book). You can also review the [Git command list](https://git-scm.com/docs). +Familiarize-se com o Git acessando o [site oficial do projeto Git](https://git-scm.com) e lendo o [livro do ProGit](http://git-scm.com/book). Você também pode revisar a [lista de comandos Git](https://git-scm.com/docs). ## Usar {% data variables.product.product_name %} diff --git a/translations/pt-BR/content/get-started/using-github/github-command-palette.md b/translations/pt-BR/content/get-started/using-github/github-command-palette.md index d916b7a80a..316e333784 100644 --- a/translations/pt-BR/content/get-started/using-github/github-command-palette.md +++ b/translations/pt-BR/content/get-started/using-github/github-command-palette.md @@ -153,7 +153,7 @@ Estes comandos estão disponíveis em todos os escopos. | `Nova organização` | Criar uma nova organização Para obter mais informações, consulte "[Criar uma nova organização do zero](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)". | | `Novo projeto` | Criar um novo quadro de projeto. Para obter mais informações, consulte "[Criar um quadro de projeto](/issues/trying-out-the-new-projects-experience/creating-a-project)". | | `Novo repositório` | Criar um novo repositório a partir do zero. Para obter mais informações, consulte "[Criar um novo repositório](/repositories/creating-and-managing-repositories/creating-a-new-repository)." | -| `Alterar tema para ` | Mude diretamente para um tema diferente para a interface do usuário. Para obter mais informações, consulte "[Gerenciando as suas configurações de tema](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)". | +| `Alterar tema para ` | Mude diretamente para um tema diferente para a interface do usuário. Para obter mais informações, consulte "[Gerenciando as suas configurações de tema](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)". | ### Comandos da organização diff --git a/translations/pt-BR/content/get-started/using-github/github-mobile.md b/translations/pt-BR/content/get-started/using-github/github-mobile.md index c197d3935b..487072bd8f 100644 --- a/translations/pt-BR/content/get-started/using-github/github-mobile.md +++ b/translations/pt-BR/content/get-started/using-github/github-mobile.md @@ -25,10 +25,13 @@ Com o {% data variables.product.prodname_mobile %} você pode: - Leia, analisar e colaborar em problemas e pull requests - Pesquisar, navegar e interagir com usuários, repositórios e organizações - Receber uma notificação push quando alguém mencionar seu nome de usuário -{% ifversion fpt or ghec %}- Proteja sua conta do GitHub.com com autenticação de dois fatores{% endif %} +{% ifversion fpt or ghec %}- Proteja sua conta do GitHub.com com autenticação de dois fatores +- Verify your sign in attempts on unrecognized devices{% endif %} Para mais informações sobre notificações para {% data variables.product.prodname_mobile %}, consulte "[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)." +{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)." {% endif %} + ## Instalar o {% data variables.product.prodname_mobile %} Para instalar {% data variables.product.prodname_mobile %} para Android ou iOS, consulte [{% data variables.product.prodname_mobile %}](https://github.com/mobile). @@ -45,7 +48,7 @@ Você pode estar conectado simultaneamente em um celular com uma conta pessoal e Você precisa instalar {% data variables.product.prodname_mobile %} 1.4 ou superior no seu dispositivo para usar {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}. -Para usar {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} deve ser a versão 3.0 ou superior, e o proprietário da empresa deverá habilitar o suporte móvel para a sua empresa. Para obter mais informações, consulte {% ifversion ghes %}"[Observações de versão](/enterprise-server/admin/release-notes)e {% endif %}"[Gerenciando {% data variables.product.prodname_mobile %} para a sua empresa]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" na documentação de {% data variables.product.prodname_ghe_server %}.{% else %}."{% endif %} +Para usar {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}, {% data variables.product.product_location %} deve ser a versão 3.0 ou superior, e o proprietário da empresa deverá habilitar o suporte móvel para a sua empresa. For more information, see {% ifversion ghes %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %} Durante o beta para {% data variables.product.prodname_mobile %} com {% data variables.product.prodname_ghe_server %}, você deve estar conectado com uma conta pessoal em {% data variables.product.prodname_dotcom_the_website %}. @@ -73,9 +76,9 @@ Se você configurar o idioma do seu dispositivo para um idioma compatível, {% d {% data variables.product.prodname_mobile %} ativa automaticamente o Universal Links para iOS. Quando você clica em qualquer link {% data variables.product.product_name %}, a URL de destino vai abrir em {% data variables.product.prodname_mobile %} em vez do Safari. Para obter mais informações, consulte [Universal Links](https://developer.apple.com/ios/universal-links/) no site de desenvolvedor da Apple -Para desabilitar os links universais, mantenha qualquer link {% data variables.product.product_name %} pressionado e, em seguida, pressione **Abrir**. Toda vez que você clica em um link {% data variables.product.product_name %} no futuro, a URL de destino abrirá no Safari em vez do {% data variables.product.prodname_mobile %}. +To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Every time you tap a {% data variables.product.product_name %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}. -Para reabilitar o Universal Links, mantenha pressionado qualquer link {% data variables.product.product_name %}, depois clique em **Abrir em {% data variables.product.prodname_dotcom %}**. +To re-enable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**. ## Compartilhando feedback diff --git a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md index 576d591c0b..e71d19d62f 100644 --- a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md +++ b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md @@ -20,7 +20,7 @@ versions: Digitar ? no {% data variables.product.prodname_dotcom %} exibe uma caixa de diálogo que lista os atalhos de teclado disponíveis para essa página. Você pode usar esses atalhos de teclado para executar ações no site sem precisar usar o mouse para navegar. {% if keyboard-shortcut-accessibility-setting %} -É possível desabilitar os atalhos de teclas de caractere, ao mesmo tempo em que permite que os atalhos que usam teclas modificadoras, nas suas configurações de acessibilidade. Para obter mais informações, consulte "[Gerenciar configurações de acessibilidade](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings)".{% endif %} +É possível desabilitar os atalhos de teclas de caractere, ao mesmo tempo em que permite que os atalhos que usam teclas modificadoras, nas suas configurações de acessibilidade. Para obter mais informações, consulte "[Gerenciar configurações de acessibilidade](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings)".{% endif %} Veja abaixo uma lista dos atalhos de teclado disponíveis. {% if command-palette %} @@ -28,11 +28,11 @@ O {% data variables.product.prodname_command_palette %} também fornece acesso r ## Atalhos para o site -| Atalho | Descrição | -| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| S or / | Evidencia a barra de pesquisa. Para obter mais informações, consulte "[Sobre pesquisar no {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". | -| G N | Vai para suas notificações. Para obter mais informações, consulte {% ifversion fpt or ghes or ghae or ghec %}"[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications)"{% endif %}." | -| Esc | Quando direcionado a um hovercard de usuário, problema ou pull request, fecha o hovercard e redireciona para o elemento no qual o hovercard está | +| Atalho | Descrição | +| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| S or / | Evidencia a barra de pesquisa. Para obter mais informações, consulte "[Sobre pesquisar no {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)". | +| G N | Vai para suas notificações. Para obter mais informações, consulte "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications)". | +| Esc | Quando direcionado a um hovercard de usuário, problema ou pull request, fecha o hovercard e redireciona para o elemento no qual o hovercard está | {% if command-palette %} @@ -106,7 +106,6 @@ Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://cod {% endif %} | R | Cita o texto selecionado em sua resposta. Para obter mais informações, consulte "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax#quoting-text)". | - ## Listas de problemas e pull requests | Atalho | Descrição | @@ -135,16 +134,15 @@ Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://cod ## Alterações em pull requests -| Atalho | Descrição | -| ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| C | Abre a lista de commits na pull request | -| T | Abre a lista de arquivos alterados na pull request | -| J | Move a seleção para baixo na lista | -| K | Move a seleção para cima na lista | -| Command+Shift+Enter | Adiciona um comentário único no diff da pull request | -| Alt e clique | Alterna entre opções de recolhimento e expansão de todos os comentários de revisão desatualizados em uma pull request ao manter pressionada a tecla Alt e clicar em **Mostrar desatualizados** ou **Ocultar desatualizados**.|{% ifversion fpt or ghes or ghae or ghec %} -| Clique, em seguida Shift e clique | Comente em várias linhas de uma pull request clicando em um número de linha, mantendo pressionado Shift, depois clique em outro número de linha. Para obter mais informações, consulte "[Comentando em uma pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." -{% endif %} +| Atalho | Descrição | +| ---------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| C | Abre a lista de commits na pull request | +| T | Abre a lista de arquivos alterados na pull request | +| J | Move a seleção para baixo na lista | +| K | Move a seleção para cima na lista | +| Command+Shift+Enter | Adiciona um comentário único no diff da pull request | +| Alt e clique | Alterna entre opções de recolhimento e expansão de todos os comentários de revisão desatualizados em uma pull request ao manter pressionada a tecla Alt e clicar em **Mostrar desatualizados** ou **Ocultar desatualizados**. | +| Clique, em seguida Shift e clique | Comente em várias linhas de uma pull request clicando em um número de linha, mantendo pressionado Shift, depois clique em outro número de linha. Para obter mais informações, consulte "[Comentando em uma pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)." | ## Quadros de projeto @@ -200,7 +198,7 @@ Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://cod {% endif %} ## Notificações -{% ifversion fpt or ghes or ghae or ghec %} + | Atalho | Descrição | | ----------------------------- | -------------------- | | E | Marcar como pronto | @@ -208,13 +206,6 @@ Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://cod | Shift+I | Marca como lido | | Shift+M | Cancelar assinatura | -{% else %} - -| Atalho | Descrição | -| -------------------------------------------- | --------------- | -| E ou I ou Y | Marca como lido | -| Shift+M | Desativa o som | -{% endif %} ## gráfico de rede diff --git a/translations/pt-BR/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/pt-BR/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md index 01d0c95e83..763924935d 100644 --- a/translations/pt-BR/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ b/translations/pt-BR/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md @@ -61,7 +61,6 @@ O gist permite mapeamento de arquivos geoJSON. Esses mapas são exibidos em gist Siga os passos abaixo para criar um gist. -{% ifversion fpt or ghes or ghae or ghec %} {% note %} Você também pode criar um gist usando o {% data variables.product.prodname_cli %}. Para obter mais informações, consulte "[`gh gist cria`](https://cli.github.com/manual/gh_gist_create)" na documentação do {% data variables.product.prodname_cli %}. @@ -69,7 +68,6 @@ Você também pode criar um gist usando o {% data variables.product.prodname_cli Como alternativa, você pode arrastar e soltar um arquivo de texto da sua área de trabalho diretamente no editor. {% endnote %} -{% endif %} 1. Entre no {% data variables.product.product_name %}. 2. Navegue até sua {% data variables.gists.gist_homepage %}. 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 3e82f45b86..bd13c371b5 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 @@ -29,18 +29,19 @@ Ao usar dois ou mais cabeçalhos, o GitHub gera automaticamente uma tabela de co ![Captura de tela que destaca o ícone da tabela de conteúdo](/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`. +You can indicate emphasis with bold, italic, strikethrough, subscript, or superscript text in comment fields and `.md` files. -| Estilo | Sintaxe | Atalho | Exemplo | Resultado | -| -------------------------- | ------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------- | ------------------------------------------ | -| Negrito | `** **` ou `__ __` | Command+B (Mac) ou Ctrl+B (Windows/Linux) | `**Esse texto está em negrito**` | **Esse texto está em negrito** | -| Itálico | `* *` ou `_ _`      | Command+I (Mac) ou Ctrl+I (Windows/Linux) | `*Esse texto está em itálico*` | *Esse texto está em itálico* | -| Tachado | `~~ ~~` | | `~~Esse texto estava errado~~` | ~~Esse texto estava errado~~ | -| Negrito e itálico aninhado | `** **` e `_ _` | | `**Esse texto é _extremamente_ importante**` | **Esse texto é _extremamente_ importante** | -| Todo em negrito e itálico | `*** ***` | | `***Todo esse texto é importante***` | ***Todo esse texto é importante*** | +| Estilo | Sintaxe | Atalho | Exemplo | Resultado | +| -------------------------- | -------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------- | ------------------------------------------ | +| Negrito | `** **` ou `__ __` | Command+B (Mac) ou Ctrl+B (Windows/Linux) | `**Esse texto está em negrito**` | **Esse texto está em negrito** | +| Itálico | `* *` ou `_ _`      | Command+I (Mac) ou Ctrl+I (Windows/Linux) | `*Esse texto está em itálico*` | *Esse texto está em itálico* | +| Tachado | `~~ ~~` | | `~~Esse texto estava errado~~` | ~~Esse texto estava errado~~ | +| Negrito e itálico aninhado | `** **` e `_ _` | | `**Esse texto é _extremamente_ importante**` | **Esse texto é _extremamente_ importante** | +| Todo em negrito e itálico | `*** ***` | | `***Todo esse texto é importante***` | ***Todo esse texto é importante*** | +| Subscript | ` ` | | `This is a subscript text` | This is a subscript text | +| Superscript | ` ` | | `This is a superscript text` | This is a superscript text | ## Citar texto @@ -235,7 +236,7 @@ Para obter mais informações, consulte "[Sobre listas de tarefas](/articles/abo ## Mencionar pessoas e equipes -Você pode mencionar uma pessoa ou [equipe](/articles/setting-up-teams/) no {% data variables.product.product_name %} digitando @ mais o nome de usuário ou nome da equipe. Isto desencadeará uma notificação e chamará a sua atenção para a conversa. As pessoas também receberão uma notificação se você editar um comentário para mencionar o respectivo nome de usuário ou da equipe. Para obter mais informações, sobre notificações, consulte {% ifversion fpt or ghes or ghae or ghec %}"[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications)"{% endif %}." +Você pode mencionar uma pessoa ou [equipe](/articles/setting-up-teams/) no {% data variables.product.product_name %} digitando @ mais o nome de usuário ou nome da equipe. Isto desencadeará uma notificação e chamará a sua atenção para a conversa. As pessoas também receberão uma notificação se você editar um comentário para mencionar o respectivo nome de usuário ou da equipe. For more information about notifications, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)." {% note %} @@ -296,7 +297,7 @@ Para obter uma lista completa dos emojis e códigos disponíveis, confira [a lis Você pode criar um parágrafo deixando uma linha em branco entre as linhas de texto. -{% ifversion fpt or ghae-issue-5180 or ghes > 3.2 or ghec %} +{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## Notas de rodapé Você pode adicionar notas de rodapé ao seu conteúdo usando esta sintaxe entre colchetes: diff --git a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/index.md b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/index.md index 00e2893e4f..b0a0d799c2 100644 --- a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/index.md +++ b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/index.md @@ -14,6 +14,7 @@ children: - /organizing-information-with-collapsed-sections - /creating-and-highlighting-code-blocks - /creating-diagrams + - /writing-mathematical-expressions - /autolinked-references-and-urls - /attaching-files - /creating-a-permanent-link-to-a-code-snippet diff --git a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md index bb02f0b103..f870386900 100644 --- a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md +++ b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md @@ -15,7 +15,7 @@ topics: ## Vinculando uma pull request a um problema -Para vincular um pull request a um problema a{% ifversion fpt or ghes or ghae or ghec %} mostre que uma correção está em andamento e {% endif %} para fechar o problema automaticamente quando alguém fizer merge do pull request, digite uma das palavras-chave a seguir seguida de uma referência ao problema. Por exemplo, `Closes #10` ou `Fixes octo-org/octo-repo#100`. +To link a pull request to an issue to show that a fix is in progress and to automatically close the issue when someone merges the pull request, type one of the following keywords followed by a reference to the issue. Por exemplo, `Closes #10` ou `Fixes octo-org/octo-repo#100`. * close * closes diff --git a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md new file mode 100644 index 0000000000..6ff758e63f --- /dev/null +++ b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md @@ -0,0 +1,59 @@ +--- +title: Writing mathematical expressions +intro: 'Use Markdown to display mathematical expressions on {% data variables.product.company_short %}.' +versions: + feature: math +shortTitle: Mathematical expressions +--- + +To enable clear communication of mathematical expressions, {% data variables.product.product_name %} supports LaTeX formatted math within Markdown. For more information, see [LaTeX/Mathematics](http://en.wikibooks.org/wiki/LaTeX/Mathematics) in Wikibooks. + +{% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide). + +## Writing inline expressions + +To include a math expression inline with your text, delimit the expression with a dollar symbol `$`. + +``` +This sentence uses `$` delimiters to show math inline: $\sqrt{3x-1}+(1+x)^2$ +``` + +![Inline math markdown rendering](/assets/images/help/writing/inline-math-markdown-rendering.png) + +## Writing expressions as blocks + +To add a math expression as a block, start a new line and delimit the expression with two dollar symbols `$$`. + +``` +**The Cauchy-Schwarz Inequality** + +$$\left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right)$$ +``` + +![Math expression as a block rendering](/assets/images/help/writing/math-expression-as-a-block-rendering.png) + +## Writing dollar signs in line with and within mathematical expressions + +To display a dollar sign as a character in the same line as a mathematical expression, you need to escape the non-delimiter `$` to ensure the line renders correctly. + + - Within a math expression, add a `\` symbol before the explicit `$`. + + ``` + This expression uses `\$` to display a dollar sign: $\sqrt{\$4}$ + ``` + + ![Dollar sign within math expression](/assets/images/help/writing/dollar-sign-within-math-expression.png) + + - Outside a math expression, but on the same line, use span tags around the explicit `$`. + + ``` + To split $100 in half, we calculate $100/2$ + ``` + + ![Dollar sign inline math expression](/assets/images/help/writing/dollar-sign-inline-math-expression.png) + +## Leia mais + +* [The MathJax website](http://mathjax.org) +* [Introdução à escrita e formatação no GitHub](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github) +* [GitHub Flavored Markdown Spec](https://github.github.com/gfm/) diff --git a/translations/pt-BR/content/github/copilot/about-github-copilot-telemetry.md b/translations/pt-BR/content/github/copilot/about-github-copilot-telemetry.md index 545a88d6ea..da046bb0bf 100644 --- a/translations/pt-BR/content/github/copilot/about-github-copilot-telemetry.md +++ b/translations/pt-BR/content/github/copilot/about-github-copilot-telemetry.md @@ -9,7 +9,7 @@ versions: ## Quais dados são coletados -Os dados coletados são descritos nos Termos de Telemetria de[{% data variables.product.prodname_copilot %}](/github/copilot/github-copilot-telemetry-terms)." Além disso, a extensão/plugin de {% data variables.product.prodname_copilot %} coleta a atividade do Ambiente Integrado de Desenvolvimento (IDE), vinculado a um registro de hora, e metadados coletados pelo pacote de telemetria da extensão/plugin. Quando usado com o Visual Studio Code, IntelliJ, NeoVIM, ou outros IDEs, {% data variables.product.prodname_copilot %} coleta os metadados padrão fornecidos por esses IDEs. +Os dados coletados são descritos nos Termos de Telemetria de[{% data variables.product.prodname_copilot %}](/github/copilot/github-copilot-telemetry-terms)." Além disso, a extensão/plugin de {% data variables.product.prodname_copilot %} coleta a atividade do Ambiente Integrado de Desenvolvimento (IDE), vinculado a um registro de hora, e metadados coletados pelo pacote de telemetria da extensão/plugin. When used with {% data variables.product.prodname_vscode %}, IntelliJ, NeoVIM, or other IDEs, {% data variables.product.prodname_copilot %} collects the standard metadata provided by those IDEs. ## Como os dados são usados pelo {% data variables.product.company_short %} diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md index bc5787e7b4..5c32b3b426 100644 --- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md +++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md @@ -30,8 +30,8 @@ Também é possível usar a barra de pesquisa "Filter cards" (Fitrar cartões) q - Filtrar cartões por status de verificação com `status:pending`, `status:success` ou `status:failure` - Filtrar cartões por tipo com `type:issue`, `type:pr` ou `type:note` - Filtrar cartões por estado e tipo com `is:open`, `is:closed` ou `is:merged`; e `is:issue`, `is:pr` ou `is:note` -- Filtrar cartões por problemas vinculados a uma pull request por uma referência de fechamento usando `linked:pr`{% ifversion fpt or ghes or ghae or ghec %} -- Filtrar cartões por repositório em um quadro de projetos de toda a organização usando `repo:ORGANIZATION/REPOSITORY`{% endif %} +- Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr` +- Filtrar cartões por repositório em um quadro de projetos de toda a organização com `repo:ORGANIZATION/REPOSITORY` 1. Navegue até o quadro de projetos que contém os cartões que você deseja filtrar. 2. Acima da coluna cartão de projeto, clique na barra de pesquisa "Filter cards" (Filtrar cartões) e digite uma consulta para filtrar os cartões. ![Barra de pesquisa Filter card (Filtrar cartões)](/assets/images/help/projects/filter-card-search-bar.png) diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md index 25da083395..96fdbd457b 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md @@ -22,7 +22,7 @@ topics: Os problemas permitem que você acompanhe seu trabalho em {% data variables.product.company_short %}, onde o desenvolvimento acontece. Ao mencionar um problema em outro problema ou pull request, a linha do tempo do problema reflete a referência cruzada para que você possa acompanhar o trabalho relacionado. Para indicar que o trabalho está em andamento, você pode vincular um problema a um pull request. Quando o pull request faz merge, o problema vinculado é fechado automaticamente. -For more information on keywords, see "[Linking a pull request to an issue](issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)." +Para obter mais informações sobre palavras-chave, consulte "[Vinculando um pull request a um problema](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)". ## Crie problemas rapidamente @@ -36,7 +36,7 @@ Para obter mais informações sobre os projetos, consulte {% ifversion fpt or gh ## Mantenha-se atualizado -Para manter-se atualizado sobre os comentários mais recentes em um problema, você pode assinar um problema para receber notificações sobre os comentários mais recentes. Para encontrar links para problemas atualizados recentemente nos quais você está inscrito, visite seu painel. Para mais informações, consulte {% ifversion fpt or ghes or ghae or ghec %}"[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}" e "[Sobre o seu painel pessoal](/articles/about-your-personal-dashboard)". +Para manter-se atualizado sobre os comentários mais recentes em um problema, você pode assinar um problema para receber notificações sobre os comentários mais recentes. Para encontrar links para problemas atualizados recentemente nos quais você está inscrito, visite seu painel. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[About your personal dashboard](/articles/about-your-personal-dashboard)." ## Gerenciamento da comunidade diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md index 5395071884..f79a47d131 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md @@ -19,7 +19,9 @@ shortTitle: Atribuir problemas & PRs ## Sobre o problema e os responsáveis por pull request -Você pode atribuir até 10 pessoas a cada problema ou pull request, incluindo a si mesmo, qualquer pessoa que comentou sobre o problema ou pull request, qualquer pessoa com permissões de gravação no repositório e integrantes da organização com permissões de leitura no repositório. Para obter mais informações, consulte "[Permissões de acesso no {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)". +Você pode atribuir várias pessoas a cada problema ou pull request, incluindo a si mesmo, qualquer pessoa que comentou sobre o problema ou pull request, qualquer pessoa com permissões de gravação no repositório e integrantes da organização com permissões de leitura no repositório. Para obter mais informações, consulte "[Permissões de acesso no {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)". + +Os problemas e pull requests em repositórios públicos e em repositórios privados de uma conta paga podem ter até 10 pessoas atribuídas. Os repositórios privados no plano grátis estão limitados a uma pessoa por problema ou pull request. ## Atribuir um problema individual ou pull request diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index a3374c9258..b245ec1f40 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -173,11 +173,9 @@ Com os termos da pesquisa de problemas e pull requests, é possível: {% endtip %} {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} Para problemas, você também pode usar a busca para: - Filtrar por problemas que estão vinculados a uma pull request por uma referência de fechamento: `linked:pr` -{% endif %} Para pull requests, você também pode usar a pesquisa para: - Filtrar pull requests de [rascunho](/articles/about-pull-requests#draft-pull-requests): `is:draft` @@ -188,8 +186,8 @@ Para pull requests, você também pode usar a pesquisa para: - Filtrar pull requests por [revisor](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat` - Filtrar pull requests por usuário específico [solicitado para revisão](/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 %} - Filtrar pull requests que alguém pediu para você revisar diretamente: `state:open type:pr user-review-requested:@me`{% endif %} -- Filtrar pull requests pela equipe solicitada para revisão: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %} -- Filtro por pull requests que estão vinculadas a um problema que a pull request pode concluir: `linked:issue`{% endif %} +- Filtrar pull requests pela equipe solicitada para revisão: `state:open type:pr team-review-requested:github/atom` +- Filtro por pull requests que estão vinculadas a um problema que a pull request pode concluir: `linked:issue` ## Ordenar problemas e pull requests @@ -211,7 +209,6 @@ Você pode ordenar qualquer exibição filtrada por: Para limpar a seleção da ordenação, clique em **Sort** (Ordenar) > **Newest** (Mais recente). - ## Compartilhar filtros Quando você filtra ou ordena problemas e pull requests, a URL do navegador é automaticamente atualizada para corresponder à nova exibição. diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md index 2851b5402f..d242bfcd66 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md @@ -27,7 +27,7 @@ shortTitle: Vincular PR a um problema ## Sobre problemas e pull requests vinculados -Você pode vincular um problema a uma pull request {% ifversion fpt or ghes or ghae or ghec %}manualmente ou {% endif %}usando uma palavra-chave suportada na descrição da pull request. +You can link an issue to a pull request manually or using a supported keyword in the pull request description. Quando você vincula uma pull request ao problema que a pull request tem de lidar, os colaboradores poderão ver que alguém está trabalhando no problema. @@ -35,7 +35,7 @@ Quando você mescla uma pull request vinculada no branch padrão de um repositó ## Vinculando uma pull request a um problema usando uma palavra-chave -You can link a pull request to an issue by using a supported keyword in the pull request's description or in a commit message. The pull request **must be** on the default branch. +Você pode vincular um pull request a um problema, usando uma palavra-chave suportada na descrição do pull request ou em uma mensagem de commit. O pull request **deve estar** no branch padrão. * close * closes @@ -47,7 +47,7 @@ You can link a pull request to an issue by using a supported keyword in the pull * resolve * resolved -Se você usar uma palavra-chave para fazer referência a um comentário de um pull request em outr pull request, os pull requests serão vinculados. Merging the referencing pull request also closes the referenced pull request. +Se você usar uma palavra-chave para fazer referência a um comentário de um pull request em outr pull request, os pull requests serão vinculados. O merge da solicitação do pull request de referência também fecha o pull request referenciado. A sintaxe para fechar palavras-chave depende se o problema está no mesmo repositório que a pull request. @@ -57,11 +57,10 @@ A sintaxe para fechar palavras-chave depende se o problema está no mesmo reposi | Problema em um repositório diferente | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100` | | Múltiplos problemas | Usar sintaxe completa para cada problema | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` | -{% ifversion fpt or ghes or ghae or ghec %}Somente pull requests vinculadas manualmente podem ser desvinculadas. Para desvincular um problema que você vinculou usando uma palavra-chave, você deve editar a descrição da pull request para remover a palavra-chave.{% endif %} +Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword. Você também pode usar palavras-chave de fechamento em uma mensagem de commit. O problema será encerrado quando você mesclar o commit no branch padrão, mas o pull request que contém o commit não será listado como um pull request vinculado. -{% ifversion fpt or ghes or ghae or ghec %} ## Vinculando manualmente uma pull request a um problema Qualquer pessoa com permissões de gravação em um repositório pode vincular manualmente uma pull request a um problema. @@ -77,7 +76,6 @@ Você pode vincular manualmente até dez problemas para cada pull request. O pro 4. Na barra lateral direita, clique em **Linked issues** (Problemas vinculados) ![Problemas vinculados na barra lateral direita](/assets/images/help/pull_requests/linked-issues.png) {% endif %} 5. Clique no problema que você deseja associar à pull request. ![Menu suspenso para problemas vinculados](/assets/images/help/pull_requests/link-issue-drop-down.png) -{% endif %} ## Leia mais diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md index cb9c313967..00cccc6cb2 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md @@ -25,4 +25,4 @@ Os painéis de problemas e pull requests estão disponíveis na parte superior d ## Leia mais -- {% ifversion fpt or ghes or ghae or ghec %}"[Visualizando as suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}"[Listando os repositórios que você está inspecionando](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}" +- "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching)" diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/creating-a-project.md index 80340caa0f..955bcd53d7 100644 --- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/creating-a-project.md +++ b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/creating-a-project.md @@ -163,7 +163,7 @@ Os campos personalizados podem ser texto, número, data, seleção única ou ite 6. Se você especificou **Seleção única** como o tipo, insira as opções. 7. Se você especificou **Iteração** como o tipo, digite a data de início da primeira iteração e a duração da iteração. Três iterações são criadas automaticamente, e você pode adicionar iterações adicionais na página de configurações do projeto. -You can also edit your custom fields. +Você também pode editar seus campos personalizados. {% data reusables.projects.project-settings %} 1. Em **Campos**, selecione o campo que deseja editar. diff --git a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md index 82f2e17373..0c599b3b5e 100644 --- a/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md +++ b/translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md @@ -142,7 +142,7 @@ Para indicar o propósito da visão, dê um nome descritivo. Por fim, adicione um fluxo de trabalho construído para definir o status como **Todo** quando um item for adicionado ao seu projeto. -1. In your project, click {% octicon "workflow" aria-label="the workflow icon" %}. +1. No seu projeto, clique em {% octicon "workflow" aria-label="the workflow icon" %}. 2. Em **Fluxos de trabalho padrão**, clique em **Item adicionado ao projeto**. 3. Ao lado de **Quando**, certifique-se de que `problemas` e `pull requests` estejam selecionados. 4. Ao lado de **Definir**, selecione **Status:Todo**. diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md index 193bd2a4a8..c764ed65f7 100644 --- a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -35,7 +35,7 @@ Na barra lateral esquerda do painel, é possível acessar os principais reposit Na seção "All activity" (Todas as atividades) do seu feed de notícias, você pode ver atualizações de outras equipes e repositórios em sua organização. -A seção "All activity" (Todas as atividades) mostra todas as últimas atividades na organização, inclusive atividades em repositórios que você não assina e de pessoas que você não está seguindo. Para mais informações, consulte {% ifversion fpt or ghes or ghae or ghec %}"[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Inspecionando e não inspecionando repositórios](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}" e "[Seguindo pessoas](/articles/following-people)". +A seção "All activity" (Todas as atividades) mostra todas as últimas atividades na organização, inclusive atividades em repositórios que você não assina e de pessoas que você não está seguindo. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[Following people](/articles/following-people)." Por exemplo, o feed de notícias da organização mostra atualizações quando alguém na organização: - Cria um branch. diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md index e7a3c5f84e..d5aaf5ee40 100644 --- a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md @@ -49,7 +49,7 @@ Você pode formatar o texto e incluir emoji, imagens e GIFs no README do perfil ## Adicionando um perfil README de organização somente apenas para membros -1. If your organization does not already have a `.github-private` repository, create a private repository called `.github-private`. +1. Se sua organização ainda não tiver um repositório `.github-private`, crie um repositório privado denominado `.github-private`. 2. No repositório `.github-private` da sua organização, crie um arquivo `README.md` na pasta `perfil`. 3. Faça o commit das alterações para o arquivo `README.md`. O conteúdo do `README.md` será exibido no modo de exibição do integrante do perfil da sua organização. diff --git a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md index cf8acdf7f5..bef2299ffa 100644 --- a/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md +++ b/translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md @@ -13,7 +13,7 @@ shortTitle: Visualizar ideias da organização permissions: Organization members can view organization insights. --- -## About organization insights +## Sobre insights da organização Você pode usar informações de atividade da organização para entender melhor como os integrantes da sua organização estão usando o {% data variables.product.product_name %} para colaborar e trabalhar no código. As informações de dependência podem ajudar você a monitorar, reportar e agir de acordo com o uso de código aberto da organização. diff --git a/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md index 80c453c867..3e79766081 100644 --- a/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md +++ b/translations/pt-BR/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -32,7 +32,7 @@ Quando alguém posta ou responde a uma discussão pública na página de uma equ {% tip %} -**Dica:** dependendo das suas configurações de notificação, você receberá atualizações por e-mail, pela página de notificações da web no {% data variables.product.product_name %}, ou por ambos. Para obter mais informações, consulte {% ifversion fpt or ghae or ghes or ghec %}"[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[Sobre notificações de e-mail](/github/receiving-notifications-about-activity-on-github/about-email-notifications)" e "[Sobre notificações da web](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}." +**Dica:** dependendo das suas configurações de notificação, você receberá atualizações por e-mail, pela página de notificações da web no {% data variables.product.product_name %}, ou por ambos. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)". {% endtip %} @@ -40,7 +40,7 @@ Por padrão, se seu nome de usuário for mencionado em uma discussão de equipe, Para desativar notificações de discussões de equipe, você pode cancelar a assinatura de uma postagem de discussão específica ou alterar as configurações de notificação para cancelar a inspeção ou ignorar completamente discussões de uma equipe específica. É possível assinar para receber notificações de uma postagem de discussão específica se você estiver cancelando a inspeção de discussões dessa equipe. -Para obter mais informações, consulte {% ifversion fpt or ghae or ghes or ghec %}"[Visualizando suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Cadastrar-se e descadastrar-se para receber notificações](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}" e "[Equipes aninhadas](/articles/about-teams/#nested-teams)." +For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)" and "[Nested teams](/articles/about-teams/#nested-teams)." {% ifversion fpt or ghec %} diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md index 9c4581aca4..9550966a6d 100644 --- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md @@ -156,5 +156,5 @@ Você pode gerenciar o acesso a funcionalidades de {% data variables.product.pro - "[Protegendo o seu repositório](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %} - "[Sobre a verificação de segredo](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %} -- "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae-issue-4864 %} +- "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae %} - "[Sobre a segurança da cadeia de suprimentos](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)"{% endif %} diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index 40c99ceccc..401665144c 100644 --- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -41,7 +41,7 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing. | [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. | -| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %} | [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/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.{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %} | [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." @@ -61,8 +61,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | {% endif %} | [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion ghec %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %} -| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} +| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %} +| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization. | [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps. | [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %} | [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} @@ -75,7 +75,7 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae or ghec %} | [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% if secret-scanning-audit-log-custom-patterns %} | [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %} | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %} | [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% if custom-repository-roles %} | [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %} @@ -236,7 +236,7 @@ An overview of some of the most common actions that are recorded as events in th | `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{% ifversion fpt or ghec or ghes > 3.2 or ghae %} ### `dependabot_alerts` category actions | Action | Description @@ -497,7 +497,6 @@ For more information, see "[Managing the publication of {% data variables.produc | `delete` | Triggered when a custom pattern is removed from secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)." {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} ### `organization_label` category actions | Action | Description @@ -506,8 +505,6 @@ For more information, see "[Managing the publication of {% data variables.produc | `update` | Triggered when a default label is edited. | `destroy` | Triggered when a default label is deleted. -{% endif %} - ### `oauth_application` category actions | Action | Description @@ -572,11 +569,10 @@ For more information, see "[Managing the publication of {% data variables.produc | `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch. | `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed. | `rejected_ref_update ` | Triggered when a branch update attempt is rejected. -| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.{% ifversion fpt or ghes or ghae or ghec %} +| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator. | `update_allow_force_pushes_enforcement_level ` | Triggered when force pushes are enabled or disabled for a protected branch. | `update_allow_deletions_enforcement_level ` | Triggered when branch deletion is enabled or disabled for a protected branch. | `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch. -{% endif %} {% ifversion fpt or ghes > 3.1 or ghae or ghec %} @@ -707,7 +703,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a repository. -{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% endif %}{% ifversion fpt or ghes or ghae or ghec %} ### `repository_vulnerability_alert` category actions | Action | Description diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index 744447a481..04f9611d00 100644 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -158,25 +158,25 @@ Algumas das funcionalidades listadas abaixo estão limitadas a organizações qu Nesta seção, você pode encontrar o acesso necessário para as funcionalidades de segurança, como as funcionalidades de {% data variables.product.prodname_advanced_security %}. -| Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------------:|{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| Receber [{% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) em um repositório | | | | | **X** | -| [Ignorar {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %} +| Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------:|{% ifversion fpt or ghes or ghae or ghec %} +| Receber [{% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) em um repositório | | | | | **X** | +| [Ignorar {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | -| [Designe outras pessoas ou equipes para receber alertas de segurança](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| Criar [consultorias de segurança](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [Designe outras pessoas ou equipes para receber alertas de segurança](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} +| Criar [consultorias de segurança](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | -| Gerenciar acesso às funcionalidades de {% data variables.product.prodname_GH_advanced_security %} (ver "[Gerenciar 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)") | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} +| Gerenciar acesso às funcionalidades de {% data variables.product.prodname_GH_advanced_security %} (ver "[Gerenciar 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)") | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} | -| [Habilitar o gráfico de dependências](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) em um repositório privado | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 or ghec %} -| [Visualizar as revisões de dependências](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** +| [Habilitar o gráfico de dependências](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) em um repositório privado | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae or ghec %} +| [Visualizar as revisões de dependências](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** {% endif %} -| [Visualizar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [Lista, descarta e exclui alertas de {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | -| [Visualizar alertas de {% data variables.product.prodname_secret_scanning %} em um repositório](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} +| [Visualizar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [Lista, descarta e exclui alertas de {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | +| [Visualizar alertas de {% data variables.product.prodname_secret_scanning %} em um repositório](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} | -| [Resolver, revogar ou reabrir alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %} -| [Designar outras pessoas ou equipes para receber alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) em repositórios | | | | | **X** +| [Resolver, revogar ou reabrir alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [Designar outras pessoas ou equipes para receber alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) em repositórios | | | | | **X** {% endif %} [1] Os autores e mantenedores do repositório só podem ver informações de alertas sobre seus próprios commits. diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md index 7b91ea1c3c..e672a01b15 100644 --- a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md @@ -5,8 +5,6 @@ permissions: Organization owners can export member information for their organiz versions: fpt: '*' ghec: '*' - ghes: '>=3.3' - ghae: issue-5146 topics: - Organizations - Teams diff --git a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md index 3b1e871f05..05b79b564c 100644 --- a/translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md @@ -23,7 +23,7 @@ permissions: Organization owners can remove members from an organization. **Aviso:** Ao remover integrantes de uma organização: - O número de licenças pagas não faz o downgrade automaticamente. Para pagar menos licenças depois de remover os usuários da sua organização, siga as etapas em "[Fazer o downgrade das estações pagas da sua organização](/articles/downgrading-your-organization-s-paid-seats)". - Os integrantes removidos perderão o acesso às bifurcações privadas dos repositórios privados da sua organização, mas ainda poderão ter cópias locais. No entanto, eles não conseguem sincronizar as cópias locais com os repositórios da organização. As bifurcações privadas poderão ser restauradas se o usuário for [restabelecido como um integrante da organização](/articles/reinstating-a-former-member-of-your-organization) em até três meses após sua remoção da organização. Em última análise, você é responsável por garantir que as pessoas que perderam o acesso a um repositório excluam qualquer informação confidencial ou de propriedade intelectual. -- When private repositories are forked to other organizations, those organizations are able to control access to the fork network. This means users may retain access to the forks even after losing access to the original organization because they will still have explicit access via a fork. +- Quando os repositórios privados são bifurcados para outras organizações, essas organizações conseguem controlar o acesso à rede da bifurcação. Isso significa que os usuários podem manter o acesso às bifurcações mesmo depois de perder o acesso à organização original, porque ainda terão acesso explícito através de uma bifurgação. {%- ifversion ghec %} - Os integrantes removidos também perderão acesso a bifurcações privadas dos repositórios internos da sua organização, se o integrante removido não for integrante de qualquer outra organização pertencente à mesma conta corporativa. Para obter mais informações, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)". {%- endif %} diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md index 6d16adece9..28a7f71b12 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -26,8 +26,8 @@ shortTitle: Converter organização em usuário 2. [Altere a função do usuário para um proprietário](/articles/changing-a-person-s-role-to-owner). 3. {% data variables.product.signin_link %} para a nova conta pessoal. 4. [Transfira cada repositório da organização](/articles/how-to-transfer-a-repository) para a nova conta pessoal. -5. [Renomeie a organização](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) para tornar o nome de usuário atual disponível. -6. [Renomeie o usuário](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) para o nome da organização. +5. [Renomeie a organização](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username) para tornar o nome de usuário atual disponível. +6. [Renomeie o usuário](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username) para o nome da organização. 7. [Exclua a organização](/organizations/managing-organization-settings/deleting-an-organization-account). diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md index 8d7127b29e..39aacd1a4a 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md @@ -103,39 +103,39 @@ Você pode configurar esse comportamento para uma organização seguindo o proce {% data reusables.actions.workflow-permissions-intro %} -Você pode definir as permissões padrão para o `GITHUB_TOKEN` nas configurações para a sua organização ou repositórios. If you select a restrictive option as the default in your organization settings, the same option is selected in the settings for repositories within your organization, and the permissive option is disabled. If your organization belongs to a {% data variables.product.prodname_enterprise %} account and a more restrictive default has been selected in the enterprise settings, you won't be able to select the more permissive default in your organization settings. +Você pode definir as permissões padrão para o `GITHUB_TOKEN` nas configurações para a sua organização ou repositórios. Se você selecionar uma opção restritiva como padrão nas configurações da sua organização, a mesma opção será selecionada nas configurações dos repositórios na organização e a opção permissiva está desabilitada. Se sua organização pertence a uma conta {% data variables.product.prodname_enterprise %} e um padrão mais restritivo foi selecionado nas configurações corporativas, você não poderá selecionar o padrão mais permissivo nas configurações da sua organização. {% data reusables.actions.workflow-permissions-modifying %} ### Configurar as permissões padrão do `GITHUB_TOKEN` {% if allow-actions-to-approve-pr-with-ent-repo %} -By default, when you create a new organization, `GITHUB_TOKEN` only has read access for the `contents` scope. +Por padrão, ao criar uma nova organização, `GITHUB_TOKEN` só tem acesso de leitura para o escopo `conteúdo`. {% endif %} {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions-general %} -1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. +1. Em "Permissões do fluxo de trabalho", escolha se você quer o `GITHUB_TOKEN` para ter acesso de leitura e escrita para todos os escopos, ou apenas ler acesso para o escopo `conteúdo`. ![Definir permissões do GITHUB_TOKEN para esta organização](/assets/images/help/settings/actions-workflow-permissions-organization{% if allow-actions-to-approve-pr %}-with-pr-{% if allow-actions-to-approve-pr-with-ent-repo %}creation-{% endif %}approval{% endif %}.png) 1. Clique em **Salvar** para aplicar as configurações. {% if allow-actions-to-approve-pr %} -### Preventing {% data variables.product.prodname_actions %} from {% if allow-actions-to-approve-pr-with-ent-repo %}creating or {% endif %}approving pull requests +### Impedindo que {% data variables.product.prodname_actions %} de {% if allow-actions-to-approve-pr-with-ent-repo %}crie ou {% endif %}aprove pull requests {% data reusables.actions.workflow-pr-approval-permissions-intro %} -By default, when you create a new organization, workflows are not allowed to {% if allow-actions-to-approve-pr-with-ent-repo %}create or {% endif %}approve pull requests. +Por padrão, ao criar uma nova organização, os fluxos de trabalho não são permitidos para {% if allow-actions-to-approve-pr-with-ent-repo %}criar ou {% endif %}aprovar pull requests. {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.settings-sidebar-actions-general %} -1. Under "Workflow permissions", use the **Allow GitHub Actions to {% if allow-actions-to-approve-pr-with-ent-repo %}create and {% endif %}approve pull requests** setting to configure whether `GITHUB_TOKEN` can {% if allow-actions-to-approve-pr-with-ent-repo %}create and {% endif %}approve pull requests. +1. Em "Permissões de fluxo de trabalho", use a configuração **Permitir que o GitHub Actions crie {% if allow-actions-to-approve-pr-with-ent-repo %}e {% endif %}aprove a pull requests** para configurar se `GITHUB_TOKEN` pode {% if allow-actions-to-approve-pr-with-ent-repo %}criar e {% endif %}aprovar pull requests. - ![Set GITHUB_TOKEN pull request approval permission for this organization](/assets/images/help/settings/actions-workflow-permissions-organization{% if allow-actions-to-approve-pr %}-with-pr-{% if allow-actions-to-approve-pr-with-ent-repo %}creation-{% endif %}approval{% endif %}.png) + ![Defina a permissão da aprovação de pull request GITHUB_TOKEN para esta organização](/assets/images/help/settings/actions-workflow-permissions-organization{% if allow-actions-to-approve-pr %}-with-pr-{% if allow-actions-to-approve-pr-with-ent-repo %}creation-{% endif %}approval{% endif %}.png) 1. Clique em **Salvar** para aplicar as configurações. {% endif %} diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md index 46b4e432f2..8b7130a011 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md @@ -16,13 +16,13 @@ shortTitle: Definir política de alterações de visibilidade permissions: Organization owners can restrict repository visibility changes for an organization. --- -You can restrict who has the ability to change the visibility of repositories in your organization, such as changing a repository from private to public. For more information about repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." +É possível restringir quem tem a capacidade de alterar a visibilidade dos repositórios na organização, como a alteração de um repositório privado para público. Para obter mais informações sobre a visibilidade do repositório, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". -You can restrict the ability to change repository visibility to organization owners only, or you can allow anyone with admin access to a repository to change visibility. +Você pode restringir a capacidade de alterar a visibilidade do repositório apenas para os proprietários da organização ou você pode permitir que qualquer pessoa com acesso de administrador a um repositório altere a visibilidade. {% warning %} -**Warning**: If enabled, this setting allows people with admin access to choose any visibility for an existing repository, even if you do not allow that type of repository to be created. Para obter mais informações sobre restringir a visibilidade de repositórios existentes durante a criação, consulte "[Restringindo a criação do repositório na sua organização](/articles/restricting-repository-creation-in-your-organization)". +**Aviso**: Se habilitada, esta configuração permite que pessoas com acesso de administrador escolham qualquer visibilidade de um repositório existente, mesmo que você não permita que esse tipo de repositório seja criado. Para obter mais informações sobre restringir a visibilidade de repositórios existentes durante a criação, consulte "[Restringindo a criação do repositório na sua organização](/articles/restricting-repository-creation-in-your-organization)". {% endwarning %} diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md index 3f22fca3e5..3f3e555341 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md @@ -1,6 +1,6 @@ --- title: Configurar permissões para adicionar colaboradores externos -intro: 'To protect your organization''s data and the number of paid licenses used in your organization, you can configure who can add outside collaborators to organization repositories.' +intro: 'Para proteger os dados da sua organização e o número de licenças pagas utilizadas na sua organização, você pode configurar quem pode adicionar colaboradores externos aos repositórios da organização.' redirect_from: - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories - /articles/setting-permissions-for-adding-outside-collaborators @@ -15,7 +15,7 @@ topics: shortTitle: Definir política de colaborador --- -Por padrão, qualquer pessoa com acesso de administrador a um repositório pode convidar colaboradores externos para trabalhar no repositório. You can choose to restrict the ability to add outside collaborators to organization owners only. +Por padrão, qualquer pessoa com acesso de administrador a um repositório pode convidar colaboradores externos para trabalhar no repositório. Você pode optar por restringir a capacidade de adicionar colaboradores externos apenas para os proprietários da organização. {% ifversion ghec %} {% note %} @@ -33,5 +33,5 @@ Por padrão, qualquer pessoa com acesso de administrador a um repositório pode {% data reusables.profile.org_settings %} {% data reusables.organizations.member-privileges %}{% ifversion ghes < 3.3 %} 5. Em "Repository invitations" (Convites para o repositório), selecione **Allow members to invite outside collaborators to repositories for this organization** (Permitir que os integrantes convidem colaboradores externos aos repositórios desta organização). ![Checkbox to allow members to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-old.png){% else %} -5. Under "Repository outside collaborators", deselect **Allow repository administrators to invite outside collaborators to repositories for this organization**. ![Checkbox to allow repository administrators to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% endif %} +5. Em "Colaboradores externos do repositório, desmarque a opção **Permitir que os administradores de repositório convidem colaboradores externos para repositórios desta organização**. ![Checkbox to allow repository administrators to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% endif %} 6. Clique em **Salvar**. diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md index 6ac2e9b0ac..cabdb9c79e 100644 --- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md @@ -52,12 +52,12 @@ Você só pode escolher uma permissão adicional se já não estiver incluída n {% ifversion ghec %} ### Discussions -- **Create a discussion category**: Ability to create a new discussion category. For more information, see "[Creating a new discussion category](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#creating-a-category)". -- **Edit a discussion category**: Ability to edit a discussion category. For more information, see "[Editing a discussion category](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#editing-a-category)." -- **Delete a discussion category**: Ability to delete a discussion category. For more information, see "[Deleting a discussion category](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#deleting-a-category)." -- **Mark or unmark discussion answers**: Ability to mark answers to a discussion, if the category for the discussion accepts answers. For more information, see "[Mark or unmark comments in a discussion as the answer](/discussions/managing-discussions-for-your-community/moderating-discussions#marking-a-comment-as-an-answer)". -- **Hide or unhide discussion comments**: Ability to hide and unhide comments in a discussion. Para obter mais informações, consulte "[Moderação de discussões](/communities/moderating-comments-and-conversations/managing-disruptive-comments#hiding-a-comment)". -- **Convert issues to discussions**: Ability to convert an issue into a discussion. For more information, see "[Converting issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." +- **Criar uma categoria de discussão**: Capacidade de criar uma nova categoria de discussão. Para obter mais informações, consulte "[Criando uma nova categoria de discussão](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#creating-a-category)". +- **Editar uma categoria de discussão**: Capacidade de editar uma categoria de discussão. Para obter mais informações, consulte "[Editando uma categoria de discussão](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#editing-a-category). " +- **Excluir uma categoria de discussão**: Capacidade de excluir uma categoria de discussão. Para obter mais informações, consulte "format@@0[Excluindo uma categoria de discussão "](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#deleting-a-category)". +- **Marcar ou desmarcar as respostas da discussão**: Capacidade de marcar respostas para uma discussão, se a categoria para a discussão aceitar respostas. Para obter mais informações, consulte "[Marcar ou desmarcar comentários em uma discussão como a resposta](/discussions/managing-discussions-for-your-community/moderating-discussions#marking-a-comment-as-an-answer). +- **Ocultar ou exibir comentários de discussão**: Capacidade de ocultar e exibir comentários em uma discussão. Para obter mais informações, consulte "[Moderação de discussões](/communities/moderating-comments-and-conversations/managing-disruptive-comments#hiding-a-comment)". +- **Converter problemas em discussões**: Capacidade de converter um problema em uma discussão. Para obter mais informações, consulte "[Convertendo problemas em discussões](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion). " {% endif %} ### Problemas e Pull Requests diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md index 032285f080..af31166483 100644 --- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md @@ -32,7 +32,7 @@ Você pode adicionar até 10 pessoas ou equipes, como moderadores. Se você já {% data reusables.profile.org_settings %} {% data reusables.organizations.security-and-analysis %} 1. Na seção "Acesso" da barra lateral, selecione **Moderação de {% octicon "report" aria-label="The report icon" %}** e, em seguida, clique em **Moderadores**. -1. Em **moderadores**, pesquise e selecione a pessoa ou equipe à qual você deseja atribuir o papel de moderador. Cada pessoa ou equipe que você selecionar aparecerá na lista abaixo da barra de pesquisa. ![The Moderators search field and list](/assets/images/help/organizations/add-moderators.png) +1. Em **moderadores**, pesquise e selecione a pessoa ou equipe à qual você deseja atribuir o papel de moderador. Cada pessoa ou equipe que você selecionar aparecerá na lista abaixo da barra de pesquisa. ![O campo de pesquisa e lista dos Moderadores](/assets/images/help/organizations/add-moderators.png) ## Removendo um moderador da organização diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md index 7aaa4489b2..eea8b373f7 100644 --- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md @@ -2,8 +2,6 @@ title: Gerenciando os gerentes de segurança da sua organização intro: Você pode conceceder à sua equipe de segurança o acesso mínimo necessário à sua organização atribuindo uma equipe à função de gerente de segurança. versions: - fpt: '*' - ghes: '>=3.3' feature: security-managers topics: - Organizations @@ -30,7 +28,7 @@ Os integrantes de uma equipe com a função de gerente de segurança só têm as Funcionalidades adicionais, incluindo uma visão geral de segurança para a organização, estão disponíveis em organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %}. Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). {% endif %} -Se uma equipe tiver a função de gerente de segurança, as pessoas com acesso de administrador à equipe e um repositório específico poderão alterar o nível de acesso da equipe a esse repositório, mas não poderão remover o acesso. 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){% ifversion ghes %}."{% else %} e "[Gerenciando as equipes e pessoas com acesso ao seu repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% endif %} +Se uma equipe tiver a função de gerente de segurança, as pessoas com acesso de administrador à equipe e um repositório específico poderão alterar o nível de acesso da equipe a esse repositório, mas não poderão remover o acesso. Para obter mais informações, consulte "[Gerenciando o acesso da equipe ao repositório](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %} da organização" e "[Gerenciando equipes e pessoas com acesso ao seu repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository).{% else %}."{% endif %} ![Gerenciar a interface do usuário do repositório com gerentes de segurança](/assets/images/help/organizations/repo-access-security-managers.png) diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md index 47935b8e4c..a6cb9c9e11 100644 --- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md @@ -146,7 +146,7 @@ Algumas das funcionalidades listadas abaixo estão limitadas a organizações qu {% endif %} | Gerenciar revisões de pull request na organização (consulte "[Gerenciando revisões de pull request na sua organização](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)") | **X** | | | | | -{% elsif ghes > 3.2 or ghae-issue-4999 %} +{% elsif ghes > 3.2 or ghae %} | Ação da organização | Proprietários | Integrantes | Gerentes de segurança | diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md index c654c44644..3cf5fd068d 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md @@ -1,5 +1,5 @@ --- -title: About SCIM for organizations +title: Sobre o SCIM para organizações intro: 'Com o Sistema para gerenciamento de identidades entre domínios (SCIM, System for Cross-domain Identity Management), os administradores podem automatizar a troca de informações de identidade do usuário entre sistemas.' redirect_from: - /articles/about-scim @@ -12,30 +12,30 @@ topics: - Teams --- -## About SCIM for organizations +## Sobre o SCIM para organizações -If your organization uses [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on), you can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.product_name %}. Por exemplo, um administrador pode desprovisionar um integrante da organização usando SCIM e remover automaticamente o integrante da organização. +Se a sua organização usar o [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on), você poderá implementar o SCIM para adicionar, gerenciar e remover o acesso dos integrantes da organização a {% data variables.product.product_name %}. Por exemplo, um administrador pode desprovisionar um integrante da organização usando SCIM e remover automaticamente o integrante da organização. {% data reusables.saml.ghec-only %} {% data reusables.scim.enterprise-account-scim %} -Se o SAML SSO for usado sem implementação do SCIM, você não terá desprovisionamento automático. Quando as sessões dos integrantes da organização expiram depois que o acesso deles é removido do IdP, eles não podem ser removidos automaticamente da organização. Os tokens autorizados concedem acesso à organização mesmo depois que as respectivas sessões expiram. If SCIM is not used, to fully remove a member's access, an organization owner must remove the member's access in the IdP and manually remove the member from the organization on {% data variables.product.prodname_dotcom %}. +Se o SAML SSO for usado sem implementação do SCIM, você não terá desprovisionamento automático. Quando as sessões dos integrantes da organização expiram depois que o acesso deles é removido do IdP, eles não podem ser removidos automaticamente da organização. Os tokens autorizados concedem acesso à organização mesmo depois que as respectivas sessões expiram. Se o SCIM não for usado, para remover completamente o acesso de um integrante, o proprietário da organização deve remover o acesso do integrante no IdP e remover manualmente o integrante da organização em {% data variables.product.prodname_dotcom %}. {% data reusables.scim.changes-should-come-from-idp %} ## Provedores de identidade compatíveis -These identity providers (IdPs) are compatible with the {% data variables.product.product_name %} SCIM API for organizations. Para obter mais informações, consulte [SCIM](/rest/scim) na documentação da API {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. +Esses provedores de identidade (IdPs) são compatíveis com a API do SCIM de {% data variables.product.product_name %} para organizações. Para obter mais informações, consulte [SCIM](/rest/scim) na documentação da API {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}. - Azure AD - Okta - OneLogin -## About SCIM configuration for organizations +## Sobre a configuração do SCIM para organizações {% data reusables.scim.dedicated-configuration-account %} -Before you authorize the {% data variables.product.prodname_oauth_app %}, you must have an active SAML session. Para obter mais informações, consulte "[Sobre a autenticação com logon único SAML](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-github-apps-and-saml-sso)". +Antes de autorizar o {% data variables.product.prodname_oauth_app %}, você deve ter uma sessão do SAML ativa. Para obter mais informações, consulte "[Sobre a autenticação com logon único SAML](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-github-apps-and-saml-sso)". {% note %} diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md index 448def86f2..29957db3a3 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md @@ -18,7 +18,7 @@ Você pode controlar o acesso à sua organização em {% data variables.product. {% data reusables.saml.ghec-only %} -O SAML SSO controla e protege o acesso a recursos da organização, como repositórios, problemas e pull requests. O SCIM adiciona, gerencia e remove automaticamente o acesso dos integrantes à sua organização em {% data variables.product.product_location %} quando você fizer alterações no Okta. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" and "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." +O SAML SSO controla e protege o acesso a recursos da organização, como repositórios, problemas e pull requests. O SCIM adiciona, gerencia e remove automaticamente o acesso dos integrantes à sua organização em {% data variables.product.product_location %} quando você fizer alterações no Okta. Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso com o logon único SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" e "[Sobre o SCIM para as organizações](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)". Após ativar o SCIM, os seguintes recursos de provisionamento estarão disponíveis para qualquer usuário ao qual você atribuir seu aplicativo do {% data variables.product.prodname_ghe_cloud %} no Okta. @@ -41,15 +41,15 @@ Como alternativa, você pode configurar o SAML SSO para uma empresa usando o Okt {% data reusables.scim.dedicated-configuration-account %} -1. Sign into {% data variables.product.prodname_dotcom_the_website %} using an account that is an organization owner and is ideally used only for SCIM configuration. -1. To create an active SAML session for your organization, navigate to `https://github.com/orgs/ORGANIZATION-NAME/sso`. Para obter mais informações, consulte "[Sobre a autenticação com logon único SAML](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-github-apps-and-saml-sso)". -1. Navigate to Okta. +1. Faça o login em {% data variables.product.prodname_dotcom_the_website %} usando uma conta que é o proprietário da organização e é idealmente usada apenas para a configuração do SCIM. +1. Para criar uma sessão ativa SAML para sua organização, acesse `https://github.com/orgs/ORGANIZATION-NAME/sso`. Para obter mais informações, consulte "[Sobre a autenticação com logon único SAML](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-github-apps-and-saml-sso)". +1. Acesse o Okta. {% data reusables.saml.okta-dashboard-click-applications %} {% data reusables.saml.okta-applications-click-ghec-application-label %} {% data reusables.saml.okta-provisioning-tab %} {% data reusables.saml.okta-configure-api-integration %} {% data reusables.saml.okta-enable-api-integration %} -1. Click **Authenticate with {% data variables.product.prodname_ghe_cloud %} - Organization**. +1. Clique em **Efetuar a autenticação com {% data variables.product.prodname_ghe_cloud %} - Organização**. 1. À direita do nome da sua organização, clique em **Conceder**. ![Botão "Conceder" para autorizar a integração do SCIM do Okta para acessar a organização](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png) diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md index eaa73c7046..74375b12b4 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md @@ -1,6 +1,6 @@ --- title: Conectar o provedor de identidade à organização -intro: 'To use SAML single sign-on and SCIM, you must connect your identity provider (IdP) to your organization on {% data variables.product.product_name %}.' +intro: 'Para usar o logon único SAML e o SCIM, você deve conectar seu provedor de identidade (IdP) à sua organização em {% data variables.product.product_name %}.' redirect_from: - /articles/connecting-your-identity-provider-to-your-organization - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization @@ -13,7 +13,7 @@ topics: shortTitle: Conectar um IdP --- -## About connection of your IdP to your organization +## Sobre a conexão do seu IdP à sua organização Ao habilitar o SAML SSO para sua organização de {% data variables.product.product_name %}, você conecta seu provedor de identidade (IdP) à sua organização. Para obter mais informações, consulte "[Habilitar e testar logon único de SAML para sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)". @@ -29,7 +29,7 @@ Você pode encontrar as informações de implementação do SAML e SCIM para seu {% note %} -**Observação:** os provedores de identidade aceitos pelo {% data variables.product.product_name %} para SCIM são Azure AD, Okta e OneLogin. For more information about SCIM, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)." +**Observação:** os provedores de identidade aceitos pelo {% data variables.product.product_name %} para SCIM são Azure AD, Okta e OneLogin. Para obter mais informações sobre o SCIM, consulte "[Sobre o SCIM para as organizações](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)". {% data reusables.scim.enterprise-account-scim %} @@ -37,4 +37,4 @@ Você pode encontrar as informações de implementação do SAML e SCIM para seu ## Metadados SAML -For more information about SAML metadata for your organization, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference)." +Para obter mais informações sobre metadados do SAML para a sua organização, consulte "[Referência de configuração do SAML](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference)". diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md index 4bcdd09191..3a579f3a76 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md @@ -14,7 +14,7 @@ shortTitle: Aplicar logon único SAML ## Sobre a aplicação do SAML SSO para sua organização -When you enable SAML SSO, {% data variables.product.prodname_dotcom %} will prompt members who visit the organization's resources on {% data variables.product.prodname_dotcom_the_website %} to authenticate on your IdP, which links the member's personal account to an identity on the IdP. Os integrantes ainda podem acessar os recursos da organização antes da autenticação com seu IdP. +Ao habilitar o SAML SSO, {% data variables.product.prodname_dotcom %} solicitará que os integrantes que visitam os recursos da organização em {% data variables.product.prodname_dotcom_the_website %} efetuem a autenticação no seu IdP, que vincula a conta pessoal do integrante a uma identidade no IdP. Os integrantes ainda podem acessar os recursos da organização antes da autenticação com seu IdP. ![Banner com solicitação para efetuar a autenticação por meio do SAML SSO para acessar a organização](/assets/images/help/saml/sso-has-been-enabled.png) diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md index 052dc5b6af..a48986bd53 100644 --- a/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md @@ -37,7 +37,7 @@ You can also use LDAP Sync to synchronize {% data variables.product.product_loca {% data reusables.organizations.types-of-team-visibility %} -You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)." +You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)." ## Team pages diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md index 2a1f319b5b..7f2947696d 100644 --- a/translations/pt-BR/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md @@ -31,11 +31,10 @@ As pessoas com o papel de mantenedor da equipe podem gerenciar as configuraçõe - [Excluir discussões de equipe](/articles/managing-disruptive-comments/#deleting-a-comment) - [Adicionar integrantes da organização à equipe](/articles/adding-organization-members-to-a-team) - [Remover membros da organização da equipe](/articles/removing-organization-members-from-a-team) -- Remover acesso da equipe aos repositórios{% ifversion fpt or ghes or ghae or ghec %} -- [Gerenciar atribuição de código para a equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% ifversion fpt or ghec %} +- Remove the team's access to repositories +- [Gerenciar atribuição de código para a equipe](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% ifversion fpt or ghec %} - [Gerenciar lembretes agendados para pull requests](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %} - ## Promover um integrante de organização a mantenedor de equipe Antes de poder promover um integrante da organização para chefe de uma equipe, a pessoa deverá ser integrante da equipe. diff --git a/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md index d785171ea8..91e4b91111 100644 --- a/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md +++ b/translations/pt-BR/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md @@ -46,7 +46,7 @@ Para gerenciar o acesso ao repositório de qualquer equipe do {% data variables. Após conectar uma equipe a um grupo de IdP, a sincronização da equipe adicionará cada integrante do grupo IdP à equipe correspondente em {% data variables.product.product_name %} apenas se: - A pessoa for integrante da organização em {% data variables.product.product_name %}. -- The person has already logged in with their personal account on {% data variables.product.product_name %} and authenticated to the organization or enterprise account via SAML single sign-on at least once. +- A pessoa já efetuou o login com sua conta pessoal em {% data variables.product.product_name %} e efetuou a autenticação na conta corporativa ou corporativa via logon único SAML pelo menos uma vez. - A identidade SSO da pessoa é um integrante do grupo IdP. As equipes ou integrantes de grupo que não atenderem a esses critérios serão automaticamente removidos da equipe em {% data variables.product.product_name %} e perderão o acesso aos repositórios. Revogar a identidade vinculada a um usuário também removerá o usuário de quaisquer equipes mapeadas com os grupos de IdP. Para obter mais informações, consulte "[Visualizando e gerenciando o acesso do SAML de um membro da sua organização](/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)" e "[Visualizando e gerenciando o acesso do SAML de um usuário da sua organização](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity)." diff --git a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/index.md b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/index.md index c83dd8d0b5..cbdb5672cd 100644 --- a/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/index.md +++ b/translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/index.md @@ -1,6 +1,6 @@ --- title: Restringir o acesso aos dados da organização -intro: 'As restrições de acesso ao {% data variables.product.prodname_oauth_app %} permitem que os proprietários da organização restrinjam o acesso de um app não confiável aos dados da organização. Organization members can then use {% data variables.product.prodname_oauth_apps %} for their personal accounts while keeping organization data safe.' +intro: 'As restrições de acesso ao {% data variables.product.prodname_oauth_app %} permitem que os proprietários da organização restrinjam o acesso de um app não confiável aos dados da organização. Os integrantes da organização podem usar {% data variables.product.prodname_oauth_apps %} para suas contas pessoais mantendo os dados da organização seguros.' redirect_from: - /articles/restricting-access-to-your-organization-s-data - /articles/restricting-access-to-your-organizations-data diff --git a/translations/pt-BR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/translations/pt-BR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md index 1abb3ca184..a57e59e2e5 100644 --- a/translations/pt-BR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md +++ b/translations/pt-BR/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md @@ -33,14 +33,14 @@ Ao conectar um repositório a um pacote, a página inicial do pacote mostrará i {% data reusables.package_registry.container-registry-ghes-beta %} {% endif %} -1. In your Dockerfile, add this line, replacing {% ifversion ghes %}`HOSTNAME`, {% endif %}`OWNER` and `REPO` with your details: +1. No arquivo Docker, adicione essa linha, substituindo {% ifversion ghes %}`HOSTNAME`, {% endif %}`OWNER` e `REPO` pelos seus detalhes: ```shell - LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPO + ETIQUETA org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPO ``` - For example, if you're the user `monalisa` and own `my-repo`, and {% data variables.product.product_location %} hostname is `github.companyname.com`, you would add this line to your Dockerfile: + Por exemplo, se você é o usuário de `monalisa` e tem `my-repo` e o nome de host {% data variables.product.product_location %} é `github. ompanyname.com`, você adicionaria esta linha ao seu arquivo Docker: ```shell - LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}{% data reusables.package_registry.container-registry-example-hostname %}{% endif %}/monalisa/my-repo + ETIQUETA org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}{% data reusables.package_registry.container-registry-example-hostname %}{% endif %}/monalisa/my-repo ``` Para obter mais informações, consulte "[ETIQUETA](https://docs.docker.com/engine/reference/builder/#label)" na documentação oficial do Docker e "[Chaves de anotação pré-definidas](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" no repositório `opencontainers/image-spec`. diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md index bd5ab483f3..08bcfdc4a6 100644 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md +++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md @@ -1,6 +1,6 @@ --- title: Trabalhando com o registro do Contêiner -intro: 'You can store and manage Docker and OCI images in the {% data variables.product.prodname_container_registry %}, which uses the package namespace `https://{% data reusables.package_registry.container-registry-hostname %}`.' +intro: 'Você pode armazenar e gerenciar imagens do Docker e OCI no {% data variables.product.prodname_container_registry %}, que usa o namespace do pacote ''https://{% data reusables.package_registry.container-registry-hostname %}''.' product: '{% data reusables.gated-features.packages %}' redirect_from: - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images @@ -22,7 +22,7 @@ shortTitle: Container registry {% ifversion ghes > 3.4 %} {% note %} -**Note**: {% data variables.product.prodname_container_registry %} is currently in beta for {% data variables.product.product_name %} and subject to change. +**Observação**: {% data variables.product.prodname_container_registry %} está atualmente em beta para {% data variables.product.product_name %} e sujeito a alterações. {% endnote %} {% endif %} @@ -30,7 +30,7 @@ shortTitle: Container registry {% ifversion ghes > 3.4 %} ## Pré-requisitos -To configure and use the {% data variables.product.prodname_container_registry %} on {% data variables.product.prodname_ghe_server %}, your site administrator must first enable {% data variables.product.prodname_registry %} **and** subdomain isolation. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" and "[Enabling subdomain isolation](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)." +Para configurar e usar o {% data variables.product.prodname_container_registry %} em {% data variables.product.prodname_ghe_server %}, primeiro seu administrador do site deve habilitar {% data variables.product.prodname_registry %} **e** o isolamento de subdomínio. Para obter mais informações, consulte "[Primeiros passos com o GitHub Packages para sua empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" e "[Habilitando o isolamento do subdomínio](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)". {% endif %} ## Sobre o suporte de {% data variables.product.prodname_container_registry %} @@ -45,7 +45,7 @@ Ao instalar ou publicar uma imagem Docker, a {% data variables.product.prodname_ {% data reusables.package_registry.authenticate_with_pat_for_container_registry %} -{% ifversion ghes %}Ensure that you replace `HOSTNAME` with {% data variables.product.product_location_enterprise %} hostname or IP address in the examples below.{% endif %} +{% ifversion ghes %}Certifique-se de substituir o `HOSTNAME` pelo nome do host {% data variables.product.product_location_enterprise %} ou endereço IP nos exemplos abaixo.{% endif %} {% data reusables.package_registry.authenticate-to-container-registry-steps %} diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md index 93cee104b0..7270bda756 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -82,13 +82,13 @@ Se você desejar manter os arquivos de origem do seu site em outro local, você Se você escolher a pasta `/docs` de qualquer branch como a fonte de publicação, o {% data variables.product.prodname_pages %} lerá tudo a ser publicado no seu site{% ifversion fpt or ghec %}, inclusive o arquivo _CNAME_,{% endif %} na pasta `/docs`.{% ifversion fpt or ghec %} Por exemplo, quando você edita o domínio personalizado usando as configurações do {% data variables.product.prodname_pages %}, o domínio personalizado grava em `/docs/CNAME`. Para obter mais informações sobre arquivos _CNAME_, consulte "[Gerenciar um domínio personalizado para seu site do {% data variables.product.prodname_pages %}](/articles/managing-a-custom-domain-for-your-github-pages-site)".{% endif %} {% ifversion ghec %} -## Limitations for {% data variables.product.prodname_emus %} -If you're a {% data variables.product.prodname_managed_user %}, your use of {% data variables.product.prodname_pages %} is limited. +## Limitações para {% data variables.product.prodname_emus %} +Se você é um {% data variables.product.prodname_managed_user %}, seu uso de {% data variables.product.prodname_pages %} é limitado. - - {% data variables.product.prodname_pages %} sites can only be published from repositories owned by organizations. - - {% data variables.product.prodname_pages %} sites are only visible to other members of the enterprise. + - Os sites de {% data variables.product.prodname_pages %} só podem ser publicados de repositórios pertencentes a organizações. + - Os sites de {% data variables.product.prodname_pages %} só são visíveis para os outros integrantes da empresa. -For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)." +Para obter mais informações sobre {% data variables.product.prodname_emus %}, consulte "[Sobre {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)". {% endif %} ## Geradores de site estáticos diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index 509c2cdd8e..0398cc977e 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -15,7 +15,7 @@ Com controle de acesso para {% data variables.product.prodname_pages %}, você p {% data reusables.pages.privately-publish-ghec-only %} -If your enterprise uses {% data variables.product.prodname_emus %}, access control is not available, and all {% data variables.product.prodname_pages %} sites are only accessible to other enterprise members. Para obter mais informações sobre {% data variables.product.prodname_emus %}, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)." +Se a sua empresa usa {% data variables.product.prodname_emus %}, o controle de acesso não está disponível, e todos os sites de {% data variables.product.prodname_pages %} estão acessíveis somente para os integrantes da empresa. Para obter mais informações sobre {% data variables.product.prodname_emus %}, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)." Se a sua organização usar {% data variables.product.prodname_ghe_cloud %} sem {% data variables.product.prodname_emus %}, você poderá optar por publicar seus sites em particular ou publicamente para qualquer pessoa na internet. O controle de acesso está disponível para os sites de projeto publicados a partir de um repositório privado ou interno que pertencem à organização. Você não pode gerenciar o controle de acesso para um site da organização. Para obter mais informações sobre os tipos de sites do {% data variables.product.prodname_pages %}, consulte "[Sobre {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)". diff --git a/translations/pt-BR/content/pages/index.md b/translations/pt-BR/content/pages/index.md index e86305bfd9..daf96fb0a7 100644 --- a/translations/pt-BR/content/pages/index.md +++ b/translations/pt-BR/content/pages/index.md @@ -1,7 +1,34 @@ --- title: Documentação do GitHub Pages shortTitle: GitHub Pages -intro: 'Você pode criar um site diretamente de um repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.' +intro: 'Learn how to create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Explore website building tools like Jekyll and troubleshoot issues with your {% data variables.product.prodname_pages %} site.' +introLinks: + quickstart: /pages/quickstart + overview: /pages/getting-started-with-github-pages/about-github-pages +featuredLinks: + guides: + - /pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site + - /pages/getting-started-with-github-pages/creating-a-github-pages-site + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll{% endif %}' + - '{% ifversion ghec %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site{% endif %}' + - '{% ifversion fpt %}/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll{% endif %}' + popular: + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages{% endif %}' + - /pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll) + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages{% endif %}' + - '{% ifversion fpt or ghec %}/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https{% endif %}' + - '{% ifversion ghes or ghae %}/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll{% endif %}' + guideCards: + - /pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site + - /pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll + - /pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites +changelog: + label: pages +layout: product-landing redirect_from: - /categories/20/articles - /categories/95/articles diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md index 581819013f..774066d6fe 100644 --- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -49,7 +49,7 @@ Pessoas com permissões de gravação para um repositório podem adicionar um te --- --- - @import "{{ site.theme }}"; + @import "{% raw %}{{ site.theme }}{% endraw %}"; ``` 3. Adicione o CSS ou Sass personalizado (incluindo importações) que deseja imediatamente após a linha `@import`. diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md index 18695dd0df..d04cb47436 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md @@ -24,13 +24,17 @@ topics: ### Mesclar mensagem para uma mesclagem por squash -Quando você faz combinação por squash e merge, o {% data variables.product.prodname_dotcom %} gera uma mensagem de commit que você pode mudar se quiser. O padrão da mensagem depende se a pull request contém vários commits ou apenas um. Nós não incluímos commits de merge quando contamos o número total de commits. +When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. The default message depends on the number of commits in the pull request, not including merge commits. | Número de commits | Sumário | Descrição | | ----------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | | Um commit | O título da mensagem de commit do único commit, seguido do número de pull request | O texto da mensagem de commit para o único commit | | Mais de um commit | Título da pull request, seguido do número da pull request | Uma lista das mensagens de commit para todos os commits combinados por squash, por ordem de data | +{% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %} +People with admin access to a repository can configure the repository to use the title of the pull request as the default merge message for all squashed commits. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)". +{% endif %} + ### Fazendo combinação por squash e merge com um branch de longa duração Se você planeja continuar trabalhando no [branch head](/github/getting-started-with-github/github-glossary#head-branch) de uma pull request depois que a pull request for mesclada, recomendamos que você não combine por squash nem faça o merge da pull request. diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md index 1e7559a93c..207bf31c82 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md @@ -1,12 +1,12 @@ --- -title: Merging a pull request with a merge queue -intro: 'If a merge queue is required by the branch protection setting for the branch, you can add your pull requests to a merge queue and {% data variables.product.product_name %} will merge the pull requests for you once all required checks have passed.' +title: Fazendo merge de um pull request com uma fila de merge +intro: 'Se uma fila de merge for exigida pela configuração de proteção de branch para o branch, você pode adicionar seus pull requests a uma fila de merge e {% data variables.product.product_name %} fará o merge dos pull requests para você assim que todas as verificações necessárias tiverem passado.' versions: fpt: '*' ghec: '*' topics: - Pull requests -shortTitle: Merge PR with merge queue +shortTitle: Fazer merge do PR com fila de merge redirect_from: - /pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue @@ -14,55 +14,55 @@ redirect_from: {% data reusables.pull_requests.merge-queue-beta %} -## About merge queues +## Sobre filas de merge {% data reusables.pull_requests.merge-queue-overview %} {% data reusables.pull_requests.merge-queue-references %} -## Adding a pull request to a merge queue +## Adicionando um pull request a uma fila de merge {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} -1. In the "Pull Requests" list, click the pull request you would like to add to a merge queue. +1. Na lista "Pull Requests", clique no pull request que você gostaria de adicionar a uma fila de merge. -1. Click **Merge when ready** to add the pull request to the merge queue. Alternatively, if you are an administrator, you can: - - Directly merge the pull request by checking **Merge without waiting for requirements to be met (administrators only)**, if allowed by branch protection settings, and follow the standard flow. ![Opções da fila de merge](/assets/images/help/pull_requests/merge-queue-options.png) +1. Clique em **Fazer merge quando estiver pronto** para adicionar o pull request à fila de merge. Como alternativa, se você for um administrador, você pode: + - Faça o merge diretamente do pull request verificando **Merge sem aguardar que os requisitos sejam cumpridos (somente administradores)**, se permitido pelas configurações de proteção de branches e siga o fluxo padrão. ![Opções da fila de merge](/assets/images/help/pull_requests/merge-queue-options.png) {% tip %} - **Tip:** You can click **Merge when ready** whenever you're ready to merge your proposed changes. {% data variables.product.product_name %} will automatically add the pull request to the merge queue once required approval and status checks conditions are met. + **Dica:** você pode clicar em **Fazer merge quando estiver pronto** sempre que estiver pronto para fazer merge das alterações propostas. {% data variables.product.product_name %} irá adicionar automaticamente o pull request à fila de merge assim que forem atendidas as condições de aprovação e verificação de status. {% endtip %} -1. Confirm you want to add the pull request to the merge queue by clicking **Confirm merge when ready**. +1. Confirme que você deseja adicionar o pull request à fila de merge clicando em **Confirmar o merge quando estiver pronto**. -## Removing a pull request from a merge queue +## Removendo um pull request de uma fila de merge {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} -1. In the "Pull Requests" list, click the pull request you would like to remove from a merge queue. +1. Na lista "Pull Requests", clique no pull request que você gostaria de remover de uma fila de merge. -1. To remove the pull request from the queue, click **Remove from queue**. ![Remove pull request from queue](/assets/images/help/pull_requests/remove-from-queue-button.png) +1. Para remover o pull request da fila, clique em **Remover da fila**. ![Remova o pull request da fila](/assets/images/help/pull_requests/remove-from-queue-button.png) -Alternatively, you can navigate to the merge queue page for the base branch, click **...** next to the pull request you want to remove, and select **Remove from queue**. For information on how to get to the merge queue page for the base branch, see the section below. +Como alternativa, você pode acessar a página da fila de merge para o branch base, clique em **...** ao lado do pull request que você deseja remover e selecione **Remover da fila**. Para obter informações sobre como obter na página da fila de merge para o branch base, consulte a seção abaixo. -## Viewing merge queues +## Visualizando filas de merge -You can view the merge queue for a base branch in various places on {% data variables.product.product_name %}. +Você pode visualizar a fila de merge para um branch base em vários lugares em {% data variables.product.product_name %}. -- Na página **Branches** para o repositório. We recommend you use this route if you don't have or don't know about a pull request already in a queue, and if you want to see what's in that queue. Para obter mais informações, consulte "[Visualizar branches no seu repositório](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository)". +- Na página **Branches** para o repositório. Recomendamos que você use encaminhamento se você não tiver ou não conhecer um pull request já na fila e se você quiser ver o que está nessa fila. Para obter mais informações, consulte "[Visualizar branches no seu repositório](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository)". ![Visualizar fila de merge na página de Branches](/assets/images/help/pull_requests/merge-queue-branches-page.png) -- On the **Pull requests** page of your repository, click {% octicon "clock" aria-label="The clock symbol" %} next to any pull request in the merge queue. +- Na página de **Pull requests** do seu repositório, clique em {% octicon "clock" aria-label="The clock symbol" %} ao lado de qualquer pull request na fila de merge. ![Visualizar fila de merge na página de Pull requests](/assets/images/help/pull_requests/clock-icon-in-pull-request-list.png) -- On the pull request page when merge queue is required for merging, scroll to the bottom of the timeline and click the **merge queue** link. +- Na página do pull request, quando a fila do merge é necessária para o merge, role para a parte inferior da linha do tempo e clique no link **fila de merge**. - ![Merge queue link on pull request](/assets/images/help/pull_requests/merge-queue-link.png) + ![Link da fila de merge no pull request](/assets/images/help/pull_requests/merge-queue-link.png) - A exibição da fila de merge mostra os pull requests que estão atualmente na fila, com seus pull requests claramente marcados. diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md index 42bc5ecdce..04b085e175 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md @@ -54,15 +54,15 @@ Para simplificar a revisão das alterações em um pull request extenso, é poss ## Comparações de diff do Git de três pontos e dois pontos -There are two comparison methods for the `git diff` command; two-dot (`git diff A..B`) and three-dot (`git diff A...B`). By default, pull requests on {% data variables.product.prodname_dotcom %} show a three-dot diff. +Existem dois métodos de comparação para o comando `git diff`; dois pontos (`git diff A..B`) e três pontos (`git diff A...B`). Por padrão, os pull requests em {% data variables.product.prodname_dotcom %} mostram um diff de três pontos. -### Three-dot Git diff comparison +### Comparação do diff de três pontos do Git -The three-dot comparison shows the difference between the latest common commit of both branches (merge base) and the most recent version of the topic branch. +A comparação de três pontos mostra a diferença entre o último commit comum de ambos os branches (merge base) e a versão mais recente do branch do tópico. -### Two-dot Git diff comparison +### Comparação do diff de dois pontos Git -The two-dot comparison shows the difference between the latest state of the base branch (for example, `main`) and the most recent version of the topic branch. +A comparação de dois pontos mostra a diferença entre o estado mais recente do branch de base (por exemplo, `principal`) e a versão mais recente do branch de tópico. Para ver duas referências de committish em uma comparação de diff de dois pontos no {% data variables.product.prodname_dotcom %}, você pode editar o URL da página "Comparing changes" (Comparar alterações) do seu repositório. Para obter mais informações, consulte [Glossário do Git para "committish"](https://git-scm.com/docs/gitglossary#gitglossary-aiddefcommit-ishacommit-ishalsocommittish) no book site do _Pro Git_. @@ -74,17 +74,17 @@ Se desejar simular um diff de dois pontos em uma pull request e ver uma compara Para obter mais informações sobre os comandos do Git para comparar alterações, consulte "[Opções de diff do Git](https://git-scm.com/docs/git-diff#git-diff-emgitdiffemltoptionsgtltcommitgtltcommitgt--ltpathgt82308203)" no site do livro do _Pro Git_. -## About three-dot comparison on {% data variables.product.prodname_dotcom %} +## Sobre a comparação de três pontos em {% data variables.product.prodname_dotcom %} -Since the three-dot comparison compares with the merge base, it is focusing on "what a pull request introduces". +Como a comparação de três pontos é comparada com a base de merge, ela está focada no "que um pull request apresenta". -When you use a two-dot comparison, the diff changes when the base branch is updated, even if you haven't made any changes to the topic branch. Additionally, a two-dot comparison focuses on the base branch. This means that anything you add is displayed as missing from the base branch, as if it was a deletion, and vice versa. As a result, the changes the topic branch introduces become ambiguous. +Ao usar uma comparação de dois pontos, o diff muda quando o branch base é atualizado, mesmo que não tenha feito nenhuma alteração no branch de tópico. Além disso, uma comparação de dois pontos foca no branch de base. Isso significa que qualquer coisa que você adicionar será exibida como ausente no branch base, como se fosse uma exclusão e vice-versa. Como resultado, as alterações que o branch do tópico introduz tornam-se ambíguas. -In contrast, by comparing the branches using the three-dot comparison, changes in the topic branch are always in the diff if the base branch is updated, because the diff shows all of the changes since the branches diverged. +Em contraste, comparando os branches usando a comparação de três pontos, as alterações no branch de tópico estão sempre no diff se o branch base for atualizado, porque o diff mostra todas as alterações desde que os branches dibergiram. -### Merging often +### Fazendo o merge frequentemente -To avoid getting confused, merge the base branch (for example, `main`) into your topic branch frequently. By merging the base branch, the diffs shown by two-dot and three-dot comparisons are the same. We recommend merging a pull request as soon as possible. This encourages contributors to make pull requests smaller, which is recommended in general. +Para evitar confusão, faça o merge do branch de base (por exemplo, `principal`) no seu branch de tópico com frequência. Ao fazer o merge do branch de base, os diffs mostrados pelas comparações de dois pontos e três pontos são iguais. Recomendamos o merge de um pull request assim que possível. Isso incentiva os contribuidores a diminuir o número de pull requests, o que é recomendado de forma geral. ## Leia mais diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md index c7ed30e9c2..b911a029d8 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md @@ -1,6 +1,6 @@ --- title: Alterar o stage de uma pull request -intro: 'Você pode marcar uma pull request de rascunho como pronta para revisão{% ifversion fpt or ghae or ghes or ghec %} ou converter uma pull request para rascunho{% endif %}.' +intro: You can mark a draft pull request as ready for review or convert a pull request to a draft. permissions: People with write permissions to a repository and pull request authors can change the stage of a pull request. product: '{% data reusables.gated-features.draft-prs %}' redirect_from: @@ -22,20 +22,16 @@ shortTitle: Alterar o estado {% data reusables.pull_requests.mark-ready-review %} -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Dicas**: Você também pode marcar um pull request como pronto para revisão usando {% data variables.product.prodname_cli %}. Para obter mais informações, consulte "[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)na documentação de {% data variables.product.prodname_cli %}. {% endtip %} -{% endif %} {% data reusables.repositories.sidebar-pr %} 2. Na lista "Pull requests", clique na pull request que deseja marcar como pronta para revisão. 3. Na caixa de merge, clique em **Pronto para revisar**. ![Botão Ready for review (Pronta para revisão)](/assets/images/help/pull_requests/ready-for-review-button.png) -{% ifversion fpt or ghae or ghes or ghec %} - ## Convertendo uma pull request em rascunho Você pode converter uma pull request em rascunho a qualquer momento. Por exemplo, se você abriu uma pull request acidentalmente em vez de um rascunho, ou se você recebeu feedback sobre sua pull request que precisa ser resolvida, você pode converter a pull request em um rascunho para indicar outras mudanças necessárias. Ninguém poderá fazer o merge da pull request até que você marque a pull request como pronta para revisão novamente. Pessoas que já estão inscritas em notificações para a pull request não serão descadastradas quando você converter a pull request em um rascunho. @@ -45,8 +41,6 @@ Você pode converter uma pull request em rascunho a qualquer momento. Por exempl 3. Na barra lateral direita, em "Revisores", clique em **Converter para rascunho**. ![Converter para link de rascunho](/assets/images/help/pull_requests/convert-to-draft-link.png) 4. Clique em **Converter para rascunho**. ![Converter para confirmação de rascunho](/assets/images/help/pull_requests/convert-to-draft-dialog.png) -{% endif %} - ## Leia mais - "[Sobre pull requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)" diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md index 3b7dd5e499..0354838fe3 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -39,9 +39,9 @@ Se o branch que você deseja excluir estiver associado a um pull request aberto, {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} 1. Role até o branch que deseja excluir e clique em {% octicon "trash" aria-label="The trash icon to delete the branch" %}. ![delete the branch](/assets/images/help/branches/branches-delete.png) {% ifversion fpt or ghes > 3.5 or ghae-issue-6763 or ghec %} -1. If you try to delete a branch that is associated with at least one open pull request, you must confirm that you intend to close the pull request(s). +1. Se você tentar excluir um branch associado a pelo menos um pull request aberto, você deverá confirmar que pretende fechar o(s) pull request(s). - ![Confirm deleting a branch](/assets/images/help/branches/confirm-deleting-branch.png){% endif %} + ![Confirme a exclusão de um branch](/assets/images/help/branches/confirm-deleting-branch.png){% endif %} {% data reusables.pull_requests.retargeted-on-branch-deletion %} Para obter mais informações, consulte "[Sobre branches](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)". diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md index f40e97b670..105a52725b 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md @@ -17,11 +17,11 @@ topics: shortTitle: Solicitar revisão de PR --- -Repositories belong to a personal account (a single individual owner) or an organization account (a shared account with numerous collaborators or maintainers). Para obter mais informações, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)". Owners and collaborators on a repository owned by a personal account can assign pull request reviews. Organization members with triage permissions can also assign a reviewer for a pull request. +Os repositórios pertencem a uma conta pessoal (um único proprietário) ou a uma conta da organização (uma conta compartilhada com inúmeros colaboradores ou mantenedores). Para obter mais informações, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)". Proprietários e colaboradores de um repositório pertencente a uma conta pessoal podem atribuir revisões de pull requests. Os integrantes da organização com permissões de triagem também podem atribuir um revisor a um pull request. -To assign a reviewer to a pull request, you will need write access to the repository. For more information about repository access, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." If you have write access, you can assign anyone who has read access to the repository as a reviewer. +Para atribuir um revisor a um pull request, você precisará de acesso de gravação ao repositório. Para obter mais informações sobre o acesso do repositório, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)". Se você tiver acesso de gravação, você pode atribuir a qualquer pessoa que tenha acesso de leitura ao repositório como revisor. -Organization members with write access can also assign a pull request review to any person or team with read access to a repository. O revisor ou a equipe receberão uma notificação informando que você solicitou a revisão de uma pull request. {% ifversion fpt or ghae or ghes or ghec %}Se você solicitar uma revisão de uma equipe e a atribuição de revisão de código estiver ativada, integrantes específicos serão solicitados e a equipe será removida como revisora. Para obter mais informações, consulte "[Gerenciando configurações de revisão de código para sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)".{% endif %} +Os integrantes da organização com acesso de gravação também podem atribuir um comentário de pull request a qualquer pessoa ou equipe com acesso de leitura a um repositório. O revisor ou a equipe receberão uma notificação informando que você solicitou a revisão de uma pull request. If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. Para obter mais informações, consulte "[Gerenciando as configurações de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." {% note %} diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md index 541484ca62..ae7434e7b7 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md @@ -22,7 +22,7 @@ Após a abertura de uma pull request, qualquer pessoa com acesso *de leitura* po {% if pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %} -Os proprietários de repositório e colaboradores podem solicitar uma revisão de pull request de uma pessoa específica. Os integrantes da organização também podem solicitar uma revisão de pull request de uma equipe com acesso de leitura ao repositório. Para obter mais informações, consulte "[Solicitar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)". {% ifversion fpt or ghae or ghes or ghec %}Você pode especificar um subconjunto de integrantes da equipe que será automaticamente responsável no lugar de toda a equipe. Para obter mais informações, consulte "[Gerenciando configurações de revisão de código para sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)".{% endif %} +Os proprietários de repositório e colaboradores podem solicitar uma revisão de pull request de uma pessoa específica. Os integrantes da organização também podem solicitar uma revisão de pull request de uma equipe com acesso de leitura ao repositório. Para obter mais informações, consulte "[Solicitar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)". You can specify a subset of team members to be automatically assigned in the place of the whole team. Para obter mais informações, consulte "[Gerenciando as configurações de revisão de código para a sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." As revisões permitem discussão das alterações propostas e ajudam a garantir que as alterações atendam às diretrizes de contribuição do repositório e outros padrões de qualidade. Você pode definir quais indivíduos ou equipes possuem determinados tipos de área de código em um arquivo CODEOWNERS. Quando uma pull request modifica código que tem um proprietário definido, esse indivíduo ou equipe será automaticamente solicitado como um revisor. Para obter mais informações, consulte "[Sobre proprietários de código](/articles/about-code-owners/)". diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 7bb4ae86ca..17a8629a13 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -5,7 +5,7 @@ product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -36,7 +36,7 @@ shortTitle: Revisar alterações de dependência Revisão de dependência permite a você "desloque para a esquerda". Você pode usar as informações preditivas fornecidas para capturar dependências vulneráveis antes que elas cheguem à produção. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)". {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-6396 %} -You can use the Dependency Review GitHub Action to help enforce dependency reviews on pull requests in your repository. For more information, see "[Dependency review enforcement](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)." +Você pode usar a Revisão de Dependência do GitHub Action para ajudar a implementar revisões de dependências em pull requests no seu repositório. Para obter mais informações, consulte "[Aplicação da revisão de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)". {% endif %} ## Revisar as dependências em um pull request diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md index c68a1c395a..3af28596ea 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md @@ -1,6 +1,6 @@ --- title: Permitir alterações em um branch de pull request criado a partir de bifurcação -intro: 'For greater collaboration, you can allow commits on branches you''ve created from forks owned by your personal account.' +intro: 'Para obter mais colaboração, você pode permitir commits nos branches que criou a partir de bifurcações de propriedade de sua conta pessoal.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork - /articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md index f55d55c4fa..b4e2f954c3 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md @@ -67,7 +67,7 @@ Se um repositório privado passa a ser público e depois é excluído, as bifurc -Se a política para a sua empresa permitir a bifurcação, qualquer bifurcação de um repositório interno será privado. If you change the visibility of an internal repository, any fork owned by an organization or personal account will remain private. +Se a política para a sua empresa permitir a bifurcação, qualquer bifurcação de um repositório interno será privado. Se você alterar a visibilidade de um repositório interno, qualquer bifurcação pertencente a uma organização ou conta pessoal continuará sendo privada. ### Excluir o repositório interno diff --git a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md index 1f6a5ddf4c..7429d93c11 100644 --- a/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md +++ b/translations/pt-BR/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md @@ -31,9 +31,9 @@ Veja a seguir um exemplo de uma [comparação entre dois branches](https://githu ## Comparar tags -A comparação de tags de versão irá mostrar alterações no seu repositório desde a última versão. {% ifversion fpt or ghae or ghes or ghec %} Para obter mais informações, consulte "[Comparar versões](/github/administering-a-repository/comparing-releases)."{% endif %} +A comparação de tags de versão irá mostrar alterações no seu repositório desde a última versão. For more information, see "[Comparing releases](/github/administering-a-repository/comparing-releases)." -{% ifversion fpt or ghae or ghes or ghec %}Para comparar tags, você pode selecionar um nome de tag no menu suspenso `compare` na parte superior da página.{% else %} Em vez de digitar um nome do branch, digite o nome da sua tag no menu suspenso `compare`.{% endif %} +To compare tags, you can select a tag name from the `compare` drop-down menu at the top of the page. Veja a seguir o exemplo de uma [comparação entre duas tags](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3). diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md index 4496ae097d..6456da8e65 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md @@ -27,8 +27,7 @@ shortTitle: Sobre métodos de merge {% data reusables.pull_requests.default_merge_option %} -{% ifversion fpt or ghae or ghes or ghec %} -O método de merge padrão cria um commit de mesclagem. Você pode impedir que uma pessoa faça pushing com commits por merge em um branch protegido aplicando um histórico de commit linear. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-linear-history)."{% endif %} +O método de merge padrão cria um commit de mesclagem. Você pode impedir que uma pessoa faça pushing com commits por merge em um branch protegido aplicando um histórico de commit linear. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches#require-linear-history)." ## Combinar por squash os commits de merge diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md index fca55fb795..96825e6005 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md @@ -22,10 +22,10 @@ shortTitle: Configurar combinação por squash de commit {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 3. Em {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Botão de merge"{% endif %}, opcionalmente, selecione **Permitir commits de merge**. Isso permite que os contribuidores façam merge de uma pull request com um histórico completo de commits. ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png) -4. Em {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Botão de merge"{% endif %}, selecione **Permitir merge de combinação por squash**. Isso permite que os contribuidores façam merge de uma pull request combinando por squash todos os commits em um único commit. The squash message automatically defaults to the title of the pull request if it contains more than one commit. {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %}If you want to use the title of the pull request as the default merge message for all squashed commits, regardless of the number of commits in the pull request, select **Default to PR title for squash merge commits**. ![Pull request squashed commits](/assets/images/help/repository/pr-merge-squash.png){% else %} +4. Em {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Botão de merge"{% endif %}, selecione **Permitir merge de combinação por squash**. Isso permite que os contribuidores façam merge de uma pull request combinando por squash todos os commits em um único commit. A mensagem da combinação por squash automaticamente é o título do pull request se ela contiver mais de um commit. {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %}Se você quiser usar o título do pull request como a mensagem de mesclagem padrão para todos os commits combinados por squash, independentemente do número de commits no pull request, selecione **Definir como padrão o título de PR para commits de merge de combinação por squash**. ![Pull request squashed commits](/assets/images/help/repository/pr-merge-squash.png){% else %} ![Pull request squashed commits](/assets/images/enterprise/3.5/repository/pr-merge-squash.png){% endif %} -If you select more than one merge method, collaborators can choose which type of merge commit to use when they merge a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} +Se você selecionar mais de um método de merge, os colaboradores poderão escolher qual o tipo de commit de merge usar ao fazer o merge de um pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ## Leia mais diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md index bf6e706c48..ec347f260e 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md @@ -1,6 +1,6 @@ --- -title: Managing a merge queue -intro: You can increase development velocity with a merge queue for pull requests in your repository. +title: Gerenciando uma fila de merge +intro: É possível aumentar a velocidade do desenvolvimento com uma fila de merge para pull requests no repositório. versions: fpt: '*' ghec: '*' @@ -8,22 +8,22 @@ permissions: People with admin permissions can manage merge queues for pull requ topics: - Repositories - Pull requests -shortTitle: Managing merge queue +shortTitle: Gerenciando fila de merge redirect_from: - /repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue --- {% data reusables.pull_requests.merge-queue-beta %} -## About merge queues +## Sobre filas de merge {% data reusables.pull_requests.merge-queue-overview %} -The merge queue creates temporary branches with a special prefix to validate pull request changes. The changes in the pull request are then grouped with the latest version of the `base_branch` as well as changes ahead of it in the queue. {% data variables.product.product_name %} will merge all these changes into `base_branch` once the checks required by the branch protections of `base_branch` pass. +A fila de merge cria branches temporários com um prefixo especial para validar as alterações do pull request. As alterações no pull request são agrupadas com a versão mais recente do `base_branch` e também com as alterações na fila. {% data variables.product.product_name %} fará merge de todas essas alterações em `base_branch` uma vez que as verificações exigidas pelas proteções do branch de `base_branch` sejam aprovadas. -You may need to update your Continuous Integration (CI) configuration to trigger builds on branch names that begin with the special prefix `gh-readonly-queue/{base_branch}` after the group is created. +Talvez você precise atualizar a sua configuração de Integração Contínua (CI) para acionar compilações em nomes de branches que começam com o prefixo especial `gh-readonly /{base_branch}` depois que o grupo é criado. -For example, with {% data variables.product.prodname_actions %}, a workflow with the following trigger will run each time a pull request that targets the base branch `main` is queued to merge. +Por exemplo, com {% data variables.product.prodname_actions %}, um fluxo de trabalho com o gatilho a seguir será executado cada vez que um pull request que visa ao branch base `main` for enfileirada para fazer merge. ```yaml on: @@ -40,19 +40,19 @@ Para obter informações sobre métodos de merge, consulte "[Sobre merges de pul **Observação:** -* A merge queue cannot be enabled with branch protection rules that use wildcard characters (`*`) in the branch name pattern. +* Uma fila de merge não pode ser habilitada com regras de proteção do branch que usam caracteres coringa (`*`) no padrão do nome do branch. {% endnote %} {% data reusables.pull_requests.merge-queue-reject %} -## Managing a merge queue +## Gerenciando uma fila de merge -Repository administrators can require a merge by enabling the branch protection setting "Require merge queue" in the protection rules for the base branch. +Os administradores de repositório podem exigir um merge que permite a proteção do branch que configura "Exigir file de merge" nas regras de proteção para o branch base. Para obter informações sobre como habilitar a configuração de proteção de fila de merge, consulte "[Gerenciando uma regra de proteção de branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule). " ## Leia mais -* "[Merging a pull request with a merge queue](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue)" +* "[Fazendo o merge de um pull request com uma fila de merge](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue)" * "[Sobre branches protegidos](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)" diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md index 33afdf8535..f8e3e1b807 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md @@ -150,7 +150,7 @@ Antes de exigir um histórico de commit linear, seu repositório deve permitir m ### Require deployments to succeed before merging -You can require that changes are successfully deployed to specific environments before a branch can be merged. For example, you can use this rule to ensure that changes are successfully deployed to a staging environment before the changes merge to your default branch. +Você pode exigir que as alterações sejam implantadas em ambientes específicos antes de ua branch poder ser mesclado. Por exemplo, você pode usar essa regra para garantir que as alterações sejam implantadas com sucesso em um ambiente de teste antes das alterações sofrerem merge no seu branch padrão. ### Incluir administradores @@ -162,13 +162,13 @@ Por padrão, as regras de branch protegidos não se aplicam a pessoas com permis Você pode habilitar as restrições do branch se seu repositório for propriedade de uma organização que usa {% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %}. {% endif %} -Ao habilitar as restrições de branches, apenas usuários, equipes ou aplicativos com permissão podem fazer push para o branch protegido. Você pode visualizar e editar usuários, equipes ou aplicativos com acesso de push a um branch protegido nas configurações do branch protegido. When status checks are required, the people, teams, and apps that have permission to push to a protected branch will still be prevented from merging into the branch when the required checks fail. As pessoas, equipes, e aplicativos que têm permissão para fazer push em um branch protegido ainda precisarão criar um pull request quando forem necessários pull requests. +Ao habilitar as restrições de branches, apenas usuários, equipes ou aplicativos com permissão podem fazer push para o branch protegido. Você pode visualizar e editar usuários, equipes ou aplicativos com acesso de push a um branch protegido nas configurações do branch protegido. Quando as verificações de status são necessárias, as pessoas, as equipes e os aplicativos que têm permissão para fazer push em um branch protegido ainda serão impedidos de realizar merge no branch quando a verificação necessária falhar. As pessoas, equipes, e aplicativos que têm permissão para fazer push em um branch protegido ainda precisarão criar um pull request quando forem necessários pull requests. {% if restrict-pushes-create-branch %} -Optionally, you can apply the same restrictions to the creation of branches that match the rule. For example, if you create a rule that only allows a certain team to push to any branches that contain the word `release`, only members of that team would be able to create a new branch that contains the word `release`. +Opcionalmente, você pode aplicar as mesmas restrições à criação de branches que correspondam à regra. Por exemplo, se você criar uma regra que só permite a uma determinada equipe fazer push para quaisquer branches que contenham a palavra `versão`, somente os integrantes dessa equipe poderiam criar um novo branch que contém a palavra `versão`. {% endif %} -You can only give push access to a protected branch, or give permission to create a matching branch, to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch or create a matching branch. +Você só pode dar acesso push a um branch protegido ou dar permissão para criar um branch correspondente para usuários, equipes ou instalar {% data variables.product.prodname_github_apps %} com acesso de gravação a um repositório. As pessoas e aplicativos com permissões de administrador em um repositório são sempre capazes de fazer push em um branch protegido ou criar um branch correspondente. ### Permitir push forçado @@ -186,7 +186,7 @@ Por padrão, os blocks do {% data variables.product.product_name %} fazem push f Habilitar push forçado não irá substituir quaisquer outras regras de proteção de branch. Por exemplo, se um branch exigir um histórico de commit linear, você não poderá forçar commits a mesclar commits para esse branch. -{% ifversion ghes or ghae %}Você não pode habilitar pushes forçados para um branch protegido se um administrador do site bloquear push forçados para todos os branches do seu repositório. For more information, see "[Blocking force pushes to repositories owned by a personal account or organization](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." +{% ifversion ghes or ghae %}Você não pode habilitar pushes forçados para um branch protegido se um administrador do site bloquear push forçados para todos os branches do seu repositório. Para obter mais informações, consulte "[Bloqueando push forçado para repositórios de propriedade de uma conta pessoal ou de organização](/enterprise/{{ currentVersion }}/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)." Se um administrador do site bloquear pushes forçados apenas para o branch padrão, você ainda pode habilitar pushes forçados para qualquer outro branch protegido.{% endif %} diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md index fd5b1610a3..9e64f711fc 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md @@ -63,9 +63,9 @@ Ao criar uma regra de branch, o branch que você especificar ainda não existe n - Opcionalmente, para ignorar uma revisão de aprovação de pull request quando um commit de modificação de código for enviado por push para o branch, selecione **Ignorar aprovações obsoletas de pull request quando novos commits forem enviados por push**. ![Caixa de seleção Dismiss stale pull request approvals when new commits are pushed (Ignorar aprovações de pull requests obsoletas ao fazer push de novos commits)](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) - Opcionalmente, para exigir a revisão de um proprietário do código quando o pull request afeta o código que tem um proprietário designado, selecione **Exigir revisão de Proprietários do Código**. Para obter mais informações, consulte "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)". ![Require review from code owners (Exigir revisão de proprietários de código)](/assets/images/help/repository/PR-review-required-code-owner.png) {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5611 %} - - Opcionalmente, para permitir que pessoas ou equipes específicas enviem código por push para o branch sem criar pull requests quando necessário, selecione **permitir que atores específicos ignorem pull requests**. Em seguida, pesquise e selecione as pessoas ou equipes que devem ter permissão para pular a criação de um pull request. ![Permitir que os atores específicos ignorem a caixa de seleção de requisitos de pull request](/assets/images/help/repository/PR-bypass-requirements.png) + - Optionally, to allow specific actors to push code to the branch without creating pull requests when they're required, select **Allow specified actors to bypass required pull requests**. Then, search for and select the actors who should be allowed to skip creating a pull request. ![Allow specific actors to bypass pull request requirements checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-bypass-requirements-with-apps.png){% else %}(/assets/images/help/repository/PR-bypass-requirements.png){% endif %} {% endif %} - - Opcionalmente, se o repositório fizer parte de uma organização, selecione **Restringir quem pode ignorar as revisões de pull request**. Em seguida, procure e selecione as pessoas ou equipes que têm permissão para ignorar as revisões de pull request. Para obter mais informações, consulte "[Ignorar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". ![Caixa de seleção Restrict who can dismiss pull request reviews (Restringir quem pode ignorar revisões de pull request)](/assets/images/help/repository/PR-review-required-dismissals.png) + - Opcionalmente, se o repositório fizer parte de uma organização, selecione **Restringir quem pode ignorar as revisões de pull request**. Then, search for and select the actors who are allowed to dismiss pull request reviews. Para obter mais informações, consulte "[Ignorar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". ![Restrict who can dismiss pull request reviews checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-review-required-dismissals-with-apps.png){% else %}(/assets/images/help/repository/PR-review-required-dismissals.png){% endif %} 1. Opcionalmente, habilite as verificações de status obrigatórias. Para obter mais informações, consulte "[Sobre verificações de status](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)". - Selecione **Require status checks to pass before merging** (Exigir verificações de status para aprovação antes de fazer merge). ![Opção Required status checks (Verificações de status obrigatórias)](/assets/images/help/repository/required-status-checks.png) - Opcionalmente, para garantir que os pull requests sejam testados com o código mais recente no branch protegido, selecione **Exigir que os branches estejam atualizados antes do merge**. ![Caixa de seleção Status obrigatório rígido ou flexível](/assets/images/help/repository/protecting-branch-loose-status.png) @@ -84,18 +84,18 @@ Ao criar uma regra de branch, o branch que você especificar ainda não existe n {% endtip %} {%- endif %} {%- if required-deployments %} -1. Optionally, to choose which environments the changes must be successfully deployed to before merging, select **Require deployments to succeed before merging**, then select the environments. ![Require successful deployment option](/assets/images/help/repository/require-successful-deployment.png) +1. Opcionalmente, para escolher em quais ambientes as alterações devem ser implantadas com sucesso antes de fazer merge, selecione **Exigir implantações para ser bem-sucedidas antes do merge** e, em seguida, selecione os ambientes. ![Exigir uma opção de implantação bem-sucedida](/assets/images/help/repository/require-successful-deployment.png) {%- endif %} 1. Opcionalmente, selecione **Aplicar as regras acima aos administradores**. ![Aplicar as regras acima à caixa de seleção dos administradores](/assets/images/help/repository/include-admins-protected-branches.png) 1. Opcionalmente, {% ifversion fpt or ghec %} se o repositório pertencer a uma organização que usa {% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %},{% endif %} habilitar as restrições de branches. - Selecione **Restringir quem pode fazer push para os branches correspondentes**. ![Branch restriction checkbox](/assets/images/help/repository/restrict-branch.png){% if restrict-pushes-create-branch %} - - Optionally, to also restrict the creation of matching branches, select **Restrict pushes that create matching branches**. ![Branch creation restriction checkbox](/assets/images/help/repository/restrict-branch-create.png){% endif %} - - Search for and select the people, teams, or apps who will have permission to push to the protected branch or create a matching branch. ![Branch restriction search]{% if restrict-pushes-create-branch %}(/assets/images/help/repository/restrict-branch-search-with-create.png){% else %}(/assets/images/help/repository/restrict-branch-search.png){% endif %} + - Opcionalmente, para também restringir a criação de branches correspondentes, selecione **Restringir pushes que criam branches correspondentes**. ![Branch creation restriction checkbox](/assets/images/help/repository/restrict-branch-create.png){% endif %} + - Pesquise e selecione pessoas, equipes ou apps que tenham permissão para fazer push para o branch protegido ou crie um branch correspondente. ![Branch restriction search]{% if restrict-pushes-create-branch %}(/assets/images/help/repository/restrict-branch-search-with-create.png){% else %}(/assets/images/help/repository/restrict-branch-search.png){% endif %} 1. Opcionalmente, em "Regras aplicadas a todos incluindo administradores", selecione **Permitir pushes forçados**. ![Permitir opção push forçado](/assets/images/help/repository/allow-force-pushes.png) {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5624 %} Em seguida, escolha quem pode fazer push forçado no branch. - Selecione **Todos** para permitir que todos com pelo menos permissões de escrita no repositório para forçar push para o branch, incluindo aqueles com permissões de administrador. - - Selecione **Especificar quem pode fazer push forçado** para permitir que apenas pessoas ou equipes específicas possam fazer push forçado no branch. Em seguida, procure e selecione essas pessoas ou equipes. ![Captura de tela das opções para especificar quem pode fazer push forçado](/assets/images/help/repository/allow-force-pushes-specify-who.png) + - Select **Specify who can force push** to allow only specific actors to force push to the branch. Then, search for and select those actors. ![Screenshot of the options to specify who can force push]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png){% else %}(/assets/images/help/repository/allow-force-pushes-specify-who.png){% endif %} {% endif %} Para obter mais informações sobre push forçado, consulte "[Permitir pushes forçados](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)". diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md index 7b0705903b..6dbb646bb9 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md @@ -37,28 +37,25 @@ remote: error: Required status check "ci-build" is failing {% endnote %} -{% ifversion fpt or ghae or ghes or ghec %} - ## Conflitos entre o título do commit e o commit de merge do teste Por vezes, os resultados das verificações de status para o commit de mescla teste e o commit principal entrarão em conflito. Se o commit de merge de testes tem status, o commit de merge de testes deve passar. Caso contrário, o status do commit principal deve passar antes de você poder mesclar o branch. Para obter mais informações sobre commits de merge de teste, consulte "[Pulls](/rest/reference/pulls#get-a-pull-request)". ![Branch com commits de mescla conflitantes](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) -{% endif %} ## Manipulação ignorada, mas verificações necessárias {% note %} -**Note:** If a workflow is skipped due to [path filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), [branch filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) or a [commit message](/actions/managing-workflow-runs/skipping-workflow-runs), then checks associated with that workflow will remain in a "Pending" state. A pull request that requires those checks to be successful will be blocked from merging. +**Observação:** Se um fluxo de trabalho for ignorado devido à [filtragem do caminho](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), a [filtragem do caminho](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) ou [mensagem de commit](/actions/managing-workflow-runs/skipping-workflow-runs) as verificações associadas a esse fluxo de trabalho permanecerão em um estado "Pendente". Um pull request que requer que essas verificações sejam bem sucedidas será bloqueado do merge. -If a job in a workflow is skipped due to a conditional, it will report its status as "Success". For more information see [Skipping workflow runs](/actions/managing-workflow-runs/skipping-workflow-runs) and [Using conditions to control job execution](/actions/using-jobs/using-conditions-to-control-job-execution). +Se um trabalho em um fluxo de trabalho for ignorado devido a uma condicional, ele informará seu status como "Sucesso". Para obter mais informações, consulte [Ignorando as execuções do fluxo de trabalho](/actions/managing-workflow-runs/skipping-workflow-runs) e [Usando condições para controlar a execução do trabalho](/actions/using-jobs/using-conditions-to-control-job-execution). {% endnote %} ### Exemplo -The following example shows a workflow that requires a "Successful" completion status for the `build` job, but the workflow will be skipped if the pull request does not change any files in the `scripts` directory. +O exemplo a seguir mostra um fluxo de trabalho que exige um status de conclusão de "Sucesso" para o trabalho de `criação`, mas o fluxo de trabalho será ignorado se o pull request não alterar quaisquer arquivos no diretório de `scripts`. ```yaml name: ci @@ -84,7 +81,7 @@ jobs: - run: npm test ``` -Due to [path filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), a pull request that only changes a file in the root of the repository will not trigger this workflow and is blocked from merging. Você verá o seguinte status no pull request: +Devido à [filtragem do caminho](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), um pull request que apenas altera um arquivo na raiz do repositório não acionará esse fluxo de trabalho e está bloqueada de fazer merge. Você verá o seguinte status no pull request: ![Verificação obrigatória ignorada mas mostrada como pendente](/assets/images/help/repository/PR-required-check-skipped.png) diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md index 5f9f8560c9..b1594861d4 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/about-repositories.md @@ -26,10 +26,10 @@ Você pode possuir repositórios individualmente ou compartilhar a propriedade d É possível restringir quem tem acesso a um repositório escolhendo a visibilidade do repositório. Para obter mais informações, consulte "[Sobre a visibilidade do repositório](#about-repository-visibility)." -Para repositórios possuídos pelo usuário, você pode fornecer a outras pessoas acesso de colaborador para que elas possam colaborar no seu projeto. Se um repositório pertencer a uma organização, você poderá fornecer aos integrantes da organização permissões de acesso para colaboração no seu repositório. For more information, see "[Permission levels for a personal account repository](/articles/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)." +Para repositórios possuídos pelo usuário, você pode fornecer a outras pessoas acesso de colaborador para que elas possam colaborar no seu projeto. Se um repositório pertencer a uma organização, você poderá fornecer aos integrantes da organização permissões de acesso para colaboração no seu repositório. Para obter mais informações, consulte "[Níveis de permissão para uma repositório de conta pessoal](/articles/permission-levels-for-a-user-account-repository/)" e "[Funções de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)". {% ifversion fpt or ghec %} -With {% data variables.product.prodname_free_team %} for personal accounts and organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set. Para obter ferramentas avançadas para repositórios privados, você pode fazer o upgrade para {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %} +Com o {% data variables.product.prodname_free_team %} em contas pessoais e de organizações, você pode trabalhar com colaboradores ilimitados em repositórios públicos ilimitados, com um conjunto completo de recursos, ou em repositórios privados ilimitados com um conjunto de recursos limitados. Para obter ferramentas avançadas para repositórios privados, você pode fazer o upgrade para {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} ou {% data variables.product.prodname_ghe_cloud %}. {% data reusables.gated-features.more-info %} {% else %} Cada pessoa e organização podem ter repositórios ilimitados e convidar um número ilimitado de colaboradores para todos os repositórios. {% endif %} diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md index e0fe145e5b..b0ef04b6f8 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md @@ -26,17 +26,15 @@ topics: {% endtip %} -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Dica**: Você também pode criar um repositório usando o {% data variables.product.prodname_cli %}. Para obter mais informações, consulte "[`criar repositório gh`](https://cli.github.com/manual/gh_repo_create)" na documentação do {% data variables.product.prodname_cli %}. {% endtip %} -{% endif %} {% data reusables.repositories.create_new %} -2. Se desejar, para criar um repositório com a estrutura de diretório e arquivos de um repositório existente, use o menu suspenso **Choose a template** (Escolher um modelo) e selecione um repositório de modelo. Você verá repositórios de modelo que pertencem a você e às organizações das quais você é integrante ou que usou antes. Para obter mais informações, consulte "[Criar um repositório a partir de um modelo](/articles/creating-a-repository-from-a-template)". ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %} -3. Opcionalmente, se você escolheu usar um modelo para incluir a estrutura do diretório e arquivos de todos os branches no modelo, e não apenas o branch-padrão, selecione **Incluir todos os branches**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} +2. Se desejar, para criar um repositório com a estrutura de diretório e arquivos de um repositório existente, use o menu suspenso **Choose a template** (Escolher um modelo) e selecione um repositório de modelo. Você verá repositórios de modelo que pertencem a você e às organizações das quais você é integrante ou que usou antes. Para obter mais informações, consulte "[Criar um repositório a partir de um modelo](/articles/creating-a-repository-from-a-template)". ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png) +3. Opcionalmente, se você escolheu usar um modelo para incluir a estrutura do diretório e arquivos de todos os branches no modelo, e não apenas o branch-padrão, selecione **Incluir todos os branches**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png) 3. No menu suspenso Proprietário, selecione a conta na qual deseja criar o repositório.![Menu suspenso Owner (Proprietário)](/assets/images/help/repository/create-repository-owner.png) {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %} diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md index b642c9320e..0c69bea52e 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md @@ -19,17 +19,13 @@ shortTitle: Criar a partir de um modelo Qualquer pessoa com permissões de leitura em um repositório de modelos pode criar um repositório a partir desse modelo. Para obter mais informações, consulte "[Criar um repositório de modelos](/articles/creating-a-template-repository)". -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Dica**: Você também pode criar um repositório a partir de um modelo usando o {% data variables.product.prodname_cli %}. Para obter mais informações, consulte "[`criar repositório gh`](https://cli.github.com/manual/gh_repo_create)" na documentação do {% data variables.product.prodname_cli %}. {% endtip %} -{% endif %} -{% ifversion fpt or ghae or ghes or ghec %} Você pode optar por incluir a estrutura do diretório e os arquivos apenas a partir do branch-padrão do repositório de modelos ou incluir todos os branches. Os branches criados a partir de um modelo têm histórico não relacionado, o que significa que você não pode criar pull requests ou fazer merge entre os branches. -{% endif %} Criar um repositório a partir de um modelo é semelhante a bifurcar um repositório, mas há diferenças importantes: - Uma nova bifurcação inclui o histórico de commits inteiro do repositório principal, enquanto um repositório criado de um modelo começa com um único commit. @@ -44,7 +40,7 @@ Para obter mais informações sobre bifurcações, consulte "[Sobre bifurcaçõe 2. Acima da lista de arquivos, clique em **Use this template** (Usar este modelo). ![Botão Use this template (Usar este modelo)](/assets/images/help/repository/use-this-template-button.png) {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} -{% data reusables.repositories.choose-repo-visibility %}{% ifversion fpt or ghae or ghes or ghec %} -6. Opcionalmente, para incluir a estrutura de diretório e arquivos de todos os branches no modelo, e não apenas o branch-padrão, selecione **Incluir todos os branches**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} +{% data reusables.repositories.choose-repo-visibility %} +6. Opcionalmente, para incluir a estrutura de diretório e arquivos de todos os branches no modelo, e não apenas o branch-padrão, selecione **Incluir todos os branches**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png) {% data reusables.repositories.select-marketplace-apps %} 8. Clique em **Create repository from template** (Criar repositório a partir do modelo). diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md index ac172d9ed9..30de098bf0 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md @@ -1,6 +1,6 @@ --- title: Criar um repositório de modelos -intro: 'Você pode converter um repositório existente em um modelo, para que você e outras pessoas possam gerar novos repositórios com a mesma estrutura de diretório{% ifversion fpt or ghae or ghes or ghec %}, branches,{% endif %} e arquivos.' +intro: 'You can make an existing repository a template, so you and others can generate new repositories with the same directory structure, branches, and files.' permissions: Anyone with admin permissions to a repository can make the repository a template. redirect_from: - /articles/creating-a-template-repository @@ -24,7 +24,7 @@ shortTitle: Criar um repositório de modelo Para criar um repositório de modelos, é preciso criar um repositório e, em seguida, torná-lo um modelo. Para obter mais informações sobre como criar um repositório, consulte "[Criar um repositório](/articles/creating-a-new-repository)". -Depois de fazer o seu repositório um modelo, qualquer pessoa com acesso ao repositório poderá gerar um novo repositório com a mesma estrutura de diretório e arquivos do branch padrão.{% ifversion fpt or ghae or ghes or ghec %} Eles também podem optar por incluir todos os outros branches no seu repositório. Os branches criados a partir de um modelo têm histórico não relacionado. Portanto, você não pode criar pull requests ou fazer merge entre os branches.{% endif %} Para obter mais informações, consulte "[Criar um repositório a partir de um modelo](/articles/creating-a-repository-from-a-template)". +After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch. They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches. Para obter mais informações, consulte "[Criar um repositório a partir de um modelo](/articles/creating-a-repository-from-a-template)". {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/renaming-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/renaming-a-repository.md index 4a943a546b..bb5a7ab252 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/renaming-a-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/renaming-a-repository.md @@ -39,7 +39,7 @@ Se você planeja renomear um repositório que tenha um site do {% data variables {% note %} -**Note:** {% data variables.product.prodname_dotcom %} will not redirect calls to an action hosted by a renamed repository. Any workflow that uses that action will fail with the error `repository not found`. Instead, create a new repository and action with the new name and archive the old repository. Para obter mais informações, consulte "[Arquivando repositórios](/repositories/archiving-a-github-repository/archiving-repositories)". +**Observação:** {% data variables.product.prodname_dotcom %} não irá redirecionar chamadas para uma ação hospedada por um repositório renomeado. Qualquer fluxo de trabalho que usar essa ação falhará com o erro `repositório não encontrado`. Instead, create a new repository and action with the new name and archive the old repository. Para obter mais informações, consulte "[Arquivando repositórios](/repositories/archiving-a-github-repository/archiving-repositories)". {% endnote %} diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md index f0299574ca..7a25fd34fd 100644 --- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md +++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md @@ -16,11 +16,11 @@ shortTitle: Restaurar repositório excluído --- {% ifversion fpt or ghec %} -Anyone can restore deleted repositories that were owned by their own personal account. Os proprietários da organização podem restaurar repositórios excluídos que pertenciam à organização. +Qualquer pessoa pode restaurar repositórios excluídos que pertenciam à própria conta pessoal. Os proprietários da organização podem restaurar repositórios excluídos que pertenciam à organização. ## Sobre a restauração do repositório -A deleted repository can be restored within {% ifversion fpt or ghec or ghes > 3.4 %}30{% else %}90{% endif %} days, unless the repository was part of a fork network that is not currently empty. Uma rede de bifurcação consiste em um repositório principal, nas bifurcações do repositório e nas bifurcações das bifurcações do repositório. Se o repositório fazia parte de uma rede de bifurcação, ele não poderá ser restaurado, a menos que todos os outros repositórios na rede sejam excluídos ou tenham sido desanexados da rede. Para obter mais informações sobre bifurcações, consulte "[Sobre bifurcações](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)". +Um repositório excluído pode ser restaurado em {% ifversion fpt or ghec or ghes > 3.4 %}30{% else %}90{% endif %} dias, a menos que o repositório faça parte de uma rede de bifurcação que atualmente não está vazia. Uma rede de bifurcação consiste em um repositório principal, nas bifurcações do repositório e nas bifurcações das bifurcações do repositório. Se o repositório fazia parte de uma rede de bifurcação, ele não poderá ser restaurado, a menos que todos os outros repositórios na rede sejam excluídos ou tenham sido desanexados da rede. Para obter mais informações sobre bifurcações, consulte "[Sobre bifurcações](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)". Se desejar restaurar um repositório que fazia parte de uma rede de bifurcação que atualmente não está vazia, contate o {% data variables.contact.contact_support %}. @@ -28,7 +28,7 @@ Depois que um repositório é excluído, pode levar até uma hora para que ele s Restaurar um repositório não vai restaurar anexos de versão nem permissões de equipe. Os problemas que são restaurados não serão etiquetados. -## Restoring a deleted repository that was owned by a personal account +## Restaurar um repositório excluído que pertencia a uma conta pessoal {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.repo-tab %} diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index 1ca0f47a1a..f5853b408e 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -119,14 +119,14 @@ By default, when you create a new repository in your personal account, `GITHUB_T {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions-general %} -1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope. +1. Em "Permissões do fluxo de trabalho", escolha se você quer o `GITHUB_TOKEN` para ter acesso de leitura e escrita para todos os escopos, ou apenas ler acesso para o escopo `conteúdo`. ![Definir permissões do GITHUB_TOKEN para este repositório](/assets/images/help/settings/actions-workflow-permissions-repository{% if allow-actions-to-approve-pr-with-ent-repo %}-with-pr-approval{% endif %}.png) 1. Clique em **Salvar** para aplicar as configurações. {% if allow-actions-to-approve-pr-with-ent-repo %} -### Preventing {% data variables.product.prodname_actions %} from creating or approving pull requests +### Impedindo {% data variables.product.prodname_actions %} de criar ou aprovar pull requests {% data reusables.actions.workflow-pr-approval-permissions-intro %} @@ -135,7 +135,7 @@ By default, when you create a new repository in your personal account, workflows {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions-general %} -1. Under "Workflow permissions", use the **Allow GitHub Actions to create and approve pull requests** setting to configure whether `GITHUB_TOKEN` can create and approve pull requests. +1. Em "Fluxos de trabalho", use a configuração **Permitir que o GitHub Actions crie e aprove pull requests** para configurar se `GITHUB_TOKEN` pode criar e aprovar pull requests. ![Definir permissões do GITHUB_TOKEN para este repositório](/assets/images/help/settings/actions-workflow-permissions-repository-with-pr-approval.png) 1. Clique em **Salvar** para aplicar as configurações. diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md index 67c8fece20..661877cff8 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md @@ -1,6 +1,6 @@ --- -title: About email notifications for pushes to your repository -intro: You can choose to automatically send email notifications to a specific email address when anyone pushes to the repository. +title: Sobre notificações de e-mail para pushes no seu repositório +intro: Você pode optar por enviar notificações por email automaticamente para um endereço de email específico quando alguém fizer push para o repositório. permissions: People with admin permissions in a repository can enable email notifications for pushes to your repository. redirect_from: - /articles/managing-notifications-for-pushes-to-a-repository @@ -16,39 +16,32 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Email notifications for pushes +shortTitle: Notificações de e-mail para pushes --- + {% data reusables.notifications.outbound_email_tip %} -Each email notification for a push to a repository lists the new commits and links to a diff containing just those commits. In the email notification you'll see: +Cada notificação de e-mail para um push no repositório lista os novos commits e os vincula a um diff contendo apenas esses commits. Na notificação de e-mail, você verá: -- The name of the repository where the commit was made -- The branch a commit was made in -- The SHA1 of the commit, including a link to the diff in {% data variables.product.product_name %} -- The author of the commit -- The date when the commit was made -- The files that were changed as part of the commit -- The commit message +- O nome do repositório onde o commit foi feito +- O branch em que um commit foi feito +- O SHA1 do commit, incluindo um link para o diff no {% data variables.product.product_name %} +- O autor do commit +- A data em que o commit foi feito +- Os arquivos que foram alterados como parte do commit +- A mensagem do commit; -You can filter email notifications you receive for pushes to a repository. For more information, see {% ifversion fpt or ghae or ghes or ghec %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}"[About notification emails](/github/receiving-notifications-about-activity-on-github/about-email-notifications)." You can also turn off email notifications for pushes. For more information, see "[Choosing the delivery method for your notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}." +É possível filtrar notificações de e-mail que você recebe para pushes em um repositório. Para obter mais informações, consulte “[Configurando notificações](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)". -## Enabling email notifications for pushes to your repository +## Habilitando notificações de e-mail para pushes no seu repositório {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.sidebar-notifications %} -5. Type up to two email addresses, separated by whitespace, where you'd like notifications to be sent. If you'd like to send emails to more than two accounts, set one of the email addresses to a group email address. -![Email address textbox](/assets/images/help/settings/email_services_addresses.png) -1. If you operate your own server, you can verify the integrity of emails via the **Approved header**. The **Approved header** is a token or secret that you type in this field, and that is sent with the email. If the `Approved` header of an email matches the token, you can trust that the email is from {% data variables.product.product_name %}. -![Email approved header textbox](/assets/images/help/settings/email_services_approved_header.png) -7. Click **Setup notifications**. -![Setup notifications button](/assets/images/help/settings/setup_notifications_settings.png) +5. Digite até dois endereços de e-mail, separados por um espaço, para os quais deseja enviar as notificações. Se desejar enviar e-mails a mais de duas contas, defina um dos endereços para um endereço de e-mail de grupo. ![Caixa de texto de endereço de e-mail](/assets/images/help/settings/email_services_addresses.png) +1. Se você operar o seu próprio servidor, você poderá verificar a integridade dos e-mails através do **Cabeçalho aprovado**. O **Cabeçalho aprovado** é um token ou segredo que você digita nesse campo e enviado com o e-mail. Se o cabeçalho `Aprovado` de um e-mail corresponder ao token, você poderá confiar que o e-mail é de {% data variables.product.product_name %}. ![Caixa de texto do cabeçalho do e-mail aprovado](/assets/images/help/settings/email_services_approved_header.png) +7. Clique em **Configurar notificações**. ![Botão para configurar notificações](/assets/images/help/settings/setup_notifications_settings.png) + +## Leia mais +- "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" -## Further reading -{% ifversion fpt or ghae or ghes or ghec %} -- "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" -{% else %} -- "[About notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" -- "[Choosing the delivery method for your notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)" -- "[About email notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" -- "[About web notifications](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)"{% endif %} diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md index d9c6180bcb..953438986a 100644 --- a/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md +++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md @@ -32,7 +32,7 @@ Versões são iterações de software implementáveis que você pode empacotar e As versões se baseiam em [tags Git](https://git-scm.com/book/en/Git-Basics-Tagging), que marcam um ponto específico no histórico do seu repositório. Uma data de tag pode ser diferente de uma data de versão, já que elas podem ser criadas em momentos diferentes. Para obter mais informações sobre como visualizar as tags existentes, consulte "[Visualizar tags e versões do seu repositório](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)". -Você pode receber notificações quando novas versões são publicadas em um repositório sem receber notificações sobre outras atualizações para o repositório. Para obter mais informações, consulte {% ifversion fpt or ghae or ghes or ghec %}"[Visualizando suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Inspecionando e desinspecionando versões para um repositório](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}." +Você pode receber notificações quando novas versões são publicadas em um repositório sem receber notificações sobre outras atualizações para o repositório. Para obter mais informações, consulte "[Visualizando suas assinaturas](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)". Qualquer pessoa com acesso de leitura a um repositório pode ver e comparar versões, mas somente pessoas com permissões de gravação a um repositório podem gerenciar versões. Para obter mais informações, consulte "[Gerenciando versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository)." @@ -40,6 +40,10 @@ Qualquer pessoa com acesso de leitura a um repositório pode ver e comparar vers Você pode criar notas de versão manualmente enquanto gerencia uma versão. Como alternativa, você pode gerar automaticamente notas de versão a partir de um modelo padrão, ou personalizar seu próprio modelo de notas de versão. Para obter mais informações, consulte "[Notas de versão geradas automaticamente](/repositories/releasing-projects-on-github/automatically-generated-release-notes)". {% endif %} +{% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7054 %} +When viewing the details for a release, the creation date for each release asset is shown next to the release asset. +{% endif %} + {% ifversion fpt or ghec %} Pessoas com permissões de administrador para um repositório podem escolher se objetos {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) estão incluídos nos arquivos ZIP e tarballs que {% data variables.product.product_name %} cria para cada versão. Para obter mais informações, consulte "[Gerenciando objetos de {% data variables.large_files.product_name_short %} nos arquivos do seu repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository)". @@ -48,7 +52,7 @@ Se uma versão consertar uma vulnerabilidade de segurança, você deverá public Você pode visualizar a aba **Dependentes** do gráfico de dependências para ver quais repositórios e pacotes dependem do código no repositório e pode, portanto, ser afetado por uma nova versão. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". {% endif %} -Você também pode usar a API de Releases para reunir informações, tais como o número de vezes que as pessoas baixam um ativo de versão. Para obter mais informações, consulte "[Versões](/rest/reference/repos#releases)". +Você também pode usar a API de Releases para reunir informações, tais como o número de vezes que as pessoas baixam um ativo de versão. Para obter mais informações, consulte "[Versões](/rest/reference/releases)". {% ifversion fpt or ghec %} ## Cotas de armazenamento e banda diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md index 2104e0a898..b917f0a287 100644 --- a/translations/pt-BR/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md +++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md @@ -17,13 +17,11 @@ topics: shortTitle: Visualizar versões & tags --- -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **Dica**: Você também pode ver uma versão usando o {% data variables.product.prodname_cli %}. Para obter mais informações, consulte "[`vista da versão `](https://cli.github.com/manual/gh_release_view)" na documentação do {% data variables.product.prodname_cli %}. {% endtip %} -{% endif %} ## Visualizar versões diff --git a/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md index a1e310ab16..b571ac2ab6 100644 --- a/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md +++ b/translations/pt-BR/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md @@ -64,7 +64,7 @@ As bifurcações são listadas em ordem alfabética pelo nome de usuário da pes {% data reusables.repositories.accessing-repository-graphs %} 3. Na barra lateral esquerda, clique em **Forks** (Bifurcações). ![Aba Forks (Bifurcações)](/assets/images/help/graphs/graphs-sidebar-forks-tab.png) -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Visualizar as dependências de um repositório Você pode usar o gráfico de dependências para explorar o código do qual seu repositório depende. diff --git a/translations/pt-BR/content/rest/enterprise-admin/audit-log.md b/translations/pt-BR/content/rest/enterprise-admin/audit-log.md index f12af94048..2345e754a7 100644 --- a/translations/pt-BR/content/rest/enterprise-admin/audit-log.md +++ b/translations/pt-BR/content/rest/enterprise-admin/audit-log.md @@ -5,6 +5,7 @@ versions: fpt: '*' ghes: '>=3.3' ghec: '*' + ghae: '*' topics: - API miniTocMaxHeadingLevel: 3 diff --git a/translations/pt-BR/content/rest/guides/getting-started-with-the-checks-api.md b/translations/pt-BR/content/rest/guides/getting-started-with-the-checks-api.md index 385259bf76..ac480b23f5 100644 --- a/translations/pt-BR/content/rest/guides/getting-started-with-the-checks-api.md +++ b/translations/pt-BR/content/rest/guides/getting-started-with-the-checks-api.md @@ -41,10 +41,7 @@ Uma execução de verificação é um teste individual que faz parte de um conju ![Fluxo de trabalho das execuções de verificação](/assets/images/check_runs.png) -{% ifversion fpt or ghes or ghae or ghec %} -Se uma execução de verificação estiver em um estado incompleto por mais de 14 dias, a execução de verificação `conclusão` torna-se `obsoleta` e aparece em -{% data variables.product.prodname_dotcom %} como obsoleto com {% octicon "issue-reopened" aria-label="The issue-reopened icon" %}. Somente {% data variables.product.prodname_dotcom %} pode marcar a execuções de verificação como `obsoleto`. Para obter mais informações sobre possíveis conclusões de uma execução de verificação, consulte o parâmetro [`conclusão`](/rest/reference/checks#create-a-check-run--parameters). -{% endif %} +Se uma execução de verificação estiver em um estado incompleto por mais de 14 dias, a execução de verificação `conclusão` irá tornar-se `obsoleta` e será exibida em {% data variables.product.prodname_dotcom %} como obsoleto com {% octicon "issue-reopened" aria-label="The issue-reopened icon" %}. Somente {% data variables.product.prodname_dotcom %} pode marcar a execuções de verificação como `obsoleto`. Para obter mais informações sobre possíveis conclusões de uma execução de verificação, consulte o parâmetro [`conclusão`](/rest/reference/checks#create-a-check-run--parameters). Assim que você receber o webhook de [`check_suite`](/webhooks/event-payloads/#check_suite), você poderá criar a execução de verificação, mesmo que a verificação não esteja completa. Você pode atualizar o `status` da execução de verificação, pois ele é completado com os valores de `queued`, `in_progress` ou `completed`, e você poderá atualizar a saída de `` conforme mais informações forem disponibilizadas. Uma verificação de execução pode conter registros de hora, um link para obter mais informações sobre o seu site externo, anotações detalhadas para linhas específicas de código, e informações sobre a análise realizada. diff --git a/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md b/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md index 375a60bf60..5f5c979865 100644 --- a/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md @@ -134,7 +134,7 @@ Ao efetuar a autenticação, você deverá ver seu limite de taxa disparado para Você pode facilmente [criar um **token de acesso pessoal**][personal token] usando a sua [página de configurações de tokens de acesso pessoal][tokens settings]: -{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} {% warning %} Para ajudar a manter suas informações seguras, é altamente recomendável definir um vencimento para seus tokens de acesso pessoal. @@ -150,7 +150,7 @@ Para ajudar a manter suas informações seguras, é altamente recomendável defi ![Seleção de Token Pessoal](/assets/images/help/personal_token_ghae.png) {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} As solicitações da API que usam um token de acesso pessoal vencido retornará a data de validade do token por meio do cabeçalho `GitHub-Authentication-Token-Expiration`. Você pode usar o cabeçalho nos seus scripts para fornecer uma mensagem de aviso quando o token estiver próximo da data de vencimento. {% endif %} diff --git a/translations/pt-BR/content/rest/overview/libraries.md b/translations/pt-BR/content/rest/overview/libraries.md index 2ece9c9dc9..d98da849ef 100644 --- a/translations/pt-BR/content/rest/overview/libraries.md +++ b/translations/pt-BR/content/rest/overview/libraries.md @@ -141,9 +141,10 @@ Warning: As of late October 2021, the offical Octokit libraries are not currentl ### Rust -| Nome da Biblioteca | Repositório | -| ------------------ | ------------------------------------------------------------- | -| **Octocrab** | [XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) | +| Nome da Biblioteca | Repositório | +| ------------------ | ----------------------------------------------------------------- | +| **Octocrab** | [XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) | +| **Octocat** | [octocat-rs/octocat-rs](https://github.com/octocat-rs/octocat-rs) | ### Scala diff --git a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md index ce521e38af..37fae36d3b 100644 --- a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md @@ -120,7 +120,7 @@ Você não conseguirá efetuar a autenticação usando sua chave e segredo do OA {% ifversion fpt or ghec %} -Leia [Mais informações sobre limitação da taxa não autenticada](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). +Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-apps). {% endif %} diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md index 7ea8c4ca97..ac2d48ca1e 100644 --- a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md +++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md @@ -87,7 +87,6 @@ Se a consulta de pesquisa contém espaço em branco, é preciso colocá-lo entre Alguns símbolos não alfanuméricos, como espaços, são descartados de consultas de pesquisa de código entre aspas, por isso os resultados podem ser inesperados. -{% ifversion fpt or ghes or ghae or ghec %} ## Consultas com nomes de usuário Se sua consulta de pesquisa contiver um qualificador que exige um nome de usuário, como, por exemplo, `usuário`, `ator` ou `responsável`, você poderá usar qualquer nome de usuário de {% data variables.product.product_name %}, para especificar uma pessoa específica ou `@me` para especificar o usuário atual. @@ -98,4 +97,3 @@ Se sua consulta de pesquisa contiver um qualificador que exige um nome de usuár | `QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) corresponde a problemas atribuídos à pessoa que está visualizando os resultados | Você só pode usar `@me` com um qualificador e não como termo de pesquisa, como `@me main.workflow`. -{% endif %} diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md index c1d14b1627..5a1ef6270c 100644 --- a/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -55,15 +55,12 @@ Para pesquisar problemas e pull requests em todos os repositórios de um usuári {% data reusables.pull_requests.large-search-workaround %} - | Qualifier | Exemplo | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) identifica os problemas com a palavra "ubuntu" nos repositórios de @defunkt. | | org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) identifica os problemas nos repositórios da organização GitHub. | | repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway criado:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) corresponde a problemas do projeto shumway de @mozilla que foram criados antes de março de 2012. | - - ## Pesquisar por estado aberto ou fechado Você pode filtrar somente problemas e pull requests abertos ou fechados usando os qualificadores `state` ou `is`. @@ -133,17 +130,15 @@ Você pode usar o qualificador `involves` para encontrar problemas que envolvem | involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** corresponde problemas que envolvem @defunkt ou @jlord. | | | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) corresponde problemas que envolvem @mdo e não contêm a palavra "bootstrap" no texto. | -{% ifversion fpt or ghes or ghae or ghec %} ## Procurar problema e pull requests vinculados Você pode restringir seus resultados para apenas incluir problemas vinculados a um pull request com uma referência ou pull requests que estão vinculados a um problema que o pull request pode fechar. -| Qualifier | Exemplo | -| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) corresponde a problemas abertos no re repositório `desktop/desktop` vinculados a um pull request por uma referência fechada. | -| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) corresponde a pull requests fechados no repositório `desktop/desktop` vinculados a um problema que o pull request pode ter fechado. | -| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) corresponde a problemas abertos no repositório `desktop/desktop` que não estão vinculados a um pull request por uma referência fechada. | -| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) corresponde a pull requests abertos no repositório `desktop/desktop` que não estão vinculados a um problema que o pull request pode fechar. -{% endif %} +| Qualifier | Exemplo | +| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) corresponde a problemas abertos no re repositório `desktop/desktop` vinculados a um pull request por uma referência fechada. | +| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) corresponde a pull requests fechados no repositório `desktop/desktop` vinculados a um problema que o pull request pode ter fechado. | +| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) corresponde a problemas abertos no repositório `desktop/desktop` que não estão vinculados a um pull request por uma referência fechada. | +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) corresponde a pull requests abertos no repositório `desktop/desktop` que não estão vinculados a um problema que o pull request pode fechar. | ## Pesquisar por etiqueta @@ -212,7 +207,7 @@ Com o qualificador `language`, você pode pesquisar problemas e pull requests em ## Pesquisar por número de comentários -Você pode usar o qualificador `comments` com os [qualificadores maior que, menor que e intervalo](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) para pesquisar pelo número de comentários. +You can use the `comments` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to search by the number of comments. | Qualifier | Exemplo | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -221,7 +216,7 @@ Você pode usar o qualificador `comments` com os [qualificadores maior que, meno ## Pesquisar por número de interações -Você pode filtrar problemas e pull requests pelo número de interações com o qualificador `interactions` e os [qualificadores maior que, menor que e intervalo](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). O número de interações é o número de interações e comentários em um problema ou uma pull request. +You can filter issues and pull requests by the number of interactions with the `interactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). O número de interações é o número de interações e comentários em um problema ou uma pull request. | Qualifier | Exemplo | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -230,7 +225,7 @@ Você pode filtrar problemas e pull requests pelo número de interações com o ## Pesquisar por número de reações -Você pode filtrar problemas e pull requests pelo número de reações usando o qualificador `reactions` e os [qualificadores maior que, menor que e intervalo](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). +You can filter issues and pull requests by the number of reactions using the `reactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). | Qualifier | Exemplo | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -238,24 +233,27 @@ Você pode filtrar problemas e pull requests pelo número de reações usando o | | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) identifica os problemas com 500 a 1.000 reações. | ## Pesquisar por pull requests de rascunho -Você pode filtrar por pull requests de rascunho. Para obter mais informações, consulte "[Sobre pull requests](/articles/about-pull-requests#draft-pull-requests)". +Você pode filtrar por pull requests de rascunho. For more information, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)." -| Qualificador | Exemplo | ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) corresponde pull requests em rascunho. | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) corresponde a pull requests prontos para revisão.{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) corresponde a rascunhos de pull requests.{% endif %} +| Qualifier | Exemplo | +| ------------- | ------------------------------------------------------------------------------------------------------------- | +| `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) matches draft pull requests. | +| `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) matches pull requests that are ready for review. | ## Pesquisar por status de revisão e revisor da pull request -Você pode filtrar as pull requests com base no [status de revisão](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_ (nenhuma), _required_ (obrigatória), _approved_ (aprovada) ou _changes requested_ (alterações solicitadas)), por revisor e por revisor solicitado. +You can filter pull requests based on their [review status](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_, _required_, _approved_, or _changes requested_), by reviewer, and by requested reviewer. -| Qualifier | Exemplo | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) identifica as pull requests que não foram revisadas. | -| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) identifica as pull requests que exigem uma revisão antes do merge. | -| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) identifica as pull requests aprovadas por um revisor. | -| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) identifica as pull requests nas quais um revisor solicitou alterações. | -| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) identifica as pull requests revisadas por uma pessoa específica. | -| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) identifica as pull requests nas quais uma pessoa específica foi solicitada para revisão. Os revisores solicitados deixam de ser relacionados nos resultados da pesquisa depois de revisarem uma pull request. Se a pessoa solicitada está em uma equipe solicitada para revisão, as solicitações de revisão para essa equipe também aparecerão nos resultados de pesqusa.{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} +| Qualifier | Exemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) matches pull requests that have not been reviewed. | +| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) matches pull requests that require a review before they can be merged. | +| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) matches pull requests that a reviewer has approved. | +| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) matches pull requests in which a reviewer has asked for changes. | +| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) matches pull requests reviewed by a particular person. | +| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. Os revisores solicitados deixam de ser relacionados nos resultados da pesquisa depois de revisarem uma pull request. Se a pessoa solicitada está em uma equipe solicitada para revisão, as solicitações de revisão para essa equipe também aparecerão nos resultados de pesqusa.{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} | user-review-requested:@me | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) corresponde a pull requests que foi solicitado diretamente que você revise.{% endif %} -| team-review-requested:TEAMNAME | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) identifica as pull requests que tem solicitações de revisão da equipe `atom/design`. Os revisores solicitados deixam de ser relacionados nos resultados da pesquisa depois de revisarem uma pull request. | +| team-review-requested:TEAMNAME | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) matches pull requests that have review requests from the team `atom/design`. Os revisores solicitados deixam de ser relacionados nos resultados da pesquisa depois de revisarem uma pull request. | ## Pesquisar por data da criação ou da última atualização de um problema ou uma pull request diff --git a/translations/pt-BR/content/site-policy/github-terms/github-community-guidelines.md b/translations/pt-BR/content/site-policy/github-terms/github-community-guidelines.md index a1266f4d42..f14638efa8 100644 --- a/translations/pt-BR/content/site-policy/github-terms/github-community-guidelines.md +++ b/translations/pt-BR/content/site-policy/github-terms/github-community-guidelines.md @@ -39,7 +39,7 @@ Embora alguns desacordos possam ser resolvidos com comunicação direta e respei * **Comunicar expectativas** - Os mantenedores podem definir diretrizes específicas da comunidade para ajudar os usuários a entender como interagir com seus projetos, por exemplo, no README de um repositório, em um [arquivo de CONTRIBUIÇÃO](/articles/setting-guidelines-for-repository-contributors/) ou [código de conduta dedicado](/articles/adding-a-code-of-conduct-to-your-project/). Você pode encontrar informações adicionais sobre a criação da comunidades [aqui](/communities). -* **Comentários moderados** - Os usuários com privilégios de acesso de gravação [](/articles/repository-permission-levels-for-an-organization/) em um repositório [podem editar, excluir ou ocultar comentários de alguém](/communities/moderating-comments-and-conversations/managing-disruptive-comments) em commits, pull requests e problemas. Qualquer pessoa com acesso de leitura em um repositório pode visualizar o histórico de edição do comentário. Os autores de comentários e as pessoas com acesso de gravação a um repositório também podem excluir informações confidenciais do [histórico de edição dos comentários](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment). Moderar os seus projetos pode parecer uma grande tarefa se houver muita atividade, mas você pode [adicionar colaboradores](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) para ajudar você a gerenciar a sua comunidade. +* **Comentários moderados** - Os usuários com privilégios de acesso de gravação [](/articles/repository-permission-levels-for-an-organization/) em um repositório [podem editar, excluir ou ocultar comentários de alguém](/communities/moderating-comments-and-conversations/managing-disruptive-comments) em commits, pull requests e problemas. Qualquer pessoa com acesso de leitura em um repositório pode visualizar o histórico de edição do comentário. Os autores de comentários e as pessoas com acesso de gravação a um repositório também podem excluir informações confidenciais do [histórico de edição dos comentários](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment). Moderar os seus projetos pode parecer uma grande tarefa se houver muita atividade, mas você pode [adicionar colaboradores](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account) para ajudar você a gerenciar a sua comunidade. * **Bloquear conversas**- Se uma discussão em um problema, pull request, ou commit fugir do assunto ou do tema, ou violar o código de conduta do seu projeto ou as políticas do GitHub, os proprietários, colaboradores, e qualquer pessoa com acesso de gravação poderá [bloquear](/articles/locking-conversations/) permanentemente a conversa. diff --git a/translations/pt-BR/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md b/translations/pt-BR/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md index 7bf885072e..af9b7c2300 100644 --- a/translations/pt-BR/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md +++ b/translations/pt-BR/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md @@ -16,8 +16,8 @@ O uso do GitHub Codespaces está sujeito à [Declaração de Privacidade](/githu A atividade no github.dev está sujeita aos [termos de pré-visualizações beta do GitHub](/github/site-policy/github-terms-of-service#j-beta-previews) -## Usando o Visual Studio Code +## Usar {% data variables.product.prodname_vscode %} -O GitHub Codespaces e github.dev permitem o uso do Visual Studio Code no navegador da web. Ao usar o Visual Studio Code no navegador da web, permite-se um nível de coleta de telemetria por padrão e isso está [explicado de forma detalhada no site do Visual Studio Code](https://code.visualstudio.com/docs/getstarted/telemetry). Os usuários podem optar por não participar da telemetria, acessando o Arquivo > Preferências > Configurações no menu superior esquerdo. +GitHub Codespaces and github.dev allow for use of {% data variables.product.prodname_vscode %} in the web browser. When using {% data variables.product.prodname_vscode_shortname %} in the web browser, some telemetry collection is enabled by default and is [explained in detail on the {% data variables.product.prodname_vscode_shortname %} website](https://code.visualstudio.com/docs/getstarted/telemetry). Os usuários podem optar por não participar da telemetria, acessando o Arquivo > Preferências > Configurações no menu superior esquerdo. -Se um usuário optar por não participar da captura da telemetria no Visual Studio Code enquanto estiver dentro de um codespace, conforme definido, isso irá sincronizar a função de desabilitar a preferência de telemetria em todas as futuras sessões web no GitHub Codespaces e github.dev. +If a user chooses to opt out of telemetry capture in {% data variables.product.prodname_vscode_shortname %} while inside of a codespace as outlined, this will sync the disable telemetry preference across all future web sessions in GitHub Codespaces and github.dev. diff --git a/translations/pt-BR/content/site-policy/privacy-policies/github-privacy-statement.md b/translations/pt-BR/content/site-policy/privacy-policies/github-privacy-statement.md index f53d150ad4..3c8397d2fe 100644 --- a/translations/pt-BR/content/site-policy/privacy-policies/github-privacy-statement.md +++ b/translations/pt-BR/content/site-policy/privacy-policies/github-privacy-statement.md @@ -65,7 +65,7 @@ Solicitaremos algumas informações básicas no momento de criação da conta. Q #### Informações de pagamento Se você fizer um registro de Conta paga conosco, enviar fundos pelo Programa de Patrocinadores do GitHub ou comprar um aplicativo no GitHub Marketplace, coletaremos seu nome completo, endereço e informações do PayPal ou do cartão de crédito. Observe que o GitHub não processa ou armazena suas informações de cartão de crédito ou do PayPal, mas nosso processador de pagamento de terceiros o fará. -Se você listar e vender um aplicativo no [GitHub Marketplace](https://github.com/marketplace), precisaremos das suas informações bancárias. Se você angariar fundos pelo [Programa de Patrocinadores do GitHub](https://github.com/sponsors), solicitaremos algumas [informações adicionais](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-bank-information) no processo de registro para você participar e receber fundos através desses serviços e para fins de compliance. +Se você listar e vender um aplicativo no [GitHub Marketplace](https://github.com/marketplace), precisaremos das suas informações bancárias. If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes. #### Informações do perfil Você pode optar por nos enviar mais informações para o perfil da sua Conta, como nome completo, avatar com foto, biografia, localidade, empresa e URL para um site de terceiros. Essas informações podem incluir Informações Pessoais de Usuário. Observe que as suas informações de perfil podem ficar visíveis para outros Usuários do nosso Serviço. diff --git a/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md index 9aee95f33f..29d47bae83 100644 --- a/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md +++ b/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md @@ -19,7 +19,7 @@ topics: {% data reusables.sponsors.no-fees %} Para obter mais informações, consulte "[Sobre a cobrança do {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)". -{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)." +{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)." {% data reusables.sponsors.you-can-be-a-sponsored-organization %} Para mais informações, consulte "[Configurando o {% data variables.product.prodname_sponsors %} para a sua organização](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md index 76818fe0a5..c2ffe9cee2 100644 --- a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md +++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md @@ -16,7 +16,7 @@ shortTitle: Contribuidores de código aberto ## Ingressar no {% data variables.product.prodname_sponsors %} -{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)." +{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)." {% data reusables.sponsors.you-can-be-a-sponsored-organization %} Para mais informações, consulte "[Configurando o {% data variables.product.prodname_sponsors %} para a sua organização](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." @@ -28,7 +28,7 @@ Você pode definir uma meta para seus patrocínios. Para obter mais informaçõe ## Níveis de patrocínio -{% data reusables.sponsors.tier-details %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)," "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization), and "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)." +{% data reusables.sponsors.tier-details %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)," "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization), and "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)." É melhor criar uma série de diferentes opções de patrocínio, incluindo camadas mensais e únicas, para facilitar o apoio de qualquer pessoa ao seu trabalho. Em particular, os pagamentos únicos permitem que as pessoas recompensem os seus esforços sem se preocuparem se as suas finanças irão acomodar um calendário de pagamentos regular. diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md index 92c581bd14..38aabf9d54 100644 --- a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md +++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md @@ -11,7 +11,7 @@ versions: ghec: '*' children: - /about-github-sponsors-for-open-source-contributors - - /setting-up-github-sponsors-for-your-user-account + - /setting-up-github-sponsors-for-your-personal-account - /setting-up-github-sponsors-for-your-organization - /editing-your-profile-details-for-github-sponsors - /managing-your-sponsorship-goal diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md index 87dddbacf6..758bdebd96 100644 --- a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -23,7 +23,7 @@ shortTitle: Configurar para organização Depois de receber um convite para sua organização ingressar no {% data variables.product.prodname_sponsors %}, você poderá concluir as etapas abaixo para se tornar uma organização patrocinada. -To join {% data variables.product.prodname_sponsors %} as an individual contributor outside an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)." +To join {% data variables.product.prodname_sponsors %} as an individual contributor outside an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)." {% data reusables.sponsors.navigate-to-github-sponsors %} {% data reusables.sponsors.view-eligible-accounts %} diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md similarity index 96% rename from translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md rename to translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md index 60b992cea7..cf0194e213 100644 --- a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md @@ -1,10 +1,11 @@ --- -title: Configurando o GitHub Sponsors (Patrocinadores do GitHub) para sua conta de usuário +title: Setting up GitHub Sponsors for your personal account intro: 'Você pode se tornar um desenvolvedor patrocinado participando de {% data variables.product.prodname_sponsors %}, completando seu perfil de desenvolvedor patrocinado, criando camadasde patrocínio, enviando seus dados bancários e fiscais e habilitando a autenticação de dois fatores para sua conta em {% data variables.product.product_location %}.' redirect_from: - /articles/becoming-a-sponsored-developer - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account + - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account versions: fpt: '*' ghec: '*' diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md index 65a5a05311..8f00004ef9 100644 --- a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md +++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md @@ -28,7 +28,7 @@ Se você for contribuinte nos Estados Unidos, você deverá enviar um [W-9](http Os formulários de imposto W-8 BEN e W-8 BEN-E ajudam {% data variables.product.prodname_dotcom %} a determinar o proprietário beneficiário de uma quantia sujeita a retenção. -Se você for contribuinte em qualquer outra região fora dos Estados Unidos, você deverá enviar um formulário [W-8 BEN](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf) (pessoa física) ou [W-8 BEN-E](https://www.irs.gov/forms-pubs/about-form-w-8-ben-e) (pessoa jurídica) antes que você possa publicar o seu perfil de {% data variables.product.prodname_sponsors %}. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-tax-information)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)." {% data variables.product.prodname_dotcom %} lhe enviará os formulários apropriados, avisando quando estiverem vencidos, e lhe dará um tempo razoável para completar e enviar os formulários. +Se você for contribuinte em qualquer outra região fora dos Estados Unidos, você deverá enviar um formulário [W-8 BEN](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf) (pessoa física) ou [W-8 BEN-E](https://www.irs.gov/forms-pubs/about-form-w-8-ben-e) (pessoa jurídica) antes que você possa publicar o seu perfil de {% data variables.product.prodname_sponsors %}. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-tax-information)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)." {% data variables.product.prodname_dotcom %} lhe enviará os formulários apropriados, avisando quando estiverem vencidos, e lhe dará um tempo razoável para completar e enviar os formulários. Se lhe foi atribuído um formulário de imposto incorreto, [entre em contato com o suporte de {% data variables.product.prodname_dotcom %} suporte](https://support.github.com/contact?form%5Bsubject%5D=GitHub%20Sponsors:%20tax%20form&tags=sponsors) para receber o formulário correto para a sua situação. diff --git a/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md index 75927abdd6..78220accdf 100644 --- a/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md +++ b/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md @@ -43,7 +43,7 @@ Você pode escolher se deseja mostrar seu patrocínio publicamente. Patrocínios Se a conta patrocinada for retirada, a sua camada permanecerá em vigor para você até que você escolha uma camada diferente ou cancele a sua assinatura. Para obter mais informações, consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)". -Se a conta que você deseja patrocinar não tiver um perfil em {% data variables.product.prodname_sponsors %}, você pode incentivar que participe. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." +Se a conta que você deseja patrocinar não tiver um perfil em {% data variables.product.prodname_sponsors %}, você pode incentivar que participe. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." {% data reusables.sponsors.sponsorships-not-tax-deductible %} diff --git a/translations/pt-BR/data/features/integration-branch-protection-exceptions.yml b/translations/pt-BR/data/features/integration-branch-protection-exceptions.yml new file mode 100644 index 0000000000..3c6a729fb9 --- /dev/null +++ b/translations/pt-BR/data/features/integration-branch-protection-exceptions.yml @@ -0,0 +1,8 @@ +--- +#Reference: #6665 +#GitHub Apps are supported as actors in all types of exceptions to branch protections +versions: + fpt: '*' + ghec: '*' + ghes: '>= 3.6' + ghae: 'issue-6665' diff --git a/translations/pt-BR/data/features/math.yml b/translations/pt-BR/data/features/math.yml new file mode 100644 index 0000000000..b7b89eb201 --- /dev/null +++ b/translations/pt-BR/data/features/math.yml @@ -0,0 +1,8 @@ +--- +#Issues 6054 +#Math support using LaTeX syntax +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.6' + ghae: 'issue-6054' diff --git a/translations/pt-BR/data/features/security-managers.yml b/translations/pt-BR/data/features/security-managers.yml index 6e62d12897..77f12eb126 100644 --- a/translations/pt-BR/data/features/security-managers.yml +++ b/translations/pt-BR/data/features/security-managers.yml @@ -4,5 +4,5 @@ versions: fpt: '*' ghes: '>=3.3' - ghae: 'issue-4999' + ghae: '*' ghec: '*' diff --git a/translations/pt-BR/data/features/security-overview-feature-specific-alert-page.yml b/translations/pt-BR/data/features/security-overview-feature-specific-alert-page.yml new file mode 100644 index 0000000000..1aebf50245 --- /dev/null +++ b/translations/pt-BR/data/features/security-overview-feature-specific-alert-page.yml @@ -0,0 +1,8 @@ +--- +#Reference: #7028. +#Documentation for feature-specific page for security overview at enterprise-level. +versions: + fpt: '*' + ghec: '*' + ghes: '>3.5' + ghae: 'issue-7028' diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/21.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/21.yml new file mode 100644 index 0000000000..8a58ed34ba --- /dev/null +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/21.yml @@ -0,0 +1,25 @@ +--- +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - Os pacotes foram atualizados para as últimas versões de segurança. + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not supported. + - Support bundles now include the row count of tables stored in MySQL. + known_issues: + - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes. + - Em uma instância de {% data variables.product.prodname_ghe_server %} recém-configurada sem usuários, um invasor pode criar o primeiro usuário administrador. + - As regras de firewall personalizadas são removidas durante o processo de atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres. + - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - Se o {% data variables.product.prodname_actions %} estiver habilitado para {% data variables.product.prodname_ghe_server %}, a desmontagem de um nó de réplica com `ghe-repl-teardown` será bem-sucedida, mas poderá retornar `ERROR:Running migrations`. + - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-2/13.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/13.yml new file mode 100644 index 0000000000..14980a2fc1 --- /dev/null +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/13.yml @@ -0,0 +1,27 @@ +--- +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - Os pacotes foram atualizados para as últimas versões de segurança. + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - Videos uploaded to issue comments would not be rendered properly. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. + - Support bundles now include the row count of tables stored in MySQL. + - Dependency Graph can now be enabled without vulnerability data, allowing you to see what dependencies are in use and at what versions. Enabling Dependency Graph without enabling {% data variables.product.prodname_github_connect %} will **not** provide vulnerability information. + known_issues: + - Em uma instância de {% data variables.product.prodname_ghe_server %} recém-configurada sem usuários, um invasor pode criar o primeiro usuário administrador. + - As regras de firewall personalizadas são removidas durante o processo de atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres. + - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes. + - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-3/8.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-3/8.yml new file mode 100644 index 0000000000..0d9ce58737 --- /dev/null +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-3/8.yml @@ -0,0 +1,34 @@ +--- +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - Os pacotes foram atualizados para as últimas versões de segurança. + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + - Videos uploaded to issue comments would not be rendered properly. + - When using the file finder on a repository page, typing the backspace key within the search field would result in search results being listed multiple times and cause rendering problems. + - When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events. + - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. + - Support bundles now include the row count of tables stored in MySQL. + - When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects. + - The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload. + known_issues: + - Após a atualização para {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} pode não ser iniciado automaticamente. Para resolver esse problema, conecte-se ao dispositivo via SSH e execute o comando `ghe-actions-start`. + - Em uma instância de {% data variables.product.prodname_ghe_server %} recém-configurada sem usuários, um invasor pode criar o primeiro usuário administrador. + - As regras de firewall personalizadas são removidas durante o processo de atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres. + - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes. + - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive. + - 'As configurações de armazenamento de {% data variables.product.prodname_actions %} não podem ser validadas e salvas no {% data variables.enterprise.management_console %} quando "Forçar estilo de caminho" for selecionado e deverão ser definidas com a ferramenta de linha de comando `ghe-actions-precheck`.' + - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-4/2.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-4/2.yml index 1d57b1b237..3ee77486aa 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-4/2.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-4/2.yml @@ -73,5 +73,10 @@ sections: Os repositórios que não estavam presentes e ativos antes de atualizar para {% data variables.product.prodname_ghe_server %} 3.3 podem não ser executados da forma ideal até que uma tarefa de manutenção de repositório seja executada e concluída com sucesso. Para iniciar uma tarefa de manutenção do repositório manualmente, acesse https:///stafftools/repositórios///network` para cada repositório afetado e clique no botão Cronograma. + - + heading: Theme picker for GitHub Pages has been removed + notes: + - | + The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)." backups: - '{% data variables.product.prodname_ghe_server %} 3.4 exige pelo menos [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) para [Backups e recuperação de desastre](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).' diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-4/3.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-4/3.yml new file mode 100644 index 0000000000..2cd0f3656f --- /dev/null +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-4/3.yml @@ -0,0 +1,41 @@ +--- +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - Os pacotes foram atualizados para as últimas versões de segurança. + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. + - When adding custom patterns and providing non-UTF8 test strings, match highlighting was incorrect. + - LDAP users with an underscore character (`_`) in their user names can now login successfully. + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - After enabling SAML encrypted assertions with Azure as identity provider, the sign in page would fail with a `500` error. + - Character key shortcut preferences weren't respected. + - Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + - Videos uploaded to issue comments would not be rendered properly. + - When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events. + - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - The Nomad allocation timeout for Dependency Graph has been increased to ensure post-upgrade migrations can complete. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. + - Support bundles now include the row count of tables stored in MySQL. + - When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects. + - The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload. + known_issues: + - Em uma instância de {% data variables.product.prodname_ghe_server %} recém-configurada sem usuários, um invasor pode criar o primeiro usuário administrador. + - As regras de firewall personalizadas são removidas durante o processo de atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres. + - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes. + - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive. + - | + When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11] + + To work around this problem, you can take one of the two following actions. + - Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute. + - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml index f789f0dcc1..0973ff2246 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -333,6 +333,11 @@ sections: notes: - | The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, 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)." + - + heading: Theme picker for GitHub Pages has been removed + notes: + - | + The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)." known_issues: - Em uma instância de {% data variables.product.prodname_ghe_server %} recém-configurada sem usuários, um invasor pode criar o primeiro usuário administrador. - As regras de firewall personalizadas são removidas durante o processo de atualização. diff --git a/translations/pt-BR/data/release-notes/github-ae/2021-06/2021-12-06.yml b/translations/pt-BR/data/release-notes/github-ae/2021-06/2021-12-06.yml index 9c485d1c2d..c0f4db0978 100644 --- a/translations/pt-BR/data/release-notes/github-ae/2021-06/2021-12-06.yml +++ b/translations/pt-BR/data/release-notes/github-ae/2021-06/2021-12-06.yml @@ -2,7 +2,7 @@ date: '2021-12-06' friendlyDate: '6 de Dezembro de 2021' title: '6 de Dezembro de 2021' -currentWeek: true +currentWeek: false sections: features: - diff --git a/translations/pt-BR/data/release-notes/github-ae/2022-05/2022-05-17.yml b/translations/pt-BR/data/release-notes/github-ae/2022-05/2022-05-17.yml new file mode 100644 index 0000000000..1db9dda802 --- /dev/null +++ b/translations/pt-BR/data/release-notes/github-ae/2022-05/2022-05-17.yml @@ -0,0 +1,190 @@ +--- +date: '2022-05-17' +friendlyDate: 'May 17, 2022' +title: 'May 17, 2022' +currentWeek: true +sections: + features: + - + heading: 'GitHub Advanced Security features are generally available' + notes: + - | + Code scanning and secret scanning are now generally available for GitHub AE. For more information, see "[About code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)." + - | + Custom patterns for secret scanning is now generally available. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + - + heading: 'View all code scanning alerts for a pull request' + notes: + - | + You can now find all code scanning alerts associated with your pull request with the new pull request filter on the code scanning alerts page. The pull request checks page shows the alerts introduced in a pull request, but not existing alerts on the pull request branch. The new "View all branch alerts" link on the Checks page takes you to the code scanning alerts page with the specific pull request filter already applied, so you can see all the alerts associated with your pull request. This can be useful to manage lots of alerts, and to see more detailed information for individual alerts. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)." + - + heading: 'Security overview for organizations' + notes: + - | + GitHub Advanced Security now offers an organization-level view of the application security risks detected by code scanning, Dependabot, and secret scanning. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. + + In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + + ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) + - + heading: 'Gráfico de dependências' + notes: + - | + Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." + - + heading: 'Alertas do Dependabot' + notes: + - | + Dependabot alerts can now notify you of vulnerabilities in your dependencies on GitHub AE. You can enable Dependabot alerts by enabling the dependency graph, enabling GitHub Connect, and syncing vulnerabilities from the GitHub Advisory Database. This feature is in beta and subject to change. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)." + + After you enable Dependabot alerts, members of your organization will receive notifications any time a new vulnerability that affects their dependencies is added to the GitHub Advisory Database or a vulnerable dependency is added to their manifest. Members can customize notification settings. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)." + - + heading: 'Security manager role for organizations' + notes: + - | + Organizations can now grant teams permission to manage security alerts and settings on all their repositories. The "security manager" role can be applied to any team and grants the team's members the following permissions. + + - Read access on all repositories in the organization + - Write access on all security alerts in the organization + - Access to the organization-level security tab + - Write access on security settings at the organization level + - Write access on security settings at the repository level + + For more information, see "[Managing security managers in your organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." + - + heading: 'Ephemeral runners and autoscaling webhooks for GitHub Actions' + notes: + - | + GitHub AE now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. + + Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, GitHub AE automatically unregisteres ephemeral runners, allowing you to perform any post-job management. + + You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to job requests from GitHub Actions. + + For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)." + - + heading: 'Composite actions for GitHub Actions' + notes: + - | + You can reduce duplication in your workflows by using composition to reference other actions. Previously, actions written in YAML could only use scripts. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)." + - + heading: 'New token scope for management of self-hosted runners' + notes: + - | + Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the `new manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to many REST API endpoints to manage your enterprise's self-hosted runners. + - + heading: 'Audit log accessible via REST API' + notes: + - | + You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." + - + heading: 'Expiration dates for personal access tokens' + notes: + - | + You can now set an expiration date on new and existing personal access tokens. GitHub AE will send you an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving you a duplicate token with the same properties as the original. When using a token with the GitHub AE API, you'll see a new header, `GitHub-Authentication-Token-Expiration`, indicating the token's expiration date. You can use this in scripts, for example to log a warning message as the expiration date approaches. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" and "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#using-personal-access-tokens)." + - + heading: 'Export a list of people with access to a repository' + notes: + - | + Organization owners can now export a list of the people with access to a repository in CSV format. For more information, see "[Viewing people with access to your repository](/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository#exporting-a-list-of-people-with-access-to-your-repository)." + - + heading: 'Improved management of code review assignments' + notes: + - | + New settings to manage code review assignment code review assignment help distribute a team's pull request review across the team members so reviews aren't the responsibility of just one or two team members. + + - Child team members: Limit assignment to only direct members of the team. Previously, team review requests could be assigned to direct members of the team or members of child teams. + - Count existing requests: Continue with automatic assignment even if one or more members of the team are already requested. Previously, a team member who was already requested would be counted as one of the team's automatic review requests. + - Team review request: Keep a team assigned to review even if one or more members is newly assigned. + + For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." + - + heading: 'New themes' + notes: + - | + Two new themes are available for the GitHub AE web UI. + + - A dark high contrast theme, with greater contrast between foreground and background elements + - Light and dark colorblind, which swap colors such as red and green for orange and blue + + For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + - + heading: 'Markdown improvements' + notes: + - | + You can now use footnote syntax in any Markdown field to reference relevant information without disrupting the flow of your prose. Footnotes are displayed as superscript links. Click a footnote to jump to the reference, displayed in a new section at the bottom of the document. 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#footnotes)." + - | + You can now toggle between the source view and rendered Markdown view through the web UI by clicking the {% octicon "code" aria-label="The Code icon" %} button to "Display the source diff" at the top of any Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file. + - | + You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + - | + GitHub AE now automatically generates a table of contents for Wikis, based on headings. + changes: + - + heading: 'Performance' + notes: + - | + As cargas e tarefas de página agora são significativamente mais rápidas para repositórios com muitas refs do Git. + - + heading: 'Administração' + notes: + - | + The user impersonation process is improved. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise owner. For more information, see "[Impersonating a user](/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)." + - + heading: 'GitHub Actions' + notes: + - | + To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." + - | + The audit log now includes additional events for GitHub Actions. GitHub AE now records audit log entries for the following events. + + - A self-hosted runner is registered or removed. + - A self-hosted runner is added to a runner group, or removed from a runner group. + - A runner group is created or removed. + - A workflow run is created or completed. + - A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner. + + For more information, see "[Security hardening for GitHub Actions](/actions/security-guides/security-hardening-for-github-actions)." + - + heading: 'Segurança Avançada GitHub' + notes: + - | + Code scanning will now map alerts identified in `on:push` workflows to show up on pull requests, when possible. The alerts shown on the pull request are those identified by comparing the existing analysis of the head of the branch to the analysis for the target branch that you are merging against. Note that if the pull request's merge commit is not used, alerts can be less accurate when compared to the approach that uses `on:pull_request` triggers. For more information, see "[About code scanning with CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." + + Some other CI/CD systems can exclusively be configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, code scanning will try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see "[Uploading a SARIF file to GitHub](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)." + - | + GitHub AE now detects secrets from additional providers. For more information, see "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets)." + - + heading: 'Pull requests' + notes: + - | + The timeline and Reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members because that team uses code review assignment. + + ![Screenshot of indicator for automatic assignment of code review](https://user-images.githubusercontent.com/2503052/134931920-409dea07-7a70-4557-b208-963357db7a0d.png) + - | + You can now filter pull request searches to only include pull requests you are directly requested to review by choosing **Awaiting review from you**. For more information, see "[Searching issues and pull requests](https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests)." + - | + Se você especificar o nome exato de um branch ao usar o menu seletor do branch, o resultado agora será exibido na parte superior da lista de branches correspondentes. Anteriormente, as correspondências exatas de nomes de branch poderiam aparecer na parte inferior da lista. + - | + When viewing a branch that has a corresponding open pull request, GitHub AE now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request. + - | + You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click in the toolbar. Note that this feature is currently only available in some browsers. + - | + A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [GitHub Changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/). + - + heading: 'Repositórios' + notes: + - | + GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](​​https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." + - | + You can now add, delete, or view autolinks through the Repositories API's Autolinks endpoint. For more information, see "[Autolinked references and URLs](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)" and "[Repositories](/rest/reference/repos#autolinks)" in the REST API documentation. + - + heading: 'Versões' + notes: + - | + The tag selection component for GitHub releases is now a drop-down menu rather than a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)." + - + heading: 'markdown' + notes: + - | + When dragging and dropping files such as images and videos into a Markdown editor, GitHub AE now uses the mouse pointer location instead of the cursor location when placing the file. diff --git a/translations/pt-BR/data/reusables/actions/allow-specific-actions-intro.md b/translations/pt-BR/data/reusables/actions/allow-specific-actions-intro.md index a41cd1c485..e92fe92ae4 100644 --- a/translations/pt-BR/data/reusables/actions/allow-specific-actions-intro.md +++ b/translations/pt-BR/data/reusables/actions/allow-specific-actions-intro.md @@ -5,8 +5,8 @@ When you choose {% data reusables.actions.policy-label-for-select-actions-workflows %}, local actions{% if actions-workflow-policy %} and reusable workflows{% endif %} are allowed, and there are additional options for allowing other specific actions{% if actions-workflow-policy %} and reusable workflows{% endif %}: -- **Permitir ações criadas por {% data variables.product.prodname_dotcom %}:** Você pode permitir que todas as ações criadas por {% data variables.product.prodname_dotcom %} sejam usadas por fluxos de trabalho. Ações criadas por {% data variables.product.prodname_dotcom %} estão localizadas em `ações` e nas organizações do `github`. Para obter mais informações, consulte as [`ações`](https://github.com/actions) e organizações do [`github`](https://github.com/github).{% ifversion fpt or ghes or ghae-issue-5094 or ghec %} -- **Permitir ações do Marketplace por criadores verificados:** {% ifversion ghes or ghae-issue-5094 %}Esta opção está disponível se você tiver {% data variables.product.prodname_github_connect %} habilitado e configurado com {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Habilitando o acesso automático às ações do GitHub.com usando o GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect).{% endif %} Você pode permitir que todas as ações de {% data variables.product.prodname_marketplace %} criadas por criadores verificados sejam usadas por fluxos de trabalho. Quando o GitHub tiver verificado o criador da ação como uma organização parceira, o selo {% octicon "verified" aria-label="The verified badge" %} será exibido ao lado da ação em {% data variables.product.prodname_marketplace %}.{% endif %} +- **Permitir ações criadas por {% data variables.product.prodname_dotcom %}:** Você pode permitir que todas as ações criadas por {% data variables.product.prodname_dotcom %} sejam usadas por fluxos de trabalho. Ações criadas por {% data variables.product.prodname_dotcom %} estão localizadas em `ações` e nas organizações do `github`. Para obter mais informações, consulte as [`ações`](https://github.com/actions) e organizações do [`github`](https://github.com/github).{% ifversion fpt or ghes or ghae or ghec %} +- **Permitir ações do Marketplace por criadores verificados:** {% ifversion ghes or ghae %}Esta opção está disponível se você tiver {% data variables.product.prodname_github_connect %} habilitado e configurado com {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Habilitando o acesso automático às ações do GitHub.com usando o GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect).{% endif %} Você pode permitir que todas as ações de {% data variables.product.prodname_marketplace %} criadas por criadores verificados sejam usadas por fluxos de trabalho. Quando o GitHub tiver verificado o criador da ação como uma organização parceira, o selo {% octicon "verified" aria-label="The verified badge" %} será exibido ao lado da ação em {% data variables.product.prodname_marketplace %}.{% endif %} - **Allow specified actions{% if actions-workflow-policy %} and reusable workflows{% endif %}:** You can restrict workflows to use actions{% if actions-workflow-policy %} and reusable workflows{% endif %} in specific organizations and repositories. To restrict access to specific tags or commit SHAs of an action{% if actions-workflow-policy %} or reusable workflow{% endif %}, use the same syntax used in the workflow to select the action{% if actions-workflow-policy %} or reusable workflow{% endif %}. diff --git a/translations/pt-BR/data/reusables/actions/jobs/using-matrix-strategy.md b/translations/pt-BR/data/reusables/actions/jobs/using-matrix-strategy.md index 842eab0b8f..1769c15511 100644 --- a/translations/pt-BR/data/reusables/actions/jobs/using-matrix-strategy.md +++ b/translations/pt-BR/data/reusables/actions/jobs/using-matrix-strategy.md @@ -1,4 +1,4 @@ -Use `jobs..strategy.matrix` para definir uma matriz de diferentes configurações de trabalho. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a veriable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`: +Use `jobs..strategy.matrix` para definir uma matriz de diferentes configurações de trabalho. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a variable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`: ```yaml jobs: diff --git a/translations/pt-BR/data/reusables/actions/message-parameters.md b/translations/pt-BR/data/reusables/actions/message-parameters.md index 662e5cf41f..ed75b5c1cc 100644 --- a/translations/pt-BR/data/reusables/actions/message-parameters.md +++ b/translations/pt-BR/data/reusables/actions/message-parameters.md @@ -1 +1 @@ -| Parâmetro | Valor | | :- | :- |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `title` | Custom title |{% endif %} | `file` | Título personalizado| | `col` | Número da colina, começando com 1 |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `endColumn` | Número final da coluna |{% endif %} | `line` | Número final da linha, começando com 1 |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `endLine` | Número final da linha |{% endif %} +| Parâmetro | Valor | | :- | :- |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `title` | Custom title |{% endif %} | `file` | Título personalizado| | `col` | Número da colina, começando com 1 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endColumn` | Número final da coluna |{% endif %} | `line` | Número final da linha, começando com 1 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endLine` | Número final da linha |{% endif %} diff --git a/translations/pt-BR/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md b/translations/pt-BR/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md index c896cf00e0..ee41c75e0f 100644 --- a/translations/pt-BR/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md +++ b/translations/pt-BR/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md @@ -20,7 +20,7 @@ on: {% note %} -**Note:** If a workflow is skipped due to [path filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), [branch filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) or a [commit message](/actions/managing-workflow-runs/skipping-workflow-runs), then checks associated with that workflow will remain in a "Pending" state. A pull request that requires those checks to be successful will be blocked from merging. For more information, see "[Handling skipped but required checks](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks)." +**Observação:** Se um fluxo de trabalho for ignorado devido à [filtragem do caminho](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), a [filtragem do caminho](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) ou [mensagem de commit](/actions/managing-workflow-runs/skipping-workflow-runs) as verificações associadas a esse fluxo de trabalho permanecerão em um estado "Pendente". Um pull request que requer que essas verificações sejam bem sucedidas será bloqueado do merge. For more information, see "[Handling skipped but required checks](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks)." {% endnote %} diff --git a/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md index 80a1833994..1c83fc9695 100644 --- a/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/pt-BR/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,4 +1,3 @@ -{% ifversion fpt or ghes or ghae or ghec %} {% warning %} **Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% ifversion fpt or ghec %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %} For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). @@ -6,4 +5,3 @@ {% ifversion ghes or ghae %} Authentication to the API using query parameters while available is no longer supported due to security concerns. Instead we recommend integrators move their access token, `client_id`, or `client_secret` in the header. {% data variables.product.prodname_dotcom %} will announce the removal of authentication by query parameters with advanced notice. {% endif %} {% endwarning %} -{% endif %} diff --git a/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md b/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md index 6f0b62c9db..3e34bbb210 100644 --- a/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md +++ b/translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md @@ -28,13 +28,13 @@ {%- ifversion ghes %} | `config_entry` | Contains activities related to configuration settings. Esses eventos só são visíveis no log de auditoria do administrador do site. {%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | `dependabot_alerts` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" | `dependabot_alerts_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. | `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access. {%- endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} | `dependabot_security_updates` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." | `dependabot_security_updates_new_repos` | 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 or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} | `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". | `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization. {%- endif %} {%- ifversion fpt or ghec %} @@ -116,7 +116,7 @@ {%- ifversion fpt or ghec %} | `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization. {%- endif %} -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} | `repository_vulnerability_alert` | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies). {%- endif %} {%- ifversion fpt or ghec %} diff --git a/translations/pt-BR/data/reusables/cli/filter-issues-and-pull-requests-tip.md b/translations/pt-BR/data/reusables/cli/filter-issues-and-pull-requests-tip.md index 97b13efa7e..a9d5e7a838 100644 --- a/translations/pt-BR/data/reusables/cli/filter-issues-and-pull-requests-tip.md +++ b/translations/pt-BR/data/reusables/cli/filter-issues-and-pull-requests-tip.md @@ -1,7 +1,5 @@ -{% ifversion fpt or ghes or ghae or ghec %} {% tip %} **Dica**: Também é possível filtrar problemas ou pull requests usando o {% data variables.product.prodname_cli %}. Para mais informações, consulte a "[`lista de problemas do gh`](https://cli.github.com/manual/gh_issue_list)" ou "[`lista pr do gh`](https://cli.github.com/manual/gh_pr_list)" na documentação de {% data variables.product.prodname_cli %}. {% endtip %} -{% endif %} diff --git a/translations/pt-BR/data/reusables/code-scanning/beta.md b/translations/pt-BR/data/reusables/code-scanning/beta.md index f8dd643a8d..2d7da13311 100644 --- a/translations/pt-BR/data/reusables/code-scanning/beta.md +++ b/translations/pt-BR/data/reusables/code-scanning/beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-5752 %} +{% ifversion ghae %} diff --git a/translations/pt-BR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/pt-BR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md index 44f5e4ef6f..2eacc3e212 100644 --- a/translations/pt-BR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ b/translations/pt-BR/data/reusables/codespaces/click-remote-explorer-icon-vscode.md @@ -1 +1 @@ -1. Em {% data variables.product.prodname_vscode %}, na barra lateral esquerda, clique no ícone Remote Explorer. ![O ícone do Remote Explorer em {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) +1. Em {% data variables.product.prodname_vscode_shortname %}, na barra lateral esquerda, clique no ícone Remote Explorer. ![O ícone do Remote Explorer em {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) diff --git a/translations/pt-BR/data/reusables/codespaces/committing-link-to-procedure.md b/translations/pt-BR/data/reusables/codespaces/committing-link-to-procedure.md index c4f51c49fa..d99cf3c9e3 100644 --- a/translations/pt-BR/data/reusables/codespaces/committing-link-to-procedure.md +++ b/translations/pt-BR/data/reusables/codespaces/committing-link-to-procedure.md @@ -1,3 +1,3 @@ -Depois de realizar alterações no seu código, tanto novo código como de configuração, você deverá fazer commit das suas alterações. O commit das alterações no seu repositório garante que qualquer pessoa que crie um codespace deste repositório tenha a mesma configuração. Isto também significa que qualquer personalização que você faça, como adicionar extensões de{% data variables.product.prodname_vscode %}, aparecerá para todos os usuários. +Depois de realizar alterações no seu código, tanto novo código como de configuração, você deverá fazer commit das suas alterações. O commit das alterações no seu repositório garante que qualquer pessoa que crie um codespace deste repositório tenha a mesma configuração. Isto também significa que qualquer personalização que você faça, como adicionar extensões de{% data variables.product.prodname_vscode_shortname %}, aparecerá para todos os usuários. Para obter informações, consulte "[Usando o controle de fonte no seu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)". diff --git a/translations/pt-BR/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/pt-BR/data/reusables/codespaces/connect-to-codespace-from-vscode.md index be18129c85..38cb536448 100644 --- a/translations/pt-BR/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ b/translations/pt-BR/data/reusables/codespaces/connect-to-codespace-from-vscode.md @@ -1 +1 @@ -Você pode se conectar ao seu código diretamente de {% data variables.product.prodname_vscode %}. Para obter mais informações, consulte "[Usar codespaces no {% data variables.product.prodname_vscode %}](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)". +Você pode se conectar ao seu código diretamente de {% data variables.product.prodname_vscode_shortname %}. Para obter mais informações, consulte "[Usar codespaces no {% data variables.product.prodname_vscode_shortname %}](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)". diff --git a/translations/pt-BR/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/pt-BR/data/reusables/codespaces/creating-a-codespace-in-vscode.md index a858083c27..284f5ec7d4 100644 --- a/translations/pt-BR/data/reusables/codespaces/creating-a-codespace-in-vscode.md +++ b/translations/pt-BR/data/reusables/codespaces/creating-a-codespace-in-vscode.md @@ -1,8 +1,8 @@ -After you connect your account on {% data variables.product.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). +After you connect your account on {% data variables.product.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces). {% note %} -**Note**: Currently, {% data variables.product.prodname_vscode %} doesn't allow you to choose a dev container configuration when you create a codespace. Se você quiser escolher uma configuração de contêiner de desenvolvimento específica, use a interface web do {% data variables.product.prodname_dotcom %} para criar o seu codespace. For more information, click the **Web browser** tab at the top of this page. +**Observação**: Atualmente, {% data variables.product.prodname_vscode_shortname %} não permite que você escolha uma configuração de contêiner de desenvolvimento ao cria um codespace. Se você quiser escolher uma configuração de contêiner de desenvolvimento específica, use a interface web do {% data variables.product.prodname_dotcom %} para criar o seu codespace. For more information, click the **Web browser** tab at the top of this page. {% endnote %} diff --git a/translations/pt-BR/data/reusables/codespaces/deleting-a-codespace-in-vscode.md b/translations/pt-BR/data/reusables/codespaces/deleting-a-codespace-in-vscode.md index 32afc67969..c0e00acd87 100644 --- a/translations/pt-BR/data/reusables/codespaces/deleting-a-codespace-in-vscode.md +++ b/translations/pt-BR/data/reusables/codespaces/deleting-a-codespace-in-vscode.md @@ -1,4 +1,4 @@ -You can delete codespaces from within {% data variables.product.prodname_vscode %} when you are not currently working in a codespace. +You can delete codespaces from within {% data variables.product.prodname_vscode_shortname %} when you are not currently working in a codespace. {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 1. Under "GITHUB CODESPACES", right-click the codespace you want to delete. diff --git a/translations/pt-BR/data/reusables/codespaces/more-info-devcontainer.md b/translations/pt-BR/data/reusables/codespaces/more-info-devcontainer.md index 430a9f1156..f0fd5c863b 100644 --- a/translations/pt-BR/data/reusables/codespaces/more-info-devcontainer.md +++ b/translations/pt-BR/data/reusables/codespaces/more-info-devcontainer.md @@ -1 +1 @@ -For information about the settings and properties that you can set in a `devcontainer.json` file, see "[devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json)" in the {% data variables.product.prodname_vscode %} documentation. \ No newline at end of file +For information about the settings and properties that you can set in a `devcontainer.json` file, see "[devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json)" in the {% data variables.product.prodname_vscode_shortname %} documentation. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/use-visual-studio-features.md b/translations/pt-BR/data/reusables/codespaces/use-visual-studio-features.md index 428e0b5879..8e25b1c1ff 100644 --- a/translations/pt-BR/data/reusables/codespaces/use-visual-studio-features.md +++ b/translations/pt-BR/data/reusables/codespaces/use-visual-studio-features.md @@ -1 +1 @@ -Você pode editar código, depurar e usar comandos do Git ao mesmo tempo que faz o desenvolvimento em um codespace com {% data variables.product.prodname_vscode %}. For more information, see the [{% data variables.product.prodname_vscode %} documentation](https://code.visualstudio.com/docs). +Você pode editar código, depurar e usar comandos do Git ao mesmo tempo que faz o desenvolvimento em um codespace com {% data variables.product.prodname_vscode_shortname %}. For more information, see the [{% data variables.product.prodname_vscode_shortname %} documentation](https://code.visualstudio.com/docs). diff --git a/translations/pt-BR/data/reusables/codespaces/vscode-settings-order.md b/translations/pt-BR/data/reusables/codespaces/vscode-settings-order.md index 56dc36a4e4..4cd623fca4 100644 --- a/translations/pt-BR/data/reusables/codespaces/vscode-settings-order.md +++ b/translations/pt-BR/data/reusables/codespaces/vscode-settings-order.md @@ -1 +1 @@ -Ao configurar as configurações de editor para {% data variables.product.prodname_vscode %}, há três escopos disponíveis: _Workspace_, _Remote [Codespaces]_, e _User_. Se uma configuração for definida em vários escopos, as configurações do _Workspace_ têm prioridade e, em seguida _Remote [Codespaces]_, depois _User_. +Ao configurar as configurações de editor para {% data variables.product.prodname_vscode_shortname %}, há três escopos disponíveis: _Workspace_, _Remote [Codespaces]_, e _User_. Se uma configuração for definida em vários escopos, as configurações do _Workspace_ têm prioridade e, em seguida _Remote [Codespaces]_, depois _User_. diff --git a/translations/pt-BR/data/reusables/dependabot/dependabot-alerts-beta.md b/translations/pt-BR/data/reusables/dependabot/dependabot-alerts-beta.md index 4cfd65386a..c2bfc45615 100644 --- a/translations/pt-BR/data/reusables/dependabot/dependabot-alerts-beta.md +++ b/translations/pt-BR/data/reusables/dependabot/dependabot-alerts-beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-4864 %} +{% ifversion ghae %} {% note %} **Note:** {% data variables.product.prodname_dependabot_alerts %} is currently in beta and is subject to change. diff --git a/translations/pt-BR/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md b/translations/pt-BR/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md index d5ae9b8415..930c6ac941 100644 --- a/translations/pt-BR/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md +++ b/translations/pt-BR/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md @@ -1,3 +1,3 @@ -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} Enterprise owners can configure {% ifversion ghes %}the dependency graph and {% endif %}{% data variables.product.prodname_dependabot_alerts %} for an enterprise. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/dependency-review.md b/translations/pt-BR/data/reusables/gated-features/dependency-review.md index 94713cb4dd..6b668da450 100644 --- a/translations/pt-BR/data/reusables/gated-features/dependency-review.md +++ b/translations/pt-BR/data/reusables/gated-features/dependency-review.md @@ -7,7 +7,7 @@ Revisão de dependências está incluída em {% data variables.product.product_n {%- elsif ghes > 3.1 %} Dependency review is available for organization-owned repositories in {% data variables.product.product_name %}. This feature requires a license for {% data variables.product.prodname_GH_advanced_security %}. -{%- elsif ghae-issue-4864 %} +{%- elsif ghae %} Dependency review is available for organization-owned repositories in {% data variables.product.product_name %}. This is a {% data variables.product.prodname_GH_advanced_security %} feature (free during the beta release). -{%- endif %} {% data reusables.advanced-security.more-info-ghas %} \ No newline at end of file +{%- endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md index e02fca77a8..0e861ddb17 100644 --- a/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md +++ b/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} Você pode escolher o método de entrega e a frequência das notificações sobre {% data variables.product.prodname_dependabot_alerts %} em repositórios que você está inspecionando ou onde você se assinou notificações para alertas de segurança. {% endif %} diff --git a/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-options.md b/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-options.md index ed1fedfe8a..8edc13a2a4 100644 --- a/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-options.md +++ b/translations/pt-BR/data/reusables/notifications/vulnerable-dependency-notification-options.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} -{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes > 3.1 or ghae %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %} - por e-mail, um e-mail é enviado quando {% data variables.product.prodname_dependabot %} for habilitado para um repositório, quando for feito commit de um novo arquivo de manifesto para o repositório, e quando uma nova vulnerabilidade com uma gravidade crítica ou alta é encontrada (Opção **Enviar um e-mail cada vez que uma vulnerabilidade for encontrada** opção). - na interface do usuário, é exibido um aviso é nos arquivos e visualizações de código do seu repositório se houver quaisquer dependências vulneráveis (opção de **alertas de interface do usuário**). diff --git a/translations/pt-BR/data/reusables/organizations/security-overview-feature-specific-page.md b/translations/pt-BR/data/reusables/organizations/security-overview-feature-specific-page.md new file mode 100644 index 0000000000..c0d110d8f2 --- /dev/null +++ b/translations/pt-BR/data/reusables/organizations/security-overview-feature-specific-page.md @@ -0,0 +1 @@ +1. Como alternativa, use a barra lateral à esquerda para filtrar informações por recurso de segurança. On each page, you can use filters that are specific to that feature to fine-tune your search. diff --git a/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md b/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md index 157a6c8c73..bf2beb6d67 100644 --- a/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md +++ b/translations/pt-BR/data/reusables/organizations/team_maintainers_can.md @@ -10,6 +10,6 @@ Os membros com permissões de mantenedor da equipe podem: - [Adicionar integrantes da organização à equipe](/articles/adding-organization-members-to-a-team) - [Remover membros da organização da equipe](/articles/removing-organization-members-from-a-team) - [Promover um membro da equipe existente para um mantenedor de equipe](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member) -- Remover acesso da equipe aos repositórios{% ifversion fpt or ghes or ghae or ghec %} -- [Manage code review settings for the team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% endif %}{% ifversion fpt or ghec %} +- Remove the team's access to repositories +- [Manage code review settings for the team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% ifversion fpt or ghec %} - [Gerenciar lembretes agendados para pull requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/pt-BR/data/reusables/package_registry/container-registry-ghes-beta.md b/translations/pt-BR/data/reusables/package_registry/container-registry-ghes-beta.md index 2b53d28dab..921dbd7826 100644 --- a/translations/pt-BR/data/reusables/package_registry/container-registry-ghes-beta.md +++ b/translations/pt-BR/data/reusables/package_registry/container-registry-ghes-beta.md @@ -2,7 +2,7 @@ {% note %} -**Note**: {% data variables.product.prodname_container_registry %} is currently in beta for {% data variables.product.product_name %} and subject to change. +**Observação**: {% data variables.product.prodname_container_registry %} está atualmente em beta para {% data variables.product.product_name %} e sujeito a alterações. Both {% data variables.product.prodname_registry %} and subdomain isolation must be enabled to use {% data variables.product.prodname_container_registry %}. Para obter mais informações, consulte "[Trabalhando com o registro do contêiner](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." diff --git a/translations/pt-BR/data/reusables/pull_requests/close-issues-using-keywords.md b/translations/pt-BR/data/reusables/pull_requests/close-issues-using-keywords.md index b6d3070db6..f7ed5cf566 100644 --- a/translations/pt-BR/data/reusables/pull_requests/close-issues-using-keywords.md +++ b/translations/pt-BR/data/reusables/pull_requests/close-issues-using-keywords.md @@ -1 +1 @@ -You can 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. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)." +You can link a pull request to an issue to show that a fix is in progress and to automatically close the issue when someone merges the pull request. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)." diff --git a/translations/pt-BR/data/reusables/repositories/copy-clone-url.md b/translations/pt-BR/data/reusables/repositories/copy-clone-url.md index 642c7807b5..13c8e57d76 100644 --- a/translations/pt-BR/data/reusables/repositories/copy-clone-url.md +++ b/translations/pt-BR/data/reusables/repositories/copy-clone-url.md @@ -1,6 +1,6 @@ 1. Acima da lista de arquivos, clique em {% octicon "download" aria-label="The download icon" %} **código**. ![Botão de "Código"](/assets/images/help/repository/code-button.png) -1. Para clonar o repositório usando HTTPS, em "Clonar com HTTPS", clique em -{% octicon "clippy" aria-label="The clipboard icon" %}. To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **Use SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. To clone a repository using {% data variables.product.prodname_cli %}, click **Use {% data variables.product.prodname_cli %}**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. - ![O ícone da área de transferência para copiar a URL para clonar um repositório](/assets/images/help/repository/https-url-clone.png) - {% ifversion fpt or ghes or ghae or ghec %} - ![O ícone da área de transferência para copiar a URL para clonar um repositório com o CLI do GitHub](/assets/images/help/repository/https-url-clone-cli.png){% endif %} +1. Copy the URL for the repository. + + - To clone the repository using HTTPS, under "HTTPS", click {% octicon "clippy" aria-label="The clipboard icon" %}. + - Para clonar o repositório usando uma chave SSH, incluindo um certificado emitido pela autoridade de certificação SSH da sua organização, clique em **SSH** e, em seguida, clique em {% octicon "clippy" aria-label="The clipboard icon" %}. + - To clone a repository using {% data variables.product.prodname_cli %}, click **{% data variables.product.prodname_cli %}**, then click {% octicon "clippy" aria-label="The clipboard icon" %}. ![O ícone da área de transferência para copiar a URL para clonar um repositório com o CLI do GitHub](/assets/images/help/repository/https-url-clone-cli.png) diff --git a/translations/pt-BR/data/reusables/repositories/default-issue-templates.md b/translations/pt-BR/data/reusables/repositories/default-issue-templates.md index b058f24dcd..b254aa6a6c 100644 --- a/translations/pt-BR/data/reusables/repositories/default-issue-templates.md +++ b/translations/pt-BR/data/reusables/repositories/default-issue-templates.md @@ -1,2 +1 @@ -You can create default issue templates{% ifversion fpt or ghes or ghae or ghec %} and a default configuration file for issue templates{% endif %} for your organization{% ifversion fpt or ghes or ghae or ghec %} or personal account{% endif %}. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." - +You can create default issue templates and a default configuration file for issue templates for your organization or personal account. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." diff --git a/translations/pt-BR/data/reusables/repositories/dependency-review.md b/translations/pt-BR/data/reusables/repositories/dependency-review.md index c768c0b627..9212bebde7 100644 --- a/translations/pt-BR/data/reusables/repositories/dependency-review.md +++ b/translations/pt-BR/data/reusables/repositories/dependency-review.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} Além disso, {% data variables.product.prodname_dotcom %} pode revisar todas as dependências adicionadas, atualizadas ou removidas em um pull request feita para o branch padrão de um repositório e sinalizar quaisquer alterações que introduziriam uma vulnerabilidade no seu projeto. Isso permite que você detecte e gerencie as dependências vulneráveis antes, e não depois, de elas alcançarem seu código. Para obter mais informações, consulte "[Revisar as mudanças de dependências em um pull request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)". {% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/enable-security-alerts.md b/translations/pt-BR/data/reusables/repositories/enable-security-alerts.md index 8c258ad344..87bfd43242 100644 --- a/translations/pt-BR/data/reusables/repositories/enable-security-alerts.md +++ b/translations/pt-BR/data/reusables/repositories/enable-security-alerts.md @@ -1,4 +1,4 @@ -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} Enterprise owners must enable {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies for {% data variables.product.product_location %} before you can use this feature. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} diff --git a/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index eddee42d31..03f4a57505 100644 --- a/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% ifversion fpt or ghes or ghae or ghec %}If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)."{% endif %} +If there is a protected branch rule in your repository that requires a linear commit history, you must allow squash merging, rebase merging, or both. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)." diff --git a/translations/pt-BR/data/reusables/repositories/start-line-comment.md b/translations/pt-BR/data/reusables/repositories/start-line-comment.md index 4c84e653b4..2a4b35980e 100644 --- a/translations/pt-BR/data/reusables/repositories/start-line-comment.md +++ b/translations/pt-BR/data/reusables/repositories/start-line-comment.md @@ -1 +1 @@ -1. Passe o mouse sobre a linha de código em que você gostaria de adicionar um comentário e clique no ícone de comentário azul.{% ifversion fpt or ghes or ghae or ghec %} Para adicionar um comentário em várias linhas, clique e arraste para selecionar o intervalo de linhas e, em seguida, clique no ícone azul do comentário.{% endif %} ![Ícone de comentário azul](/assets/images/help/commits/hover-comment-icon.gif) +1. Hover over the line of code where you'd like to add a comment, and click the blue comment icon. To add a comment on multiple lines, click and drag to select the range of lines, then click the blue comment icon. ![Ícone de comentário azul](/assets/images/help/commits/hover-comment-icon.gif) diff --git a/translations/pt-BR/data/reusables/repositories/suggest-changes.md b/translations/pt-BR/data/reusables/repositories/suggest-changes.md index c9079f8ec0..00256f1309 100644 --- a/translations/pt-BR/data/reusables/repositories/suggest-changes.md +++ b/translations/pt-BR/data/reusables/repositories/suggest-changes.md @@ -1,2 +1,2 @@ -1. Optionally, to suggest a specific change to the line{% ifversion fpt or ghes or ghae or ghec %} or lines{% endif %}, click {% octicon "diff" aria-label="The diff symbol" %}, then edit the text within the suggestion block. +1. Optionally, to suggest a specific change to the line or lines, click {% octicon "diff" aria-label="The diff symbol" %}, then edit the text within the suggestion block. ![Suggestion block](/assets/images/help/pull_requests/suggestion-block.png) diff --git a/translations/pt-BR/data/reusables/secret-scanning/beta.md b/translations/pt-BR/data/reusables/secret-scanning/beta.md index 3d3c9fd759..9b38b26259 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/beta.md +++ b/translations/pt-BR/data/reusables/secret-scanning/beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-5752 %} +{% ifversion ghae %} diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md index 2de83ea642..0cbaa7a827 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -13,9 +13,9 @@ Adobe | Adobe JSON Web Token | adobe_jwt{% endif %} Alibaba Cloud | Alibaba Clou Amazon | Amazon OAuth Client ID | amazon_oauth_client_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Amazon | Amazon OAuth Client Secret | amazon_oauth_client_secret{% endif %} Amazon Web Services (AWS) | Amazon AWS Access Key ID | aws_access_key_id Amazon Web Services (AWS) | Amazon AWS Secret Access Key | aws_secret_access_key -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} Atlassian | Atlassian API Token | atlassian_api_token Atlassian | Atlassian JSON Web Token | atlassian_jwt @@ -27,7 +27,7 @@ Azure | Azure Active Directory Application Secret | azure_active_directory_appli Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key{% endif %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token Azure | Azure SAS Token | azure_sas_token Azure | Azure Service Management Certificate | azure_management_certificate {%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %} Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} Azure | Azure Storage Account Key | azure_storage_account_key -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Beamer | Beamer API Key | beamer_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key{% endif %} @@ -35,7 +35,7 @@ Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_k Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key{% endif %} Clojars | Clojars Deploy Token | clojars_deploy_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Contentful | Contentful Personal Access Token | contentful_personal_access_token{% endif %} Databricks | Databricks Access Token | databricks_access_token {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} DigitalOcean | DigitalOcean Personal Access Token | digitalocean_personal_access_token DigitalOcean | DigitalOcean OAuth Token | digitalocean_oauth_token DigitalOcean | DigitalOcean Refresh Token | digitalocean_refresh_token DigitalOcean | DigitalOcean System Token | digitalocean_system_token{% endif %} Discord | Discord Bot Token | discord_bot_token Doppler | Doppler Personal Token | doppler_personal_token Doppler | Doppler Service Token | doppler_service_token Doppler | Doppler CLI Token | doppler_cli_token Doppler | Doppler SCIM Token | doppler_scim_token @@ -55,7 +55,7 @@ Fastly | Fastly API Token | fastly_api_token{% endif %} Finicity | Finicity App Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key{% endif %} Frame.io | Frame.io JSON Web Token | frameio_jwt Frame.io| Frame.io Developer Token | frameio_developer_token -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} FullStory | FullStory API Key | fullstory_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %} @@ -67,13 +67,13 @@ GitHub | GitHub Refresh Token | github_refresh_token{% endif %} GitHub | GitHub App Installation Access Token | github_app_installation_access_token{% endif %} GitHub | GitHub SSH Private Key | github_ssh_private_key {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} GitLab | GitLab Access Token | gitlab_access_token{% endif %} GoCardless | GoCardless Live Access Token | gocardless_live_access_token GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %} Google | Google API Key | google_api_key Google | Google Cloud Private Key ID | google_cloud_private_key_id -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Google | Google OAuth Access Token | google_oauth_access_token{% endif %} @@ -93,9 +93,9 @@ Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %} Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} JD Cloud | JD Cloud Access Key | jd_cloud_access_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Linear | Linear API Key | linear_api_key{% endif %} @@ -115,13 +115,13 @@ Meta | Facebook Access Token | facebook_access_token{% endif %} Midtrans | Midtrans Production Server Key | midtrans_production_server_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Midtrans | Midtrans Sandbox Server Key | midtrans_sandbox_server_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic License Key | new_relic_license_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Notion | Notion Integration Token | notion_integration_token{% endif %} @@ -135,15 +135,15 @@ Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} OpenAI | OpenAI API Key | openai_api_key{% endif %} Palantir | Palantir JSON Web Token | palantir_jwt -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Plivo | Plivo Auth ID | plivo_auth_id{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Plivo | Plivo Auth Token | plivo_auth_token{% endif %} Postman | Postman API Key | postman_api_key Proctorio | Proctorio Consumer Key | proctorio_consumer_key Proctorio | Proctorio Linkage Key | proctorio_linkage_key Proctorio | Proctorio Registration Key | proctorio_registration_key Proctorio | Proctorio Secret Key | proctorio_secret_key Pulumi | Pulumi Access Token | pulumi_access_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} PyPI | PyPI API Token | pypi_api_token{% endif %} @@ -153,9 +153,9 @@ RubyGems | RubyGems API Key | rubygems_api_key{% endif %} Samsara | Samsara API 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 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Shippo | Shippo Live API Token | shippo_live_api_token{% endif %} diff --git a/translations/pt-BR/data/reusables/security-center/permissions.md b/translations/pt-BR/data/reusables/security-center/permissions.md new file mode 100644 index 0000000000..8bc67f83a0 --- /dev/null +++ b/translations/pt-BR/data/reusables/security-center/permissions.md @@ -0,0 +1 @@ +Organization owners and security managers can access the security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} and view their organization's repositories via the enterprise-level security overview. Enterprise owners can use the enterprise-level security overview to view all repositories in their enterprise's organizations{% endif %}. Os integrantes de uma equipe podem visualizar a visão geral de segurança dos repositórios para os quais a equipe tem privilégios de administrador. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/security/compliance-report-list.md b/translations/pt-BR/data/reusables/security/compliance-report-list.md index e1e9c19c57..db6b9af39f 100644 --- a/translations/pt-BR/data/reusables/security/compliance-report-list.md +++ b/translations/pt-BR/data/reusables/security/compliance-report-list.md @@ -1,4 +1,5 @@ - SOC 1, Tipo 2 - SOC 2, Tipo 2 - Cloud Security Alliance CAIQ self-assessment (CSA CAIQ) +- ISO/IEC 27001:2013 certification - {% data variables.product.prodname_dotcom_the_website %} Services Continuity and Incident Management Plan diff --git a/translations/pt-BR/data/reusables/ssh/key-type-support.md b/translations/pt-BR/data/reusables/ssh/key-type-support.md index 57b5241f88..05e444cc2b 100644 --- a/translations/pt-BR/data/reusables/ssh/key-type-support.md +++ b/translations/pt-BR/data/reusables/ssh/key-type-support.md @@ -1,3 +1,4 @@ +{% ifversion fpt or ghec %} {% note %} **Note:** {% data variables.product.company_short %} improved security by dropping older, insecure key types on March 15, 2022. @@ -7,3 +8,4 @@ As of that date, DSA keys (`ssh-dss`) are no longer supported. You cannot add ne RSA keys (`ssh-rsa`) with a `valid_after` before November 2, 2021 may continue to use any signature algorithm. RSA keys generated after that date must use a SHA-2 signature algorithm. Some older clients may need to be upgraded in order to use SHA-2 signatures. {% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/user-settings/removes-personal-access-tokens.md b/translations/pt-BR/data/reusables/user-settings/removes-personal-access-tokens.md index b11c0bbd8b..c6184d182d 100644 --- a/translations/pt-BR/data/reusables/user-settings/removes-personal-access-tokens.md +++ b/translations/pt-BR/data/reusables/user-settings/removes-personal-access-tokens.md @@ -1 +1 @@ -As a security precaution, {% data variables.product.company_short %} automatically removes personal access tokens that haven't been used in a year.{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} To provide additional security, we highly recommend adding an expiration to your personal access tokens.{% endif %} +As a security precaution, {% data variables.product.company_short %} automatically removes personal access tokens that haven't been used in a year.{% ifversion fpt or ghes > 3.1 or ghae or ghec %} To provide additional security, we highly recommend adding an expiration to your personal access tokens.{% endif %} diff --git a/translations/pt-BR/data/reusables/webhooks/check_run_properties.md b/translations/pt-BR/data/reusables/webhooks/check_run_properties.md index 95392ecdeb..1dc80f22d0 100644 --- a/translations/pt-BR/data/reusables/webhooks/check_run_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/check_run_properties.md @@ -1,12 +1,12 @@ -| Tecla | Tipo | Descrição | -| --------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser uma das ações a seguir:
  • `created` - Uma nova execução de verificação foi criada.
  • `completed` - O `status` da execução da verificação está `completed`.
  • `rerequested` - Alguém pediu para executar novamente sua verificação a partir da interface de usuário do pull request. Veja "[Sobre verificações de status](/articles/about-status-checks#checks)" para mais informações sobre a interface do usuário do GitHub. Ao receber uma ação `rerequested`, você deverá [criar uma nova execução de verificação](/rest/reference/checks#create-a-check-run). Apenas o {% data variables.product.prodname_github_app %} que alguém solicitar para repetir a verificação receberá a carga `rerequested`.
  • `requested_action` - Alguém solicitou novamente que se tome uma ação fornecida pelo seu aplicativo. Apenas o {% data variables.product.prodname_github_app %} para o qual alguém solicitou uma ação receberá a carga `requested_action`. Para saber mais sobre verificações executadas e ações solicitadas, consulte "[Execuções de verificação e ações solicitadas](/rest/reference/checks#check-runs-and-requested-actions)."
| -| `check_run` | `objeto` | O [check_run](/rest/reference/checks#get-a-check-run). | -| `check_run[status]` | `string` | O status atual da execução da verificação. Pode ser `queued`, `in_progress` ou `completed`. | -| `check_run[conclusion]` | `string` | O resultado da execução de verificação concluída. Pode ser `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% ifversion fpt or ghes or ghae or ghec %}`action_required` ou `stale`{% else %}ou `action_required`{% endif %}. Este valor será `null` até que a execução da verificação seja `completed`. | -| `check_run[name]` | `string` | O nome da execução da verificação. | -| `check_run[check_suite][id]` | `inteiro` | A identificação do conjunto de verificações do qual a execução de verificação faz parte. | -| `check_run[check_suite][pull_requests]` | `array` | Um array de pull requests que correspondem a este conjunto de verificações. A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
| -| `check_run[check_suite][deployment]` | `objeto` | A deployment to a repository environment. This will only be populated if the check run was created by a {% data variables.product.prodname_actions %} workflow job that references an environment. | -| `requested_action` | `objeto` | A ação solicitada pelo usuário. | -| `requested_action[identifier]` | `string` | A referência de integrador da ação solicitada pelo usuário. | +| Tecla | Tipo | Descrição | +| --------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `Ação` | `string` | A ação realizada. Pode ser uma das ações a seguir:
  • `created` - Uma nova execução de verificação foi criada.
  • `completed` - O `status` da execução da verificação está `completed`.
  • `rerequested` - Alguém pediu para executar novamente sua verificação a partir da interface de usuário do pull request. Veja "[Sobre verificações de status](/articles/about-status-checks#checks)" para mais informações sobre a interface do usuário do GitHub. Ao receber uma ação `rerequested`, você deverá [criar uma nova execução de verificação](/rest/reference/checks#create-a-check-run). Apenas o {% data variables.product.prodname_github_app %} que alguém solicitar para repetir a verificação receberá a carga `rerequested`.
  • `requested_action` - Alguém solicitou novamente que se tome uma ação fornecida pelo seu aplicativo. Apenas o {% data variables.product.prodname_github_app %} para o qual alguém solicitou uma ação receberá a carga `requested_action`. Para saber mais sobre verificações executadas e ações solicitadas, consulte "[Execuções de verificação e ações solicitadas](/rest/reference/checks#check-runs-and-requested-actions)."
| +| `check_run` | `objeto` | O [check_run](/rest/reference/checks#get-a-check-run). | +| `check_run[status]` | `string` | O status atual da execução da verificação. Pode ser `queued`, `in_progress` ou `completed`. | +| `check_run[conclusion]` | `string` | O resultado da execução de verificação concluída. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, `action_required` or `stale`. Este valor será `null` até que a execução da verificação seja `completed`. | +| `check_run[name]` | `string` | O nome da execução da verificação. | +| `check_run[check_suite][id]` | `inteiro` | A identificação do conjunto de verificações do qual a execução de verificação faz parte. | +| `check_run[check_suite][pull_requests]` | `array` | Um array de pull requests que correspondem a este conjunto de verificações. A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
| +| `check_run[check_suite][deployment]` | `objeto` | A deployment to a repository environment. This will only be populated if the check run was created by a {% data variables.product.prodname_actions %} workflow job that references an environment. | +| `requested_action` | `objeto` | A ação solicitada pelo usuário. | +| `requested_action[identifier]` | `string` | A referência de integrador da ação solicitada pelo usuário. | diff --git a/translations/pt-BR/data/reusables/webhooks/check_suite_properties.md b/translations/pt-BR/data/reusables/webhooks/check_suite_properties.md index 128b520791..ea51bcbea8 100644 --- a/translations/pt-BR/data/reusables/webhooks/check_suite_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/check_suite_properties.md @@ -1,10 +1,10 @@ -| Tecla | Tipo | Descrição | -| ---------------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada. Pode ser:
  • `completed` - Todas as verificações executadas em um conjunto de verificações foram concluídas.
  • `requested` - Ocorre quando o novo código é carregado para o repositório do aplicativo. Ao receber os eventos de ação `requested`, você deverá [criar uma nova execução de verificação](/rest/reference/checks#create-a-check-run).
  • `rerequested` - Ocorre quando alguém solicita uma nova execução de todo o conjunto de verificação da interface de usuário do pull request. Ao receber os eventos de ação `rerequested`, você deverá [criar uma nova execução de verificação](/rest/reference/checks#create-a-check-run). Veja "[Sobre verificações de status](/articles/about-status-checks#checks)" para mais informações sobre a interface do usuário do GitHub.
| -| `check_suite` | `objeto` | O [check_suite](/rest/reference/checks#suites). | -| `check_suite[head_branch]` | `string` | O nome do branch principal em que as alterações se encontram. | -| `check_suite[head_sha]` | `string` | A SHA do commit mais recente para este conjunto de verificações. | -| `check_suite[status]` | `string` | O status de resumo para todas as verificações que fazem parte do conjunto de verificações. Pode ser `requested`, `in_progress` ou `completed`. | -| `check_suite[conclusion]` | `string` | O resumo da conclusão para todas as verificações que fazem parte do conjunto de verificações. Pode ser `success`, `failure`, `neutral`, `cancelled`, `timed_out`, {% ifversion fpt or ghes or ghae or ghec %}`action_required` ou `stale`{% else %}ou `action_required`{% endif %}. Este valor será `null` até que a execução da verificação seja `completed`. | -| `check_suite[url]` | `string` | A URL que aponta para o recurso da API do conjunto de verificações. | -| `check_suite[pull_requests]` | `array` | Um array de pull requests que correspondem a este conjunto de verificações. A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
| +| Tecla | Tipo | Descrição | +| ---------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `Ação` | `string` | A ação realizada. Pode ser:
  • `completed` - Todas as verificações executadas em um conjunto de verificações foram concluídas.
  • `requested` - Ocorre quando o novo código é carregado para o repositório do aplicativo. Ao receber os eventos de ação `requested`, você deverá [criar uma nova execução de verificação](/rest/reference/checks#create-a-check-run).
  • `rerequested` - Ocorre quando alguém solicita uma nova execução de todo o conjunto de verificação da interface de usuário do pull request. Ao receber os eventos de ação `rerequested`, você deverá [criar uma nova execução de verificação](/rest/reference/checks#create-a-check-run). Veja "[Sobre verificações de status](/articles/about-status-checks#checks)" para mais informações sobre a interface do usuário do GitHub.
| +| `check_suite` | `objeto` | O [check_suite](/rest/reference/checks#suites). | +| `check_suite[head_branch]` | `string` | O nome do branch principal em que as alterações se encontram. | +| `check_suite[head_sha]` | `string` | A SHA do commit mais recente para este conjunto de verificações. | +| `check_suite[status]` | `string` | O status de resumo para todas as verificações que fazem parte do conjunto de verificações. Pode ser `requested`, `in_progress` ou `completed`. | +| `check_suite[conclusion]` | `string` | O resumo da conclusão para todas as verificações que fazem parte do conjunto de verificações. Can be one of `success`, `failure`, `neutral`, `cancelled`, `timed_out`, `action_required` or `stale`. Este valor será `null` até que a execução da verificação seja `completed`. | +| `check_suite[url]` | `string` | A URL que aponta para o recurso da API do conjunto de verificações. | +| `check_suite[pull_requests]` | `array` | Um array de pull requests que correspondem a este conjunto de verificações. A pull request matches a check suite if they have the same `head_branch`.

**Note:**
  • The `head_sha` of the check suite can differ from the `sha` of the pull request if subsequent pushes are made into the PR.
  • When the check suite's `head_branch` is in a forked repository it will be `null` and the `pull_requests` array will be empty.
| diff --git a/translations/pt-BR/data/reusables/webhooks/installation_properties.md b/translations/pt-BR/data/reusables/webhooks/installation_properties.md index 8ffee2cec4..1b45bece11 100644 --- a/translations/pt-BR/data/reusables/webhooks/installation_properties.md +++ b/translations/pt-BR/data/reusables/webhooks/installation_properties.md @@ -1,4 +1,4 @@ | Tecla | Tipo | Descrição | | -------------- | -------- | ----------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação que foi executada. Pode ser uma das ações a seguir:
  • `created` - Alguém instala um {% data variables.product.prodname_github_app %}.
  • `deleted` - Alguém desinstala {% data variables.product.prodname_github_app %}
    • {% ifversion fpt or ghes or ghae or ghec %}
  • `suspend` - Alguém suspende uma instalação de {% data variables.product.prodname_github_app %}.
  • `unsuspend` - Alguém não suspende uma instalação de {% data variables.product.prodname_github_app %}.
    • {% endif %}
  • `new_permissions_accepted` - Alguém aceita novas permissões para uma instalação de {% data variables.product.prodname_github_app %}. Quando um proprietário de {% data variables.product.prodname_github_app %} solicita novas permissões, a pessoa que instalou o {% data variables.product.prodname_github_app %} deve aceitar a nova solicitação de permissões.
| +| `Ação` | `string` | A ação que foi executada. Pode ser uma das ações a seguir:
  • `created` - Alguém instala um {% data variables.product.prodname_github_app %}.
  • `deleted` - Alguém desinstala {% data variables.product.prodname_github_app %}
  • `suspend` - Alguém suspende uma instalação de {% data variables.product.prodname_github_app %}.
  • `unsuspend` - Alguém não suspende uma instalação de {% data variables.product.prodname_github_app %}.
  • `new_permissions_accepted` - Alguém aceita novas permissões para uma instalação de {% data variables.product.prodname_github_app %}. Quando um proprietário de {% data variables.product.prodname_github_app %} solicita novas permissões, a pessoa que instalou o {% data variables.product.prodname_github_app %} deve aceitar a nova solicitação de permissões.
| | `repositories` | `array` | Uma matriz de objetos do repositório que a instalação pode acessar. | diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml index 16b56fedec..a6b43126d8 100644 --- a/translations/pt-BR/data/variables/product.yml +++ b/translations/pt-BR/data/variables/product.yml @@ -140,10 +140,14 @@ prodname_advisory_database: 'Banco de Dados Consultivo GitHub' prodname_codeql_workflow: 'Fluxo de trabalho de análise do CodeQL' #Visual Studio prodname_vs: 'Visual Studio' +prodname_vscode_shortname: 'VS Code' prodname_vscode: 'Visual Studio Code' prodname_vss_ghe: 'Visual Studio subscriptions with GitHub Enterprise' prodname_vss_admin_portal_with_url: '[portal de administrador para assinaturas do Visual Studio](https://visualstudio.microsoft.com/subscriptions-administration/)' -prodname_vscode_command_palette: 'Paleta de Comando do VS Code' +prodname_vscode_command_palette_shortname: 'Paleta de Comando do VS Code' +prodname_vscode_command_palette: 'Visual Studio Code Command Palette' +prodname_vscode_marketplace: 'Visual Studio Code Marketplace' +prodname_vs_marketplace_shortname: 'VS Code Marketplace' #GitHub Dependabot prodname_dependabot: 'Dependabot' prodname_dependabot_alerts: 'Alertas do Dependabot' diff --git a/translations/zh-CN/content/account-and-profile/index.md b/translations/zh-CN/content/account-and-profile/index.md index 2c63ecf2ea..df425fc73e 100644 --- a/translations/zh-CN/content/account-and-profile/index.md +++ b/translations/zh-CN/content/account-and-profile/index.md @@ -37,7 +37,7 @@ topics: - Profiles - Notifications children: - - /setting-up-and-managing-your-github-user-account + - /setting-up-and-managing-your-personal-account-on-github - /setting-up-and-managing-your-github-profile - /managing-subscriptions-and-notifications-on-github --- diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md index 8bf7e159fe..9f48a72b7c 100644 --- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md +++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md @@ -129,8 +129,8 @@ Email notifications from {% data variables.product.product_location %} contain t | --- | --- | | `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. | | `To` field | This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} | -| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
  • `assign`: You were assigned to an issue or pull request.
  • `author`: You created an issue or pull request.
  • `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
  • `comment`: You commented on an issue or pull request.
  • `manual`: There was an update to an issue or pull request you manually subscribed to.
  • `mention`: You were mentioned on an issue or pull request.
  • `push`: Someone committed to a pull request you're subscribed to.
  • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • {% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
    • {% endif %}
  • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
  • `subscribed`: There was an update in a repository you're watching.
  • `team_mention`: A team you belong to was mentioned on an issue or pull request.
  • `your_activity`: You opened, commented on, or closed an issue or pull request.
| -| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
  • `assign`: You were assigned to an issue or pull request.
  • `author`: You created an issue or pull request.
  • `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
  • `comment`: You commented on an issue or pull request.
  • `manual`: There was an update to an issue or pull request you manually subscribed to.
  • `mention`: You were mentioned on an issue or pull request.
  • `push`: Someone committed to a pull request you're subscribed to.
  • `review_requested`: You or a team you're a member of was requested to review a pull request.
    • {% ifversion fpt or ghes or ghae or ghec %}
  • `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
    • {% endif %}
  • `state_change`: An issue or pull request you're subscribed to was either closed or opened.
  • `subscribed`: There was an update in a repository you're watching.
  • `team_mention`: A team you belong to was mentioned on an issue or pull request.
  • `your_activity`: You opened, commented on, or closed an issue or pull request.
| +| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae or ghec %} | `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:
  • `low`
  • `moderate`
  • `high`
  • `critical`
For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %} ## Choosing your notification settings @@ -139,7 +139,7 @@ Email notifications from {% data variables.product.product_location %} contain t {% data reusables.notifications-v2.manage-notifications %} 3. On the notifications settings page, choose how you receive notifications when: - There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)." - - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} + - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae or ghec %} - There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% endif %} {% ifversion fpt or ghec %} - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5668 %} - There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."{% endif %} @@ -194,7 +194,7 @@ If you are a member of more than one organization, you can configure each one to 5. Select one of your verified email addresses, then click **Save**. ![Switching your per-org email address](/assets/images/help/notifications/notifications_switching_org_email.gif) -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## {% data variables.product.prodname_dependabot_alerts %} notification options {% data reusables.notifications.vulnerable-dependency-notification-enable %} diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md index 5676a74682..33dc8379c6 100644 --- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md +++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md @@ -112,13 +112,13 @@ shortTitle: 从收件箱管理 - `is:gist` - `is:issue-or-pull-request` - `is:release` -- `is:repository-invitation`{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +- `is:repository-invitation`{% ifversion fpt or ghes or ghae or ghec %} - `is:repository-vulnerability-alert`{% endif %}{% ifversion fpt or ghec %} - `is:repository-advisory`{% endif %} - `is:team-discussion`{% ifversion fpt or ghec %} - `is:discussion`{% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} 有关减少 {% data variables.product.prodname_dependabot_alerts %} 通知干扰的信息，请参阅“[配置漏洞依赖项的通知](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)”。 {% endif %} @@ -133,20 +133,20 @@ shortTitle: 从收件箱管理 要根据收到更新的原因过滤通知，您可以使用 `reason:` 查询。 例如，要查看当您（或您所属团队）被请求审查拉取请求时的通知，请使用 `reason:review-requested`。 更多信息请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)”。 -| 查询 | 描述 | -| ------------------------- | ------------------------------------------------------------------------ | -| `reason:assign` | 分配给您的议题或拉取请求有更新时。 | -| `reason:author` | 当您打开拉取请求或议题并且有更新或新评论时。 | -| `reason:comment` | 当您评论了议题、拉取请求或团队讨论时。 | -| `reason:participating` | 当您评论了议题、拉取请求或团队讨论或者被@提及时。 | -| `reason:invitation` | 当您被邀请加入团队、组织或仓库时。 | -| `reason:manual` | 当您在尚未订阅的议题或拉取请求上单击 **Subscribe（订阅）**时。 | -| `reason:mention` | 您被直接@提及。 | -| `reason:review-requested` | 您或您所属的团队被请求审查拉取请求。{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| 查询 | 描述 | +| ------------------------- | ------------------------------------------------------------- | +| `reason:assign` | 分配给您的议题或拉取请求有更新时。 | +| `reason:author` | 当您打开拉取请求或议题并且有更新或新评论时。 | +| `reason:comment` | 当您评论了议题、拉取请求或团队讨论时。 | +| `reason:participating` | 当您评论了议题、拉取请求或团队讨论或者被@提及时。 | +| `reason:invitation` | 当您被邀请加入团队、组织或仓库时。 | +| `reason:manual` | 当您在尚未订阅的议题或拉取请求上单击 **Subscribe（订阅）**时。 | +| `reason:mention` | 您被直接@提及。 | +| `reason:review-requested` | 您或您所属的团队被请求审查拉取请求。{% ifversion fpt or ghes or ghae or ghec %} | `reason:security-alert` | 为仓库发出安全警报时。{% endif %} -| `reason:state-change` | 当拉取请求或议题的状态改变时。 例如，议题已关闭或拉取请求合并时。 | -| `reason:team-mention` | 您所在的团队被@提及时。 | -| `reason:ci-activity` | 当仓库有 CI 更新时，例如新的工作流程运行状态。 | +| `reason:state-change` | 当拉取请求或议题的状态改变时。 例如，议题已关闭或拉取请求合并时。 | +| `reason:team-mention` | 您所在的团队被@提及时。 | +| `reason:ci-activity` | 当仓库有 CI 更新时，例如新的工作流程运行状态。 | {% ifversion fpt or ghec %} ### 支持的 `author:` 查询 @@ -161,7 +161,7 @@ shortTitle: 从收件箱管理 {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## {% data variables.product.prodname_dependabot %} 自定义过滤器 {% ifversion fpt or ghec or ghes > 3.2 %} @@ -173,7 +173,7 @@ shortTitle: 从收件箱管理 有关 {% data variables.product.prodname_dependabot %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。 {% endif %} -{% ifversion ghes < 3.3 or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae %} 如果使用 {% data variables.product.prodname_dependabot %} 来告知易受攻击的依赖项，则可以使用并保存这些自定义筛选器来显示 {% data variables.product.prodname_dependabot_alerts %} 的通知： - `is:repository_vulnerability_alert` diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md index 78f74ca3f7..c00c16fcab 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md @@ -91,10 +91,7 @@ The contribution activity section includes a detailed timeline of your work, inc ![Contribution activity time filter](/assets/images/help/profile/contributions_activity_time_filter.png) -{% ifversion fpt or ghes or ghae or ghec %} - ## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %} If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and your enterprise owner enables {% data variables.product.prodname_unified_contributions %}, you can send enterprise contribution counts from to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)." -{% endif %} diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md similarity index 50% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md index ab8c2960a2..bbf2fae874 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md @@ -1,10 +1,11 @@ --- -title: 设置和管理 GitHub 用户帐户 -intro: 您可以管理 GitHub 个人帐户中的设置，包括电子邮件首选项、个人仓库的协作者权限以及组织成员身份。 +title: Setting up and managing your personal account on GitHub +intro: 'You can manage settings for your personal account on {% data variables.product.prodname_dotcom %}, including email preferences, collaborator access for personal repositories, and organization memberships.' shortTitle: 个人帐户 redirect_from: - /categories/setting-up-and-managing-your-github-user-account - /github/setting-up-and-managing-your-github-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account versions: fpt: '*' ghes: '*' @@ -13,7 +14,7 @@ versions: topics: - Accounts children: - - /managing-user-account-settings + - /managing-personal-account-settings - /managing-email-preferences - /managing-access-to-your-personal-repositories - /managing-your-membership-in-organizations diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md similarity index 79% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md index c0817d75d6..f72d99b22e 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md @@ -6,6 +6,7 @@ redirect_from: - /categories/managing-repository-collaborators - /articles/managing-access-to-your-personal-repositories - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' @@ -19,7 +20,7 @@ children: - /inviting-collaborators-to-a-personal-repository - /removing-a-collaborator-from-a-personal-repository - /removing-yourself-from-a-collaborators-repository - - /maintaining-ownership-continuity-of-your-user-accounts-repositories + - /maintaining-ownership-continuity-of-your-personal-accounts-repositories shortTitle: 访问仓库 --- 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-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md similarity index 95% rename from 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 rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index daec0aa952..192cd6c2bf 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-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md @@ -7,6 +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 + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md similarity index 88% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md index 3aad87b5f5..68632f686b 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md @@ -1,5 +1,5 @@ --- -title: 保持用户帐户仓库的所有权连续性 +title: Maintaining ownership continuity of your personal account's repositories intro: 如果您无法管理用户拥有的仓库，可以邀请他人管理。 versions: fpt: '*' @@ -10,6 +10,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories shortTitle: 所有权连续性 --- 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md similarity index 93% rename from 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 rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md index 7587fc0c4d..17b58af33a 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md @@ -10,6 +10,7 @@ redirect_from: - /articles/removing-a-collaborator-from-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository product: '{% data reusables.gated-features.user-repo-collaborators %}' versions: fpt: '*' 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md similarity index 90% rename from 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 rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md index 5acf5c9e69..6590eee2df 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-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md @@ -9,6 +9,7 @@ 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 + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md similarity index 91% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md index 8bb3b72ffd..2237cc1aef 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md @@ -5,6 +5,7 @@ redirect_from: - /articles/adding-an-email-address-to-your-github-account - /github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md similarity index 91% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md index 5769b9644f..a7e1807619 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/blocking-command-line-pushes-that-expose-your-personal-email-address - /github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address versions: fpt: '*' ghec: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md similarity index 93% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md index 5998b2873b..97c6d80945 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/changing-your-primary-email-address - /github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md similarity index 91% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md index 0e5451c1d2..4c75488847 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md @@ -5,6 +5,7 @@ redirect_from: - /categories/managing-email-preferences - /articles/managing-email-preferences - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md similarity index 92% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md index 88a6bd8426..7e7f9590d7 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md @@ -5,6 +5,7 @@ redirect_from: - /articles/managing-marketing-emails-from-github - /github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github versions: fpt: '*' ghec: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md similarity index 95% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md index 0391ee54d9..cb055e2355 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md @@ -7,6 +7,7 @@ redirect_from: - /articles/remembering-your-github-username-or-email - /github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md similarity index 90% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md index 152ac6cb46..3812065a55 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md @@ -5,6 +5,7 @@ redirect_from: - /articles/setting-a-backup-email-address - /github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md similarity index 98% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md index bd0009257f..7bf97193d7 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md @@ -12,6 +12,7 @@ redirect_from: - /articles/setting-your-commit-email-address - /github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md similarity index 95% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md index a2bf93f059..aaed3d9cd3 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md @@ -5,6 +5,7 @@ redirect_from: - /articles/types-of-emails-github-sends - /github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends versions: fpt: '*' ghec: '*' diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md similarity index 97% rename from content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md index c0c7c3bb13..d1cde5e951 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md @@ -6,6 +6,7 @@ redirect_from: - /articles/about-your-personal-dashboard - /github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard intro: 'You can visit your personal dashboard to keep track of issues and pull requests you''re working on or following, navigate to your top repositories and team pages, stay updated on recent activities in organizations and repositories you''re subscribed to, and explore recommended repositories.' versions: fpt: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md similarity index 94% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md index c4eaa60b01..18516601b8 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md @@ -5,6 +5,7 @@ redirect_from: - /articles/best-practices-for-leaving-your-company - /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company versions: fpt: '*' ghec: '*' diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md similarity index 98% rename from translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md index 4913ddd731..84367ad293 100644 --- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md @@ -9,6 +9,7 @@ redirect_from: - /articles/changing-your-github-username - /github/setting-up-and-managing-your-github-user-account/changing-your-github-username - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md similarity index 93% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md index c4a9dd2f69..a3e3b98311 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md @@ -6,6 +6,7 @@ redirect_from: - /articles/converting-a-user-into-an-organization - /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization intro: 您可以将个人帐户转换为组织。 这样可以对属于组织的仓库设置更细化的权限。 versions: fpt: '*' @@ -48,7 +49,7 @@ shortTitle: 用户到组织 2. [离开](/articles/removing-yourself-from-an-organization)要转换的个人帐户此前加入的任何组织。 {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.organizations %} -5. 在“Transform account（转换帐户）”下，单击 **Turn into an organization（将 转换为组织）**。 ![组织转换按钮](/assets/images/help/settings/convert-to-organization.png) +5. Under "Transform account", click **Turn into an organization**. ![组织转换按钮](/assets/images/help/settings/convert-to-organization.png) 6. 在 Account Transformation Warning（帐户转换警告）对话框中，查看并确认转换。 请注意，此框中的信息与本文顶部的警告信息相同。 ![转换警告](/assets/images/help/organizations/organization-account-transformation-warning.png) 7. 在“Transform your user into an organization（将用户转换为组织）”页面的“Choose an organization owner（选择组织所有者）”下，选择您在前面创建的备用个人帐户或您信任的其他用户来管理组织。 ![添加组织所有者页面](/assets/images/help/organizations/organization-add-owner.png) 8. 选择新组织的订阅，并在提示时输入帐单信息。 diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md similarity index 95% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md index 7f928be6b9..bf19520149 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md @@ -1,11 +1,12 @@ --- -title: 删除用户帐户 +title: Deleting your personal account intro: '您可以随时在 {% data variables.product.product_name %} 上删除您的个人帐户。' redirect_from: - /articles/deleting-a-user-account - /articles/deleting-your-user-account - /github/setting-up-and-managing-your-github-user-account/deleting-your-user-account - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md similarity index 67% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md index f0ba726a84..44e94058a5 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md @@ -6,6 +6,7 @@ redirect_from: - /categories/user-accounts - /articles/managing-user-account-settings - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings versions: fpt: '*' ghes: '*' @@ -18,15 +19,15 @@ children: - /managing-your-theme-settings - /managing-your-tab-size-rendering-preference - /changing-your-github-username - - /merging-multiple-user-accounts + - /merging-multiple-personal-accounts - /converting-a-user-into-an-organization - - /deleting-your-user-account - - /permission-levels-for-a-user-account-repository - - /permission-levels-for-user-owned-project-boards + - /deleting-your-personal-account + - /permission-levels-for-a-personal-account-repository + - /permission-levels-for-a-project-board-owned-by-a-personal-account - /managing-accessibility-settings - /managing-the-default-branch-name-for-your-repositories - - /managing-security-and-analysis-settings-for-your-user-account - - /managing-access-to-your-user-accounts-project-boards + - /managing-security-and-analysis-settings-for-your-personal-account + - /managing-access-to-your-personal-accounts-project-boards - /integrating-jira-with-your-personal-projects - /best-practices-for-leaving-your-company - /what-does-the-available-for-hire-checkbox-do 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-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md similarity index 92% rename from 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 rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md index e85c3dc457..5fce80e2e7 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-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md @@ -5,6 +5,7 @@ redirect_from: - /articles/integrating-jira-with-your-personal-projects - /github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects versions: ghes: '*' ghae: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md similarity index 90% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md index f16693eb8d..b5cb52a5bd 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md @@ -1,5 +1,5 @@ --- -title: 管理对用户帐户项目板的访问 +title: Managing access to your personal account's project boards intro: 作为项目板所有者，您可以添加或删除协作者，以及自定义他们对项目板的权限。 redirect_from: - /articles/managing-project-boards-in-your-repository-or-organization @@ -7,6 +7,7 @@ redirect_from: - /articles/managing-access-to-your-user-accounts-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md similarity index 89% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md index 6c343072fe..0296abe293 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md @@ -3,6 +3,8 @@ title: 管理辅助功能设置 intro: '您可以在 {% data variables.product.prodname_dotcom %} 上的辅助功能设置中禁用字符键快捷方式。' versions: feature: keyboard-shortcut-accessibility-setting +redirect_from: + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings --- ## 关于辅助功能设置 diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md similarity index 94% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md index 49aefd4136..59cc8362e9 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md @@ -1,5 +1,5 @@ --- -title: 管理用户帐户的安全和分析设置 +title: Managing security and analysis settings for your personal account intro: '您可以控制功能以保护 {% data variables.product.prodname_dotcom %} 上项目的安全并分析其中的代码。' versions: fpt: '*' @@ -10,6 +10,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account shortTitle: 管理安全和分析 --- diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md similarity index 100% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md 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-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md similarity index 82% rename from 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 rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md index c6f0f0b929..302e80da1d 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-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md @@ -9,6 +9,8 @@ versions: topics: - Accounts shortTitle: 管理选项卡大小 +redirect_from: + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference --- 如果您觉得在 {% data variables.product.product_name %} 上呈现的选项卡式代码缩进占用了太多或太少的空间，可以在设置中更改。 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-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md similarity index 67% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md index c13660b9d2..b04497a29f 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-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md @@ -11,6 +11,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings shortTitle: 管理主题设置 --- @@ -18,7 +19,7 @@ shortTitle: 管理主题设置 您可能需要使用深色主题来减少某些设备的功耗，以在低光条件下减小眼睛的压力，或者因为您更喜欢主题的外观。 -{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}如果您视力不佳，则可以从前景和背景元素之间对比度更高的高对比度主题中受益。{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} 如果您有色盲，可能会从我们的浅色盲和深色盲主题中受益。 +{% ifversion fpt or ghes > 3.2 or ghae or ghec %}如果您视力不佳，则可以从前景和背景元素之间对比度更高的高对比度主题中受益。{% endif %}{% ifversion fpt or ghae or ghec %} 如果您有色盲，可能会从我们的浅色盲和深色盲主题中受益。 {% endif %} @@ -31,10 +32,10 @@ shortTitle: 管理主题设置 1. 单击想要使用的主题。 - 如果您选择单个主题，请单击一个主题。 - {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} + {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %} - 如果您选择遵循系统设置，请单击白天主题和夜间主题。 - {% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} + {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} {% ifversion fpt or ghec %} - 如果您想选择当前处于公开测试阶段的主题，则首先需要通过功能预览启用它。 更多信息请参阅“[通过功能预览了解早期访问版本](/get-started/using-github/exploring-early-access-releases-with-feature-preview)”。{% endif %} diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md similarity index 87% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md index fe3d000bbc..571041d9dd 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md @@ -1,5 +1,5 @@ --- -title: 合并多个用户帐户 +title: Merging multiple personal accounts intro: 如果工作和个人分别使用不同的帐户，您可以合并这些帐户。 redirect_from: - /articles/can-i-merge-two-accounts @@ -7,6 +7,7 @@ redirect_from: - /articles/merging-multiple-user-accounts - /github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts versions: fpt: '*' ghec: '*' @@ -39,7 +40,7 @@ shortTitle: 合并多个个人帐户 1. 从您要删除的帐户[转让任何仓库](/articles/how-to-transfer-a-repository)到要保留的帐户。 议题、拉取请求和 wiki 也会转让。 确认要保留的帐户中存在仓库。 2. [更新远程 URL](/github/getting-started-with-github/managing-remote-repositories)（在移动的仓库的任何本地克隆中）。 -3. [删除帐户](/articles/deleting-your-user-account)（不再使用的）。 +3. [删除帐户](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account)（不再使用的）。 4. 要将过去的提交归因于新帐户，请将用于创作提交的电子邮件地址添加到要保留的帐户。 更多信息请参阅“[为什么我的贡献没有在我的个人资料中显示？](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)” ## 延伸阅读 diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md similarity index 98% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md index 2621e434e8..f4fb4b3f8b 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md @@ -1,10 +1,11 @@ --- -title: 用户帐户仓库的权限级别 +title: Permission levels for a personal account repository intro: 个人帐户拥有的仓库有两种权限级别：仓库所有者和协作者。 redirect_from: - /articles/permission-levels-for-a-user-account-repository - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository versions: fpt: '*' ghes: '*' @@ -12,7 +13,7 @@ versions: ghec: '*' topics: - Accounts -shortTitle: 权限用户仓库 +shortTitle: 仓库权限 --- ## 关于个人帐户仓库的权限级别 @@ -47,7 +48,7 @@ shortTitle: 权限用户仓库 | 删除和恢复包 | “[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)” {% endif %} | 自定义仓库的社交媒体预览 | "[自定义仓库的社交媒体预览](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | -| 从仓库创建模板 | "[创建模板仓库](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| 从仓库创建模板 | "[创建模板仓库](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae or ghec %} | 控制对易受攻击依赖项的 {% data variables.product.prodname_dependabot_alerts %} 访问 | "[管理仓库的安全和分析设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %} | 忽略仓库中的 {% data variables.product.prodname_dependabot_alerts %} | "[查看漏洞依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | | 管理私有仓库的数据使用 | “[管理私有仓库的数据使用设置](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)” diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md similarity index 90% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md index 4041f25d79..e4d9281708 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md @@ -1,10 +1,11 @@ --- -title: 用户拥有的项目板的权限级别 +title: Permission levels for a project board owned by a personal account intro: 个人帐户拥有的项目板有两种权限级别：项目板所有者和协作者。 redirect_from: - /articles/permission-levels-for-user-owned-project-boards - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards versions: fpt: '*' ghes: '*' @@ -12,7 +13,7 @@ versions: ghec: '*' topics: - Accounts -shortTitle: 权限用户项目板 +shortTitle: 项目板权限 --- ## 权限概述 diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md similarity index 90% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md index 381bc57228..d6dc812228 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md @@ -5,6 +5,7 @@ redirect_from: - /articles/what-does-the-available-for-hire-checkbox-do - /github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do versions: fpt: '*' ghec: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md similarity index 95% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md index e4db7678d8..5856d842dc 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md @@ -5,6 +5,7 @@ redirect_from: - /articles/about-organization-membership - /github/setting-up-and-managing-your-github-user-account/about-organization-membership - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md similarity index 85% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md index 9ab1e6940b..d57cf1b92c 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md @@ -8,6 +8,7 @@ redirect_from: - /articles/accessing-an-organization - /github/setting-up-and-managing-your-github-user-account/accessing-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md similarity index 87% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md index 612d76981a..50177970ad 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md @@ -4,6 +4,7 @@ intro: 如果您是组织的成员，便可公开或隐藏您的成员资格， redirect_from: - /articles/managing-your-membership-in-organizations - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations versions: fpt: '*' ghes: '*' 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-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md similarity index 96% rename from 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 rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md index db484a3715..73b015b049 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-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md @@ -9,6 +9,7 @@ topics: redirect_from: - /github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders shortTitle: 管理预定提醒 --- diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md similarity index 89% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md index 1bacec097a..932483709c 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md @@ -6,6 +6,7 @@ redirect_from: - /articles/publicizing-or-hiding-organization-membership - /github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md similarity index 90% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md index 2b1783c6a9..cf4eb9c918 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md @@ -6,6 +6,7 @@ redirect_from: - /articles/removing-yourself-from-an-organization - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md similarity index 92% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md index e540196eb6..174ecd5702 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md @@ -7,6 +7,7 @@ redirect_from: - /articles/requesting-organization-approval-for-oauth-apps - /github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps versions: fpt: '*' ghec: '*' diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md similarity index 96% rename from translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md rename to translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md index 33e9bb501b..14454173b7 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md @@ -7,6 +7,7 @@ redirect_from: - /articles/viewing-peoples-roles-in-an-organization - /github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization + - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization versions: fpt: '*' ghes: '*' diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md deleted file mode 100644 index f2e2f5924c..0000000000 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -title: 构建并测试 Node.js 或 Python -shortTitle: 构建和测试 Node.js 或 Python -intro: 您可以创建持续集成 (CI) 工作流程来构建和测试您的项目。 使用语言选择器显示所选语言的示例。 -redirect_from: - - /actions/guides/building-and-testing-nodejs-or-python -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: tutorial -topics: - - CI ---- - - - diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index 63a2c560a0..3128960474 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -11,13 +11,11 @@ versions: ghae: '*' ghec: '*' type: tutorial -hidden: true topics: - CI - Node - JavaScript shortTitle: 构建和测试 Node.js -hasExperimentalAlternative: true --- {% data reusables.actions.enterprise-beta %} diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md index bb2a754a7b..4718018caa 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -11,12 +11,10 @@ versions: ghae: '*' ghec: '*' type: tutorial -hidden: true topics: - CI - Python shortTitle: 构建和测试 Python -hasExperimentalAlternative: true --- {% data reusables.actions.enterprise-beta %} @@ -246,7 +244,7 @@ steps: - run: pip test ``` -默认情况下， `setup-python` 操作会在整个存储库中搜索依赖项文件（对于 pip 为`requirements.txt`，对于 pipenv 为 `Pipfile.lock`）。 更多信息请参阅 `setup-python` 自述文件中的“[缓存包依赖项](https://github.com/actions/setup-python#caching-packages-dependencies)”。 +By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip, `Pipfile.lock` for pipenv or `poetry.lock` for poetry) in the whole repository. 更多信息请参阅 `setup-python` 自述文件中的“[缓存包依赖项](https://github.com/actions/setup-python#caching-packages-dependencies)”。 如果您有自定义要求或需要更精确的缓存控制，则可以使用 [`cache` 操作](https://github.com/marketplace/actions/cache)。 Pip 根据运行器的操作系统将依赖项缓存在不同的位置。 您需要缓存的路径可能不同于上面的 Ubuntu 示例，具体取决于您使用的操作系统。 更多信息请参阅 `cache` 操作存储库中的 [Python 缓存示例](https://github.com/actions/cache/blob/main/examples.md#python---pip)。 diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/index.md b/translations/zh-CN/content/actions/automating-builds-and-tests/index.md index 5786c97d85..edfc6f6c84 100644 --- a/translations/zh-CN/content/actions/automating-builds-and-tests/index.md +++ b/translations/zh-CN/content/actions/automating-builds-and-tests/index.md @@ -14,13 +14,14 @@ redirect_from: - /actions/language-and-framework-guides/github-actions-for-java - /actions/language-and-framework-guides/github-actions-for-javascript-and-typescript - /actions/language-and-framework-guides/github-actions-for-python + - /actions/guides/building-and-testing-nodejs-or-python + - /actions/automating-builds-and-tests/building-and-testing-nodejs-or-python children: - /about-continuous-integration - /building-and-testing-java-with-ant - /building-and-testing-java-with-gradle - /building-and-testing-java-with-maven - /building-and-testing-net - - /building-and-testing-nodejs-or-python - /building-and-testing-nodejs - /building-and-testing-powershell - /building-and-testing-python 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 7f1f1f5b95..f2647ba73b 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 @@ -273,7 +273,7 @@ runs: ### `runs.steps` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **必要** 您计划在此操作中的步骤。 这些步骤可以是 `run` 步骤或 `uses` 步骤。 @@ -288,7 +288,7 @@ runs: #### `runs.steps[*].run` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **可选** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本： @@ -332,7 +332,7 @@ runs: #### `runs.steps[*].shell` -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **可选** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。 @@ -407,7 +407,7 @@ steps: **可选** 指定命令在其中运行的工作目录。 -{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} #### `runs.steps[*].uses` diff --git a/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md index f84c550826..fee9575372 100644 --- a/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md +++ b/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md @@ -1,6 +1,6 @@ --- -title: Deploying with GitHub Actions -intro: Learn how to control deployments with features like environments and concurrency. +title: 使用 GitHub Actions 进行部署 +intro: 了解如何使用环境和并发性等功能控制部署。 versions: fpt: '*' ghes: '*' @@ -11,35 +11,35 @@ redirect_from: - /actions/deployment/deploying-with-github-actions topics: - CD -shortTitle: Deploy with GitHub Actions +shortTitle: 使用 GitHub Actions 进行部署 --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Introduction +## 简介 -{% data variables.product.prodname_actions %} offers features that let you control deployments. You can: +{% data variables.product.prodname_actions %} 提供了允许您控制部署的功能。 您可以: -- Trigger workflows with a variety of events. -- Configure environments to set rules before a job can proceed and to limit access to secrets. -- Use concurrency to control the number of deployments running at a time. +- 使用各种事件触发工作流程。 +- 配置环境以在作业可以继续之前设置规则，并限制对机密的访问。 +- 使用并发性来控制一次运行的部署数。 -For more information about continuous deployment, see "[About continuous deployment](/actions/deployment/about-continuous-deployment)." +有关持续部署的更多信息，请参阅“[关于持续部署](/actions/deployment/about-continuous-deployment)”。 -## Prerequisites +## 基本要求 -You should be familiar with the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +您应该熟悉 {% data variables.product.prodname_actions %} 的语法。 更多信息请参阅“[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。 -## Triggering your deployment +## 触发部署 -You can use a variety of events to trigger your deployment workflow. Some of the most common are: `pull_request`, `push`, and `workflow_dispatch`. +您可以使用各种事件来触发您的部署工作流程。 最常见的有：`pull_request`、`put` 和 `Workflow_paid`。 -For example, a workflow with the following triggers runs whenever: +例如，具有以下触发器的工作流在以下情况下会运行： -- There is a push to the `main` branch. -- A pull request targeting the `main` branch is opened, synchronized, or reopened. -- Someone manually triggers it. +- 有人推送到 `main` 分支。 +- 打开、同步或重新打开面向 `main` 分支的拉取请求。 +- 有人手动触发它。 ```yaml on: @@ -52,23 +52,23 @@ on: workflow_dispatch: ``` -For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." +更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows)”。 -## Using environments +## 使用环境 {% data reusables.actions.about-environments %} -## Using concurrency +## 使用并发 -Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time. +并发确保只有使用相同并发组的单一作业或工作流程才会同时运行。 您可以使用并发，以便环境中每次最多有一个正在进行的部署和一个待处理的部署。 {% note %} -**Note:** `concurrency` and `environment` are not connected. The concurrency value can be any string; it does not need to be an environment name. Additionally, if another workflow uses the same environment but does not specify concurrency, that workflow will not be subject to any concurrency rules. +**注意**：`concurrency` 和 `environment` 未连接。 并发值可以是任何字符串；它无需是环境名称。 此外，如果另一个工作流程使用相同的环境，但未指定并发性，则该工作流程将不受任何并发规则的约束。 {% endnote %} -For example, when the following workflow runs, it will be paused with the status `pending` if any job or workflow that uses the `production` concurrency group is in progress. It will also cancel any job or workflow that uses the `production` concurrency group and has the status `pending`. This means that there will be a maximum of one running and one pending job or workflow in that uses the `production` concurrency group. +例如，当以下工作流程运行时，如果正在进行使用 `production` 并发组的任何作业或工作流程，则该工作流程将暂停，且状态为 `pending`。 它还将取消使用 `production` 并发组并且状态为 `pending` 的任何作业或工作流程。 这意味着最多将有一个正在运行的作业或工作流程和一个使用 `production` 并发组的挂起作业或工作流程。 ```yaml name: Deployment @@ -89,7 +89,7 @@ jobs: # ...deployment-specific steps ``` -You can also specify concurrency at the job level. This will allow other jobs in the workflow to proceed even if the concurrent job is `pending`. +您也可以在作业级别指定并发性。 这将允许工作流中的其他作业继续，即使并发作业状态为 `pending`。 ```yaml name: Deployment @@ -109,7 +109,7 @@ jobs: # ...deployment-specific steps ``` -You can also use `cancel-in-progress` to cancel any currently running job or workflow in the same concurrency group. +还可以使用 `cancel-in-progress` 取消同一并发组中任何当前正在运行的作业或工作流程。 ```yaml name: Deployment @@ -132,42 +132,42 @@ jobs: # ...deployment-specific steps ``` -For guidance on writing deployment-specific steps, see "[Finding deployment examples](#finding-deployment-examples)." +有关编写特定于部署的步骤的指导，请参阅“[查找部署示例](#finding-deployment-examples)”。 -## Viewing deployment history +## 查看部署历史记录 -When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. For more information about viewing deployments to environments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)." +当 {% data variables.product.prodname_actions %} 工作流程部署到某个环境时，该环境将显示在存储库的主页上。 有关查看环境部署的详细信息，请参阅“[查看部署历史记录](/developers/overview/viewing-deployment-history)”。 -## Monitoring workflow runs +## 监控工作流程运行 -Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug deployments. For more information see, "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)." +每个工作流程运行都会生成一个实时图表，说明运行进度。 您可以使用此图表来监控和调试部署。 更多信息请参阅“[使用可视化图](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)”。 -You can also view the logs of each workflow run and the history of workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." +您还可以查看每个工作流程运行的日志和工作流程运行的历史记录。 更多信息请参阅“[查看工作流程运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。 -## Tracking deployments through apps +## 通过应用跟踪部署 {% ifversion fpt or ghec %} -If your personal account or organization on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} is integrated with Microsoft Teams or Slack, you can track deployments that use environments through Microsoft Teams or Slack. For example, you can receive notifications through the app when a deployment is pending approval, when a deployment is approved, or when the deployment status changes. For more information about integrating Microsoft Teams or Slack, see "[GitHub extensions and integrations](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)." +如果您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的个人帐户或组织与 Microsoft Teams 或 Slack 集成，则可以通过 Microsoft Teams 或 Slack 跟踪使用环境的部署。 例如，当部署正在等待批准、部署获得批准或部署状态更改时，您可以通过应用接收通知。 有关集成 Microsoft Teams 或 Slack 的详细信息，请参阅“[GitHub 扩展和集成](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)”。 {% endif %} -You can also build an app that uses deployment and deployment status webhooks to track deployments. {% data reusables.actions.environment-deployment-event %} For more information, see "[Apps](/developers/apps)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)." +你还可以构建一个应用，该应用使用部署和部署状态 web 挂钩来跟踪部署。 {% data reusables.actions.environment-deployment-event %} 更多信息请参阅“[应用程序](/developers/apps)”和“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)”。 {% ifversion fpt or ghes or ghec %} -## Choosing a runner +## 选择运行器 -You can run your deployment workflow on {% data variables.product.company_short %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.company_short %}-hosted runners can come from a [wide range of network addresses](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be communicate with your internal services or resources. To overcome this, you can host your own runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)." +您可以在 {% data variables.product.company_short %} 托管的运行器或自托管运行器上运行部署工作流程。 来自 {% data variables.product.company_short %} 托管运行器的流量可以来自[广泛的网络地址](/rest/reference/meta#get-github-meta-information)。 If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be able to communicate with your internal services or resources. 为了克服这一点，您可以托管自己的运行器。 更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”和“[关于 GitHub 托管的运行器](/actions/using-github-hosted-runners/about-github-hosted-runners)”。 {% endif %} -## Displaying a status badge +## 显示状态徽章 -You can use a status badge to display the status of your deployment workflow. {% data reusables.repositories.actions-workflow-status-badge-intro %} +您可以使用状态徽章来显示您的部署工作流程状态。 {% data reusables.repositories.actions-workflow-status-badge-intro %} -For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)." +更多信息请参阅“[添加工作流程状态徽章](/actions/managing-workflow-runs/adding-a-workflow-status-badge)”。 -## Finding deployment examples +## 查找部署示例 -This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows. +本文演示了可添加到部署工作流程的 {% data variables.product.prodname_actions %} 的功能。 {% data reusables.actions.cd-templates-actions %} diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md index 8b0034d35a..1ef503ff69 100644 --- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md +++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md @@ -134,4 +134,4 @@ jobs: * 有关原始入门工作流程，请参阅 {% data variables.product.prodname_actions %} `starter-workflows` 仓库中的 [`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml)。 * 用于部署 Web 应用的操作是正式的 Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) 操作。 * 有关部署到 Azure 的 GitHub 操作工作流程的更多示例，请参阅 [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) 存储库。 -* Azure web 应用文档中的“[在 Azure 中创建 Node.js web 应用](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)”快速入门说明如何通过 [Azure App Service 扩展](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice)使用 VS Code。 +* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using {% data variables.product.prodname_vscode %} with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice). 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 c1e1ea2515..3c82ac9aa4 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 @@ -69,7 +69,7 @@ You can use any machine as a self-hosted runner as long at it meets these requir * 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. -{% ifversion fpt or ghes > 3.2 or ghec or ghae-issue-4462 %} +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## Autoscaling your self-hosted runners You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)." 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 a0bb72ec3b..63f179beba 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 @@ -5,7 +5,7 @@ versions: fpt: '*' ghec: '*' ghes: '>3.2' - ghae: issue-4462 + ghae: '*' type: overview --- diff --git a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md index fc01153822..7eab08ef5f 100644 --- a/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/zh-CN/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -208,7 +208,8 @@ Travis CI 和 {% data variables.product.prodname_actions %} 可以将自定义 ### 在 {% data variables.product.prodname_actions %} 中使用不同的语言 在 {% data variables.product.prodname_actions %} 中使用不同语言时，您可以在作业中创建步骤来设置语言依赖项。 有关使用特定语言的信息，请参阅特定指南： - - [构建并测试 Node.js 或 Python](/actions/guides/building-and-testing-nodejs-or-python) + - [构建和测试 Node.js](/actions/guides/building-and-testing-nodejs) + - [构建和测试 Python](/actions/guides/building-and-testing-python) - [构建和测试 PowerShell](/actions/guides/building-and-testing-powershell) - [使用 Maven 构建和测试 Java](/actions/guides/building-and-testing-java-with-maven) - [使用 Gradle 构建和测试 Java](/actions/guides/building-and-testing-java-with-gradle) diff --git a/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md index 8d92f84c86..3d6fb28e76 100644 --- a/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md +++ b/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md @@ -37,7 +37,7 @@ miniTocMaxHeadingLevel: 3 - + 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 8eee80aae4..5756e3af78 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 @@ -24,7 +24,7 @@ shortTitle: 触发工作流程的事件 某些事件具有多种活动类型。 对于这些事件，您可以指定将触发工作流程运行的活动类型。 有关每个活动类型的含义的详细信息，请参阅“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhook-events-and-payloads)”。 请注意，并非所有 web 挂钩事件都会触发工作流程。 -{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4968 %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae %} ### `branch_protection_rule` | Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | @@ -1051,7 +1051,7 @@ on: {% endnote %} -在存储库中发生发布活动时运行工作流程。 有关发行版 API 的信息，请参阅 GraphQL API 文档中的“[发行版](/graphql/reference/objects#release)”或 REST API 文档中的“[发行版](/rest/reference/repos#releases)”。 +在存储库中发生发布活动时运行工作流程。 有关发行版 API 的信息，请参阅 GraphQL API 文档中的“[发行版](/graphql/reference/objects#release)”或 REST API 文档中的“[发行版](/rest/reference/releases)”。 例如，您可以在版本发布为 `published` 时运行工作流程。 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 f735e1d8e0..fa119048ac 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 @@ -99,18 +99,18 @@ core.setOutput('SELECTED_COLOR', 'green'); 下表显示了在工作流程中可用的工具包功能： -| 工具包函数 | 等效工作流程命令 | -| --------------------- | --------------------------------------------------------------------- | -| `core.addPath` | 可使用环境文件 `GITHUB_PATH` 访问 | -| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +| 工具包函数 | 等效工作流程命令 | +| --------------------- | ---------------------------------------------------------- | +| `core.addPath` | 可使用环境文件 `GITHUB_PATH` 访问 | +| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `core.notice` | `notice` {% endif %} -| `core.error` | `error` | -| `core.endGroup` | `endgroup` | -| `core.exportVariable` | 可使用环境文件 `GITHUB_ENV` 访问 | -| `core.getInput` | 可使用环境变量 `INPUT_{NAME}` 访问 | -| `core.getState` | 可使用环境变量 `STATE_{NAME}` 访问 | -| `core.isDebug` | 可使用环境变量 `RUNNER_DEBUG` 访问 | +| `core.error` | `error` | +| `core.endGroup` | `endgroup` | +| `core.exportVariable` | 可使用环境文件 `GITHUB_ENV` 访问 | +| `core.getInput` | 可使用环境变量 `INPUT_{NAME}` 访问 | +| `core.getState` | 可使用环境变量 `STATE_{NAME}` 访问 | +| `core.isDebug` | 可使用环境变量 `RUNNER_DEBUG` 访问 | {%- if actions-job-summaries %} | `core.summary` | 可使用环境变量 `GITHUB_STEP_SUMMARY` 访问 | {%- endif %} @@ -170,7 +170,7 @@ Write-Output "::debug::Set the Octocat variable" {% endpowershell %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ## 设置通知消息 diff --git a/translations/zh-CN/content/admin/code-security/index.md b/translations/zh-CN/content/admin/code-security/index.md index e289e60d6c..c9499cd3f3 100644 --- a/translations/zh-CN/content/admin/code-security/index.md +++ b/translations/zh-CN/content/admin/code-security/index.md @@ -5,7 +5,7 @@ intro: 您可以使用将机密和漏洞排除在代码库之外并维护软件 versions: ghes: '*' ghec: '*' - ghae: issue-4864 + ghae: '*' topics: - Enterprise children: diff --git a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md index 55f6a3e42e..6aa1399182 100644 --- a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md @@ -5,7 +5,7 @@ shortTitle: About supply chain security permissions: '' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise diff --git a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md index 753726f4cb..5f3c1c4c1f 100644 --- a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md +++ b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md @@ -4,7 +4,7 @@ shortTitle: 供应链安全 intro: 您可以可视化、维护和保护开发人员软件供应链中的依赖项。 versions: ghes: '*' - ghae: issue-4864 + ghae: '*' topics: - Enterprise children: diff --git a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md index 953517b46c..17ea3bbd95 100644 --- a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md @@ -5,7 +5,7 @@ shortTitle: View vulnerability data permissions: 'Site administrators can view vulnerability data on {% data variables.product.product_location %}.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md index 6f1210f301..54d17c56d4 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -12,7 +12,7 @@ topics: ## About {% data variables.product.prodname_github_connect %} -{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae-issue-4864 %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}. +{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}. {% data variables.product.prodname_github_connect %} does not open {% data variables.product.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)." @@ -28,7 +28,7 @@ After you configure the connection between {% data variables.product.product_loc Feature | Description | More information | ------- | ----------- | ---------------- |{% ifversion ghes %} -Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae-issue-4864 %} +Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} {% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% if server-statistics %} {% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} @@ -64,7 +64,7 @@ Additional data is transmitted if you enable individual features of {% data vari Feature | Data | Which way does the data flow? | Where is the data used? | ------- | ---- | --------- | ------ |{% ifversion ghes %} -Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %} +Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot_alerts %} | Vulnerability alerts | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %} {% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository

If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} {% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% if server-statistics %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md index f2561e091c..f09cd71b31 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -15,7 +15,7 @@ redirect_from: permissions: 'Enterprise owners can enable {% data variables.product.prodname_dependabot %}.' versions: ghes: '*' - ghae: issue-4864 + ghae: '*' type: how_to topics: - Enterprise @@ -64,6 +64,8 @@ After you enable {% data variables.product.prodname_dependabot_alerts %}, you ca {% endnote %} +By default, {% data variables.product.prodname_actions %} runners used by {% data variables.product.prodname_dependabot %} need access to the internet, to download updated packages from upstream package managers. For {% data variables.product.prodname_dependabot_updates %} powered by {% data variables.product.prodname_github_connect %}, internet access provides your runners with a token that allows access to dependencies and advisories hosted on {% data variables.product.prodname_dotcom_the_website %}. + With {% data variables.product.prodname_dependabot_updates %}, {% data variables.product.company_short %} automatically creates pull requests to update dependencies in two ways. - **{% data variables.product.prodname_dependabot_version_updates %}**: Users add a {% data variables.product.prodname_dependabot %} configuration file to the repository to enable {% data variables.product.prodname_dependabot %} to create pull requests when a new version of a tracked dependency is released. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)." @@ -121,6 +123,11 @@ Before you enable {% data variables.product.prodname_dependabot_updates %}, you ![Screenshot of the dropdown menu to enable updating vulnerable dependencies](/assets/images/enterprise/site-admin-settings/dependabot-updates-button.png) -{% elsif ghes > 3.2 %} -When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Managing self-hosted runners for {% data variables.product.prodname_dependabot_updates %} on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)." +{% endif %} +{% ifversion ghes > 3.2 %} + +When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Managing self-hosted runners for {% data variables.product.prodname_dependabot_updates %} on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)." + +If you need enhanced security, we recommend configuring {% data variables.product.prodname_dependabot %} to use private registries. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_dependabot %}](/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot)." + {% endif %} 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 bbd29e52aa..3335f4cc4d 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 @@ -673,6 +673,12 @@ This utility manually repackages a repository network to optimize pack storage. You can add the optional `--prune` argument to remove unreachable Git objects that aren't referenced from a branch, tag, or any other ref. This is particularly useful for immediately removing [previously expunged sensitive information](/enterprise/user/articles/remove-sensitive-data/). +{% warning %} + +**Warning**: Before using the `--prune` argument to remove unreachable Git objects, put {% data variables.product.product_location %} into maintenance mode, or ensure the repository is offline. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)." + +{% endwarning %} + ```shell ghe-repo-gc username/reponame ``` diff --git a/translations/zh-CN/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md b/translations/zh-CN/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md index cbac75727a..ac3054b2b2 100644 --- a/translations/zh-CN/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md +++ b/translations/zh-CN/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md @@ -33,12 +33,13 @@ topics: ## 配置存储库缓存 -1. 在测试期间，您必须为主 {% data variables.product.prodname_ghe_server %} 设备上的存储库缓存启用功能标志。 +{% ifversion ghes = 3.3 %} +1. 在主 {% data variables.product.prodname_ghe_server %} 设备上，为存储库缓存启用功能标志。 ``` $ ghe-config cluster.cache-enabled true ``` - +{%- endif %} 1. 在所需平台上设置新的 {% data variables.product.prodname_ghe_server %} 设备。 此设备将是您的存储库缓存。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)”。 {% data reusables.enterprise_installation.replica-steps %} 1. 使用 SSH 连接到存储库缓存的 IP 地址。 @@ -46,7 +47,13 @@ topics: ```shell $ ssh -p 122 admin@REPLICA IP ``` +{%- ifversion ghes = 3.3 %} +1. 在缓存副本上，为存储库缓存启用功能标志。 + ``` + $ ghe-config cluster.cache-enabled true + ``` +{%- endif %} {% data reusables.enterprise_installation.generate-replication-key-pair %} {% data reusables.enterprise_installation.add-ssh-key-to-primary %} 1. 要验证与主缓存的连接并为存储库缓存启用副本模式，请再次运行 `ghe-repl-setup`。 diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md index aa4af2b44f..9d6a31ef24 100644 --- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md +++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md @@ -18,7 +18,7 @@ topics: SNMP 是一种用于通过网络监视设备的公共标准。 强烈建议启用 SNMP，以便监视 {% data variables.product.product_location %} 的健康状态并了解何时向主机增加更多内存、存储空间或处理器能力。 -{% data variables.product.prodname_enterprise %} 采用标准 SNMP 安装，因此您可以充分利用 Nagios 或其他任何监视系统可用的[多种插件](http://www.monitoring-plugins.org/doc/man/check_snmp.html)。 +{% data variables.product.prodname_enterprise %} 采用标准 SNMP 安装，因此您可以充分利用 Nagios 或其他任何监视系统可用的[多种插件](https://www.monitoring-plugins.org/doc/man/check_snmp.html)。 ## 配置 SNMP v2c @@ -66,7 +66,7 @@ SNMP 是一种用于通过网络监视设备的公共标准。 强烈建议启 #### 查询 SNMP 数据 -关于您的设备的硬件和软件级信息都适用于 SNMP v3。 由于 `noAuthNoPriv` 和 `authNoPriv` 安全等级缺乏加密和隐私，因此我们的结果 SNMP 报告中不包括 `hrSWRun` 表 (1.3.6.1.2.1.25.4.)。 如果您使用的是 `authPriv` 安全等级，我们将包括此表。 更多信息请参阅“[OID 参考文档](http://oidref.com/1.3.6.1.2.1.25.4)。 +关于您的设备的硬件和软件级信息都适用于 SNMP v3。 由于 `noAuthNoPriv` 和 `authNoPriv` 安全等级缺乏加密和隐私，因此我们的结果 SNMP 报告中不包括 `hrSWRun` 表 (1.3.6.1.2.1.25.4.)。 如果您使用的是 `authPriv` 安全等级，我们将包括此表。 更多信息请参阅“[OID 参考文档](https://oidref.com/1.3.6.1.2.1.25.4)。 如果使用 SNMP v2c，则仅会提供关于您的设备的硬件级信息。 {% data variables.product.prodname_enterprise %} 中的应用程序和服务未配置 OID 来报告指标。 有多个 MIB 可用，在网络中 SNMP 的支持下，在单独的工作站上运行 `smpwaste` 可以看到： diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index 743d214535..c70b99c442 100644 --- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -1,12 +1,12 @@ --- title: Getting started with self-hosted runners for your enterprise shortTitle: Self-hosted runners -intro: You can configure a runner machine for your enterprise so your developers can start automating workflows with {% data variables.product.prodname_actions %}. +intro: 'You can configure a runner machine for your enterprise so your developers can start automating workflows with {% data variables.product.prodname_actions %}.' versions: ghec: '*' ghes: '*' ghae: '*' -permissions: Enterprise owners can configure policies for {% data variables.product.prodname_actions %} and add self-hosted runners to the enterprise. +permissions: 'Enterprise owners can configure policies for {% data variables.product.prodname_actions %} and add self-hosted runners to the enterprise.' type: quick_start topics: - Actions @@ -32,7 +32,7 @@ This guide shows you how to apply a centralized management approach to self-host 1. Deploy a self-hosted runner for your enterprise 1. Create a group to manage access to the runners available to your enterprise 1. Optionally, further restrict the repositories that can use the runner -{%- ifversion ghec or ghae-issue-4462 or ghes > 3.2 %} +{%- ifversion ghec or ghae or ghes > 3.2 %} 1. Optionally, build custom tooling to automatically scale your self-hosted runners {% endif %} @@ -122,7 +122,7 @@ Optionally, organization owners can further restrict the access policy of the ru For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." -{% ifversion ghec or ghae-issue-4462 or ghes > 3.2 %} +{% ifversion ghec or ghae or ghes > 3.2 %} ## 5. Automatically scale your self-hosted runners diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index f539aeca8d..7ea2bb0b09 100644 --- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -46,7 +46,7 @@ Before enabling access to all actions from {% data variables.product.prodname_do ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png) 1. {% data reusables.actions.enterprise-limit-actions-use %} -{% ifversion ghes > 3.2 or ghae-issue-4815 %} +{% ifversion ghes > 3.2 or ghae %} ## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %} diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md index 1af5a98dfd..3f5f872968 100644 --- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md +++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md @@ -33,7 +33,7 @@ If your machine has access to both systems at the same time, you can do the sync The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories. -{% ifversion ghes > 3.2 or ghae-issue-4815 %} +{% ifversion ghes > 3.2 or ghae %} {% note %} **Note:** The `actions-sync` tool is intended for use in systems where {% data variables.product.prodname_github_connect %} is not enabled. If you run the tool on a system with {% data variables.product.prodname_github_connect %} enabled, you may see the error `The repository has been retired and cannot be reused`. This indicates that a workflow has used that action directly on {% data variables.product.prodname_dotcom_the_website %} and the namespace is retired on {% data variables.product.product_location %}. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md index 97e81a3546..5d4d770631 100644 --- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md +++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md @@ -47,7 +47,7 @@ Once {% data variables.product.prodname_github_connect %} is configured, you can 1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`. 1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}. - {% ifversion ghes > 3.2 or ghae-issue-4815 %} + {% ifversion ghes > 3.2 or ghae %} {% note %} **Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.product.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index 844392d5b5..3d666e5d33 100644 --- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -2,7 +2,7 @@ title: Audit log events for your enterprise intro: Learn about audit log events recorded for your enterprise. shortTitle: Audit log events -permissions: Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can interact with the audit log. +permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can interact with the audit log.' miniTocMaxHeadingLevel: 4 redirect_from: - /enterprise/admin/articles/audited-actions @@ -202,7 +202,7 @@ Action | Description | `config_entry.update` | A configuration setting was edited. These events are only visible in the site admin audit log. The type of events recorded relate to:
- Enterprise settings and policies
- Organization and repository permissions and settings
- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings. {%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} ### `dependabot_alerts` category actions | Action | Description @@ -240,7 +240,7 @@ Action | Description | `dependabot_security_updates_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. {%- endif %} -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} ### `dependency_graph` category actions | Action | Description @@ -682,7 +682,7 @@ Action | Description | `org.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was removed. | `org.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was removed from an organization. | `org.remove_billing_manager` | An owner removed a billing manager from an organization. {% ifversion fpt or ghec %}For more information, see "[Removing a billing manager from your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization)"{% endif %}{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and a billing manager didn't use 2FA or disabled 2FA.{% endif %} -| `org.remove_member` | An [owner removed a member from an organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disabled 2FA{% endif %}. Also an [organization member removed themselves](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization) from an organization. +| `org.remove_member` | An [owner removed a member from an organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disabled 2FA{% endif %}. Also an [organization member removed themselves](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization) from an organization. | `org.remove_outside_collaborator` | An owner removed an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an outside collaborator didn't use 2FA or disabled 2FA{% endif %}. | `org.remove_self_hosted_runner` | A self-hosted runner was removed. For more information, see "[Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)." | `org.rename` | An organization was renamed. @@ -1145,7 +1145,7 @@ Action | Description | `repository_visibility_change.disable` | The ability for enterprise members to update a repository's visibility was disabled. Members are unable to change repository visibilities in an organization, or all organizations in an enterprise. | `repository_visibility_change.enable` | The ability for enterprise members to update a repository's visibility was enabled. Members are able to change repository visibilities in an organization, or all organizations in an enterprise. -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} ### `repository_vulnerability_alert` category actions | Action | Description 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 5b731dd40e..97df83b1e0 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 @@ -66,7 +66,7 @@ You can choose to disable {% data variables.product.prodname_actions %} for all 1. Under "Policies", select {% data reusables.actions.policy-label-for-select-actions-workflows %} and add your required actions{% if actions-workflow-policy %} and reusable workflows{% endif %} to the list. {% if actions-workflow-policy %} ![Add actions and reusable workflows to the allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list-with-workflows.png) - {%- elsif ghes or ghae-issue-5094 %} + {%- elsif ghes or ghae %} ![Add actions to the allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) {%- elsif ghae %} ![Add actions to the allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md index a725faf1c7..c3beae0da5 100644 --- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md @@ -68,7 +68,15 @@ You can view more information about the person's access to your enterprise, such {% ifversion ghec %} ## Viewing pending invitations -You can see all the pending invitations to become administrators, members, or outside collaborators in your enterprise. You can filter the list in useful ways, such as by organization. You can find a specific person by searching for their username or display name. +You can see all the pending invitations to become members, administrators, or outside collaborators in your enterprise. You can filter the list in useful ways, such as by organization. You can find a specific person by searching for their username or display name. + +In the list of pending members, for any individual account, you can cancel all invitations to join organizations owned by your enterprise. This does not cancel any invitations for that same person to become an enterprise administrator or outside collaborator. + +{% note %} + +**Note:** If an invitation was provisioned via SCIM, you must cancel the invitation via your identity provider (IdP) instead of on {% data variables.product.prodname_dotcom %}. + +{% endnote %} If you use {% data variables.product.prodname_vss_ghe %}, the list of pending invitations includes all {% data variables.product.prodname_vs %} subscribers that haven't joined any of your organizations on {% data variables.product.prodname_dotcom %}, even if the subscriber does not have a pending invitation to join an organization. For more information about how to get {% data variables.product.prodname_vs %} subscribers access to {% data variables.product.prodname_enterprise %}, see "[Setting up {% data variables.product.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)." @@ -77,7 +85,9 @@ If you use {% data variables.product.prodname_vss_ghe %}, the list of pending in 1. Under "People", click **Pending invitations**. ![Screenshot of the "Pending invitations" tab in the sidebar](/assets/images/help/enterprises/pending-invitations-tab.png) +1. Optionally, to cancel all invitations for an account to join organizations owned by your enterprise, to the right of the account, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Cancel invitation**. + ![Screenshot of the "Cancel invitation" button](/assets/images/help/enterprises/cancel-enterprise-member-invitation.png) 1. Optionally, to view pending invitations for enterprise administrators or outside collaborators, under "Pending members", click **Administrators** or **Outside collaborators**. ![Screenshot of the "Members", "Administrators", and "Outside collaborators" tabs](/assets/images/help/enterprises/pending-invitations-type-tabs.png) diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index b0c87d6303..113e3394b5 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -16,7 +16,7 @@ shortTitle: Authentication to GitHub --- ## About authentication to {% data variables.product.prodname_dotcom %} -To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. +To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. You can access your resources in {% data variables.product.product_name %} in a variety of ways: in the browser, via {% data variables.product.prodname_desktop %} or another desktop application, with the API, or via the command line. Each way of accessing {% data variables.product.product_name %} supports different modes of authentication. {%- ifversion not fpt %} @@ -27,35 +27,47 @@ You can access your resources in {% data variables.product.product_name %} in a ## Authenticating in your browser -You can authenticate to {% data variables.product.product_name %} in your browser {% ifversion ghae %}using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."{% else %}in different ways. +{% ifversion ghae %} + +You can authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)." + +{% else %} {% ifversion fpt or ghec %} -- If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} - If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also be required to enable two-factor authentication. +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} + +If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also use two-factor authentication and SAML single sign-on, which can be required by organization and enterprise owners. + +{% else %} + +You can authenticate to {% data variables.product.product_name %} in your browser in a number of ways. + {% endif %} - **Username and password only** - You'll create a password when you create your account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)."{% ifversion fpt or ghec %} - If you have not enabled 2FA, {% data variables.product.product_name %} will ask for additional verification when you first sign in from an unrecognized device, such as a new browser profile, a browser where the cookies have been deleted, or a new computer. - - After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the GitHub Mobile application installed, you'll receive a notification there instead.{% endif %} + + After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the {% data variables.product.prodname_mobile %} application installed, you'll receive a notification there instead. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."{% endif %} - **Two-factor authentication (2FA)** (recommended) - If you enable 2FA, after you successfully enter your username and password, we'll also prompt you to provide a code that's generated by a time-based one time password (TOTP) application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)." - - In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% endif %}{% ifversion ghes %} -- **Identity provider (IdP) authentication** - - Your site administrator may configure {% data variables.product.product_location %} to use authentication with an IdP instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)." + - In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% ifversion ghes %} +- **External authentication** + - Your site administrator may configure {% data variables.product.product_location %} to use external authentication instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)."{% endif %}{% ifversion fpt or ghec %} +- **SAML single sign-on** + - Before you can access resources owned by an organization or enterprise account that uses SAML single sign-on, you may need to also authenticate through an IdP. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} + {% endif %} ## Authenticating with {% data variables.product.prodname_desktop %} - You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)." ## Authenticating with the API You can authenticate with the API in different ways. -- **Personal access tokens** +- **Personal access tokens** - In limited situations, such as testing, you can use a personal access token to access the API. Using a personal access token enables you to revoke access at any time. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)." - **Web application flow** - For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)." @@ -68,11 +80,11 @@ You can access repositories on {% data variables.product.product_name %} from th ### HTTPS -You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. +You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy. If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a personal access token or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login). -If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a personal access token. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git). +If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a personal access token. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them with a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git). ### SSH 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 cf241ab5cd..b823047c68 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 @@ -44,7 +44,7 @@ A token with no assigned scopes can only access public information. To use your {% data reusables.user-settings.personal_access_tokens %} {% data reusables.user-settings.generate_new_token %} 5. Give your token a descriptive name. - ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %} + ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae or ghec %} 6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker. ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %} 7. Select the scopes, or permissions, you'd like to grant this token. To use your token to access repositories from the command line, select **repo**. @@ -82,5 +82,5 @@ Instead of manually entering your PAT for every HTTPS Git operation, you can cac ## Further reading -- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} - "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md index 385e8c165a..d706fb6c7b 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md @@ -24,9 +24,9 @@ You can remove the file from the latest commit with `git rm`. For information on {% warning %} -This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. However, it's important to note that those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}. +**Warning**: This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. However, those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones or forks of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}. -**Warning: Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! If you committed a key, generate a new one. Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. Consider these limitations in your decision to rewrite your repository's history. +**Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! If you committed a key, generate a new one. Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. Consider these limitations in your decision to rewrite your repository's history. {% endwarning %} @@ -151,7 +151,7 @@ To illustrate how `git filter-repo` works, we'll show you how to remove your fil After using either the BFG tool or `git filter-repo` to remove the sensitive data and pushing your changes to {% data variables.product.product_name %}, you must take a few more steps to fully remove the data from {% data variables.product.product_name %}. -1. Contact {% data variables.contact.contact_support %}, asking them to remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed. +1. Contact {% data variables.contact.contact_support %}, asking them to remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed.{% ifversion ghes %} For more information about how site administrators can remove unreachable Git objects, see "[Command line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repo-gc)."{% endif %} 2. Tell your collaborators to [rebase](https://git-scm.com/book/en/Git-Branching-Rebasing), *not* merge, any branches they created off of your old (tainted) repository history. One merge commit could reintroduce some or all of the tainted history that you just went to the trouble of purging. 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 340312de61..5cfc48630e 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 @@ -28,15 +28,11 @@ shortTitle: 安全日志 1. 在用户设置侧边栏中，单击 **Security log（安全日志）**。 ![安全日志选项卡](/assets/images/help/settings/audit-log-tab.png) {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} ## 搜索安全日志 {% data reusables.audit_log.audit-log-search %} ### 基于执行的操作搜索 -{% else %} -## 了解安全日志中的事件 -{% endif %} 安全日志中列出的事件由您的操作触发。 操作分为以下几类： @@ -109,10 +105,10 @@ shortTitle: 安全日志 ### `oauth_authority` 类别操作 -| 操作 | 描述 | -| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create` | 当您[授予 {% data variables.product.prodname_oauth_app %} 访问权限](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)时触发。 | -| `destroy` | 当您 [撤销 {% data variables.product.prodname_oauth_app %}对您帐户的访问](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} 时，以及当 [授权被吊销或过期](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)时触发。{% else %}.{% endif %} +| 操作 | 描述 | +| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `create` | 当您[授予 {% data variables.product.prodname_oauth_app %} 访问权限](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)时触发。 | +| `destroy` | 当您 [撤销 {% data variables.product.prodname_oauth_app %}对您帐户的访问](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae or ghes > 3.2 or ghec %} 时，以及当 [授权被吊销或过期](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)时触发。{% else %}。{% endif %} {% ifversion fpt or ghec %} @@ -178,25 +174,25 @@ shortTitle: 安全日志 {% 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-user-account)”） | -| `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-user-account)”） | -| `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-user-account)”） | -| `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-user-account)”） | -| `waitlist_join` | 当您加入成为被赞助开发者的等候名单时触发（请参阅“[为您的个人帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”） | +| 操作 | 描述 | +| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `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` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `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` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `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` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | +| `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") | {% endif %} {% ifversion fpt or ghec %} diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md index 0d6d387f01..6bc662da9f 100644 --- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md +++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md @@ -14,7 +14,7 @@ redirect_from: - /github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation --- -当令牌 {% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}已过期或 {% endif %} 已被吊销时，它不能再用于对 Git 和 API 请求进行身份验证。 无法还原过期或已吊销的令牌，您或应用程序将需要创建新令牌。 +当令牌 {% ifversion fpt or ghae or ghes > 3.2 or ghec %}已过期或 {% endif %} 已被吊销时，它不能再用于对 Git 和 API 请求进行身份验证。 无法还原过期或已吊销的令牌，您或应用程序将需要创建新令牌。 本文介绍了 {% data variables.product.product_name %} 令牌可能被吊销或过期的可能原因。 @@ -24,7 +24,7 @@ redirect_from: {% endnote %} -{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## 令牌在到达其到期日期后被吊销 创建个人访问令牌时，建议为令牌设置过期时间。 到达令牌的到期日期后，令牌将自动吊销。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)”。 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 3ed800b595..75c003b0c8 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 @@ -57,7 +57,7 @@ shortTitle: 更新访问凭据 {% ifversion not ghae %} -如果您已重置帐户密码，并且还希望触发从 GitHub Mobile 应用注销，则可以撤销对“GitHub iOS”或“GitHub Android”OAuth 应用的授权。 有关其他信息，请参阅“[>审查授权的集成](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)”。 +如果您已重置帐户密码，并且还想触发从 {% data variables.product.prodname_mobile %} 应用程序注销，则可以撤销对“GitHub iOS”或“GitHub Android”OAuth 应用程序 的授权。 这将注销与您的帐户关联的 {% data variables.product.prodname_mobile %} 应用程序的所有实例。 有关其他信息，请参阅“[>审查授权的集成](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)”。 {% endif %} diff --git a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md index 31db45b53b..04e4f2d27c 100644 --- a/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md +++ b/translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md @@ -22,7 +22,7 @@ shortTitle: 更改 2FA 递送方式 {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security %} -3. Next to "Primary two-factor method", click **Change**. ![Edit primary delivery options](/assets/images/help/2fa/edit-primary-delivery-option.png) +3. 在“Primary two-factor method（主要双重方法）”旁边，点击 **Change（更改）**。 ![编辑主要递送选项](/assets/images/help/2fa/edit-primary-delivery-option.png) 4. 在“Delivery options（递送选项）”下，单击 **Reconfigure two-factor authentication（重新配置双重身份验证）**。 ![切换 2FA 递送选项](/assets/images/help/2fa/2fa-switching-methods.png) 5. 决定是使用 TOTP 移动应用程序还是使用短信设置双重身份验证。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication)”。 - 要使用 TOTP 移动应用程序设置双重身份验证，请单击 **Set up using an app（使用应用程序设置）**。 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 7c799b17c3..41f9cebff2 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 @@ -48,7 +48,7 @@ shortTitle: GitHub Actions 的计费 仓库使用的存储空间是 {% data variables.product.prodname_actions %} 构件和 {% data variables.product.prodname_registry %} 使用的存储空间总计。 您的存储成本是您帐户拥有的所有帐户的总使用量。 有关 {% data variables.product.prodname_registry %} 定价的更多信息，请参阅“[关于 {% data variables.product.prodname_registry %} 的计费](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)”。 - 如果您的帐户使用量超出了这些限额，并且您设置的支出限额高于 0 美元，则每月的每 GB 存储用量和每分钟用量需要支付 0.25 美元，具体取决于 {% data variables.product.prodname_dotcom %} 托管运行器使用的操作系统。 {% data variables.product.prodname_dotcom %} 将每个作业使用的分钟数舍入到最接近的分钟整数。 + 如果您的帐户使用量超出了这些限额，并且您设置的支出限额高于 0 美元，则每天每 GB 存储用量和每分钟用量需要支付 0.008 美元，具体取决于 {% data variables.product.prodname_dotcom %} 托管运行器使用的操作系统。 {% data variables.product.prodname_dotcom %} 将每个作业使用的分钟数舍入到最接近的分钟整数。 {% note %} diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/zh-CN/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md index d9247cd964..1bbe77f653 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md +++ b/translations/zh-CN/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md @@ -49,9 +49,9 @@ All data transferred out, when triggered by {% data variables.product.prodname_a Storage usage is shared with build artifacts produced by {% data variables.product.prodname_actions %} for repositories owned by your account. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." -{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.25 USD per GB of storage and $0.50 USD per GB of data transfer. +{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and $0.50 USD per GB of data transfer. -For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.25 USD per GB or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD. +For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.008 USD per GB per day or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD. {% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %} diff --git a/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md index 15c126e263..49cf14c22f 100644 --- a/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md +++ b/translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md @@ -59,7 +59,7 @@ One person may be able to complete the tasks because the person has all of the r **Tips**: - While not required, we recommend that the organization owner sends an invitation to the same email address used for the subscriber's User Primary Name (UPN). When the email address on {% data variables.product.product_location %} matches the subscriber's UPN, you can ensure that another enterprise does not claim the subscriber's license. - - If the subscriber accepts the invitation to the organization with an existing personal account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their personal account on {% data variables.product.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account)." + - If the subscriber accepts the invitation to the organization with an existing personal account on {% data variables.product.product_location %}, we recommend that the subscriber add the email address they use for {% data variables.product.prodname_vs %} to their personal account on {% data variables.product.product_location %}. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account)." - If the organization owner must invite a large number of subscribers, a script may make the process faster. For more information, see [the sample PowerShell script](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) in the `github/platform-samples` repository. {% endtip %} 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 cccde8bdec..a462055e5a 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 @@ -73,7 +73,7 @@ By default, the {% data variables.product.prodname_codeql_workflow %} uses the ` If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Additionally, when an `on:push` scan returns results that can be mapped to an open pull request, these alerts will automatically appear on the pull request in the same places as other pull request alerts. The alerts are identified by comparing the existing analysis of the head of the branch to the analysis for the target branch. For more information on {% data variables.product.prodname_code_scanning %} alerts in pull requests, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." {% endif %} @@ -85,7 +85,7 @@ For more information about the `pull_request` event, see "[Events that trigger w If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)." -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." {% endif %} diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index 7649b34387..990c6e03c7 100644 --- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -155,9 +155,9 @@ The names of the {% data variables.product.prodname_code_scanning %} analysis ch ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png) -When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. +When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check. -{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png) The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request. @@ -167,13 +167,13 @@ For example, in the screenshot above, {% data variables.product.prodname_code_sc ![Missing analysis for commit message](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png) {% endif %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} ### Reasons for the "Analysis not found" message {% else %} ### Reasons for the "Missing analysis" message {% endif %} -After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. +After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message. There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include: 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 b91352a273..0f3eeabbb0 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 @@ -28,7 +28,7 @@ topics: ## 关于拉取请求上的 {% data variables.product.prodname_code_scanning %} 结果 在仓库中，如果 {% data variables.product.prodname_code_scanning %} 被配置为拉取请求检查，则 {% data variables.product.prodname_code_scanning %} 将检查拉取请求中的代码。 默认情况下，这仅限于针对默认分支的拉取请求，但是您可以在 {% data variables.product.prodname_actions %} 或第三方 CI/CD 系统中更改此配置。 如果合并分支给目标分支带来新的 {% data variables.product.prodname_code_scanning %} 警报，这些警报将在拉取请求中被报告为检查结果。 警报还将在拉取请求的 **Files changed（文件已更改）**选项卡中显示为注释。 如果您拥有仓库的写入权限，您可以在 **Security（安全）**选项卡中查看任何现有的 {% data variables.product.prodname_code_scanning %} 警报。 有关仓库警报的更多信息，请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)”。 -{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %} +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} 在 {% data variables.product.prodname_code_scanning %} 配置为在每次推送代码时扫描的存储库中，{% data variables.product.prodname_code_scanning %} 还会将结果映射到任何打开的拉取请求，并将警报作为注释添加到与其他拉取请求检查相同的位置。 更多信息请参阅“[在推送时扫描](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)”。 {% endif %} @@ -42,7 +42,7 @@ topics: 对于 {% data variables.product.prodname_code_scanning %} 的所有配置，包含 {% data variables.product.prodname_code_scanning %} 结果的检查为：**{% data variables.product.prodname_code_scanning_capc %} 结果**。 所使用的每个分析工具的结果将单独显示。 由拉取请求中的更改引起的任何新警报都显示为注释。 -{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 or ghec %} 要查看所分析分支的完整警报集，请单击“**查看所有分支警报**”。 这将打开完整的警报视图，您可以在其中按类型、严重性、标记等筛选分支上的所有警报。 更多信息请参阅“[管理仓库的代码扫描警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)”。 +{% ifversion fpt or ghes > 3.2 or ghae or ghec %} 要查看所分析分支的完整警报集，请单击“**查看所有分支警报**”。 这将打开完整的警报视图，您可以在其中按类型、严重性、标记等筛选分支上的所有警报。 更多信息请参阅“[管理仓库的代码扫描警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)”。 ![拉取请求的 {% data variables.product.prodname_code_scanning_capc %} 结果检查](/assets/images/help/repository/code-scanning-results-check.png) {% endif %} diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index 233364f4bf..b73490579e 100644 --- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -10,7 +10,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md index 4f6968a138..e5b5a4a033 100644 --- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md +++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md @@ -5,7 +5,7 @@ shortTitle: 配置 Dependabot 警报 versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md index 1fda1d6562..c6fd3ed1d5 100644 --- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md +++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -31,7 +31,7 @@ topics: {% ifversion fpt or ghec %}如果您是组织所有者，您可以对组织中的所有仓库一键启用或禁用 {% data variables.product.prodname_dependabot_alerts %}。 您也可以设置是否对新建的仓库启用或禁用有漏洞依赖项检测。 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)”。 {% endif %} -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} 默认情况下，如果您的企业所有者已配置电子邮件以获取有关企业的通知，您将收到 {% data variables.product.prodname_dependabot_alerts %} 电子邮件。 企业所有者也可以在没有通知的情况下启用 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。 diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/index.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/index.md index 50226097a9..eb1e253e71 100644 --- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/index.md +++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/index.md @@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md index 64b4137800..1826ee5240 100644 --- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md +++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md @@ -11,7 +11,7 @@ shortTitle: 查看 Dependabot 警报 versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -55,7 +55,7 @@ topics: {% note %} -**注意：** 在测试版期间，此功能仅适用于在 2022 年 4 月 14 日*之后*创建的新 Python 公告，以及历史 Python 公告的子集。 GitHub 正在努力回填其他历史 Python 公告的数据，这些公告是滚动添加的。 有漏洞的调用仅在 {% data variables.product.prodname_dependabot_alerts %} 页面上突出显示。 +**注意：** 在测试版期间，此功能仅适用于在 2022 年 4 月 14 日*之后*创建的新 Python 公告，以及历史 Python 公告的子集。 {% data variables.product.prodname_dotcom %} 正在努力回填其他历史 Python 公告的数据，这些公告是滚动添加的。 有漏洞的调用仅在 {% data variables.product.prodname_dependabot_alerts %} 页面上突出显示。 {% endnote %} @@ -65,7 +65,7 @@ topics: 对于检测到有漏洞的调用的警报，警报详细信息页面将显示其他信息： -- 显示函数使用位置或者在有多个调用时显示对函数的第一次调用的代码块。 +- 一个或多个代码块，显示函数的使用位置。 - 列出函数本身以及指向调用函数的行的链接的注释。 ![显示警报的并带有"有漏洞的调用"标签的警报详细信息页面屏幕截图](/assets/images/help/repository/review-calls-to-vulnerable-functions.png) diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md index a79c611287..fc16885db1 100644 --- a/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md +++ b/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md @@ -61,7 +61,7 @@ If security updates are not enabled for your repository and you don't know why, You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below). -You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your personal account or organization. For more information, see "[Managing security and analysis settings for your personal 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)." +You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your personal account or organization. For more information, see "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% data variables.product.prodname_dependabot_security_updates %} require specific repository settings. For more information, see "[Supported repositories](#supported-repositories)." diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md index 41bafcbf8c..cd1a0ff73d 100644 --- a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md +++ b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md @@ -30,7 +30,7 @@ shortTitle: Dependabot 版本更新 {% data variables.product.prodname_dependabot %} 负责维护您的依赖项。 您可以使用它来确保仓库自动跟上它所依赖的包和应用程序的最新版本。 -通过将 a _dependabot.yml_configuration 文件检入仓库，可启用 {% data variables.product.prodname_dependabot_version_updates %}。 配置文件指定存储在仓库中的清单或其他包定义文件的位置。 {% data variables.product.prodname_dependabot %} 使用此信息来检查过时的软件包和应用程序。 {% data variables.product.prodname_dependabot %} 确定依赖项是否有新版本，它通过查看依赖的语义版本 ([semver](https://semver.org/)) 来决定是否应更新该版本。 对于某些软件包管理器，{% data variables.product.prodname_dependabot_version_updates %} 也支持供应。 供应（或缓存）的依赖项是检入仓库中特定目录的依赖项，而不是在清单中引用的依赖项。 即使包服务器不可用，供应的依赖项在生成时也可用。 {% data variables.product.prodname_dependabot_version_updates %} 可以配置为检查为新版本供应的依赖项，并在必要时更新它们。 +通过将 _dependabot.yml_ 配置文件检入仓库，可启用 {% data variables.product.prodname_dependabot_version_updates %}。 配置文件指定存储在仓库中的清单或其他包定义文件的位置。 {% data variables.product.prodname_dependabot %} 使用此信息来检查过时的软件包和应用程序。 {% data variables.product.prodname_dependabot %} 确定依赖项是否有新版本，它通过查看依赖的语义版本 ([semver](https://semver.org/)) 来决定是否应更新该版本。 对于某些软件包管理器，{% data variables.product.prodname_dependabot_version_updates %} 也支持供应。 供应（或缓存）的依赖项是检入仓库中特定目录的依赖项，而不是在清单中引用的依赖项。 即使包服务器不可用，供应的依赖项在生成时也可用。 {% data variables.product.prodname_dependabot_version_updates %} 可以配置为检查为新版本供应的依赖项，并在必要时更新它们。 当 {% data variables.product.prodname_dependabot %} 发现过时的依赖项时，它会发起拉取请求以将清单更新到依赖项的最新版本。 对于供应和依赖项，{% data variables.product.prodname_dependabot %} 提出拉取请求以直接将过时的依赖项替换为新版本。 检查测试是否通过，查看拉取请求摘要中包含的更改日志和发行说明，然后合并它。 更多信息请参阅“[配置 {% data variables.product.prodname_dependabot %} 版本更新](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)”。 diff --git a/translations/zh-CN/content/code-security/dependabot/index.md b/translations/zh-CN/content/code-security/dependabot/index.md index cb1f4984f9..2cfeef9d87 100644 --- a/translations/zh-CN/content/code-security/dependabot/index.md +++ b/translations/zh-CN/content/code-security/dependabot/index.md @@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot diff --git a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index 722d2e48bd..86519f787b 100644 --- a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -9,7 +9,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -36,7 +36,7 @@ topics: * {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new vulnerability record is added, it scans all existing repositories and generates an alert for each vulnerable repository. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." * {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)." - {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% ifversion ghes or ghae-issue-4864 %} and synchronized to {% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)." + {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% ifversion ghes or ghae %} and synchronized to {% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)." ## Do {% data variables.product.prodname_dependabot_alerts %} only relate to vulnerable dependencies in manifests and lockfiles? 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 21c6e0e3f7..c32115569b 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 @@ -20,7 +20,7 @@ topics: The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Available for all repositories {% endif %} ### Security policy @@ -41,7 +41,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." {% endif %} -{% ifversion ghes < 3.3 or ghae-issue-4864 %} +{% ifversion ghes < 3.3 or ghae %} ### {% data variables.product.prodname_dependabot_alerts %} {% data reusables.dependabot.dependabot-alerts-beta %} @@ -55,7 +55,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ### Dependency graph The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository. @@ -100,13 +100,13 @@ Available only with a license for {% data variables.product.prodname_GH_advanced Automatically detect tokens or credentials that have been checked into a repository. You can view alerts for any secrets that {% data variables.product.company_short %} finds in your code, so that you know which tokens or credentials to treat as compromised. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ### Dependency review 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 or ghae-issue-4554 %} +{% ifversion ghec or ghes > 3.1 or ghae %} ### Security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams {% ifversion ghec %} 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 ebb6dbe2c8..dd6785e84c 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 @@ -33,7 +33,7 @@ You can create a default security policy that will display in any of your organi {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph {% 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. @@ -51,7 +51,7 @@ You can create a default security policy that will display in any of your organi For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Managing dependency review @@ -138,7 +138,7 @@ 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 fpt or ghes > 3.1 or ghec or ghae-issue-4554 %}{% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae-issue-4554 %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %} +{% ifversion fpt or ghes > 3.1 or ghec or ghae %}{% ifversion ghes > 3.1 or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %} {% ifversion ghec %} diff --git a/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md b/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md index 6ee9dc430b..8b9288bdea 100644 --- a/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md +++ b/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md @@ -44,7 +44,7 @@ From the main page of your repository, click **{% octicon "gear" aria-label="The For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)." -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing the dependency graph {% ifversion fpt or ghec %} @@ -61,7 +61,7 @@ For more information, see "[Exploring the dependencies of a repository](/code-se {% endif %} -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## Managing {% data variables.product.prodname_dependabot_alerts %} {% data variables.product.prodname_dependabot_alerts %} are generated when {% data variables.product.prodname_dotcom %} identifies a dependency in the dependency graph with a vulnerability. {% ifversion fpt or ghec %}You can enable {% data variables.product.prodname_dependabot_alerts %} for any repository.{% endif %} @@ -75,11 +75,11 @@ For more information, see "[Exploring the dependencies of a repository](/code-se {% data reusables.dependabot.dependabot-alerts-beta %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[Managing security and analysis settings for your personal account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account){% endif %}." +For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account){% endif %}." {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} ## Managing dependency review Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." 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 58b79f6752..33a07b0d55 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 @@ -1,13 +1,13 @@ --- title: 关于安全概述 intro: 您可以在一个位置查看、筛选和排序组织或团队拥有的存储库的安全警报：“安全概述”页。 -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' redirect_from: - /code-security/security-overview/exploring-security-alerts versions: fpt: '*' - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' type: how_to @@ -22,7 +22,7 @@ topics: shortTitle: 关于安全概述 --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} @@ -69,7 +69,7 @@ shortTitle: 关于安全概述 {% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} ### 关于企业级安全性概述 -在企业级别，安全性概述显示企业的综合和存储库特定的安全信息。 您可以查看企业拥有的具有安全警报的存储库，也可以查看整个企业的所有 {% data variables.product.prodname_secret_scanning %} 警报。 +在企业级别，安全性概述显示企业的综合和存储库特定的安全信息。 您可以查看企业拥有的具有安全警报的存储库，查看所有安全警报或整个企业中特定于安全功能的警报。 企业中组织的组织所有者和安全管理员对企业级安全概述的访问权限也有限。 他们只能查看他们具有完全访问权限的组织的存储库和警报。 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 0a3d0600a0..f8c455db64 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 @@ -1,10 +1,10 @@ --- title: 筛选安全性概述中的警报 intro: 使用筛选器查看特定类别的警报 -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' versions: - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' type: how_to @@ -17,7 +17,7 @@ topics: shortTitle: 筛选警报 --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} diff --git a/translations/zh-CN/content/code-security/security-overview/index.md b/translations/zh-CN/content/code-security/security-overview/index.md index 3fe12634bd..5eb9b22459 100644 --- a/translations/zh-CN/content/code-security/security-overview/index.md +++ b/translations/zh-CN/content/code-security/security-overview/index.md @@ -5,7 +5,7 @@ intro: 在一个位置查看、排序和过滤整个组织的安全警报。 product: '{% data reusables.gated-features.security-center %}' versions: fpt: '*' - ghae: issue-4554 + ghae: '*' ghes: '>3.1' ghec: '*' topics: 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 16524c1a83..e948401af1 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 @@ -1,7 +1,7 @@ --- title: 查看安全性概述 intro: 导航到安全概述中可用的不同视图 -permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for. +permissions: '{% data reusables.security-center.permissions %}' product: '{% data reusables.gated-features.security-center %}' versions: ghae: issue-5503 @@ -17,7 +17,7 @@ topics: shortTitle: 查看安全性概述 --- -{% ifversion ghes < 3.5 or ghae-issue-4554 %} +{% ifversion ghes < 3.5 or ghae %} {% data reusables.security-center.beta %} {% endif %} @@ -28,7 +28,8 @@ shortTitle: 查看安全性概述 1. 要查看有关警报类型的汇总信息，请单击 **Show more（显示更多）**。 ![显示更多按钮](/assets/images/help/organizations/security-overview-show-more-button.png) {% data reusables.organizations.filter-security-overview %} {% if security-overview-views %} -1. 或者，也可以使用左侧边栏按安全功能筛选信息。 在每个页面上，您可以使用特定于每个功能的筛选器来微调搜索。 ![代码扫描特定页面的截图](/assets/images/help/organizations/security-overview-code-scanning-alerts.png) +{% data reusables.organizations.security-overview-feature-specific-page %} + ![代码扫描特定页面的截图](/assets/images/help/organizations/security-overview-code-scanning-alerts.png) ## 查看整个组织中的警报 @@ -42,6 +43,9 @@ shortTitle: 查看安全性概述 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} 1. 在左侧边栏中，单击 {% octicon "shield" aria-label="The shield icon" %} **代码安全性**。 +{% if security-overview-feature-specific-alert-page %} +{% data reusables.organizations.security-overview-feature-specific-page %} +{% endif %} {% endif %} ## 查看仓库的警报 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md index 6c5d8dcc9a..d03c07e432 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md @@ -19,6 +19,8 @@ topics: 端到端软件供应链安全的核心是确保您分发的代码未被篡改。 以前，攻击者专注于针对您使用的依赖项，例如库和框架。 攻击者现在已经扩大了他们的关注点，包括针对用户帐户和构建过程，因此这些系统也必须得到保护。 +For information about features in {% data variables.product.prodname_dotcom %} that can help you secure dependencies, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." + ## 关于这些指南 本系列指南介绍了如何考虑保护端到端供应链：个人帐户、代码和构建流程。 每本指南都解释了该领域的风险，并介绍可帮助您解决该风险的 {% data variables.product.product_name %} 功能。 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/index.md b/translations/zh-CN/content/code-security/supply-chain-security/index.md index eaeba9aeb4..3959ac0d47 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/index.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/index.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependabot 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 1760354052..7e851c9dac 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 @@ -6,7 +6,7 @@ shortTitle: 依赖项审查 versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -37,6 +37,8 @@ redirect_from: 依赖项审查支持与依赖关系图相同的语言和包管理生态系统。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)”。 +For more information on supply chain features available on {% data variables.product.product_name %}, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." + {% ifversion ghec or ghes %} ## 启用依赖项审查 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md index 0518b8bf9f..83672fd238 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md @@ -8,7 +8,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -54,6 +54,10 @@ Other supply chain features on {% data variables.product.prodname_dotcom %} rely {% data variables.product.prodname_dependabot %} cross-references dependency data provided by the dependency graph with the list of known vulnerabilities published in the {% data variables.product.prodname_advisory_database %}, scans your dependencies and generates {% data variables.product.prodname_dependabot_alerts %} when a potential vulnerability is detected. {% endif %} +{% ifversion fpt or ghec or ghes %} +For best practice guides on end-to-end supply chain security including the protection of personal accounts, code, and build processes, see "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)." +{% endif %} + ## Feature overview ### What is the dependency graph @@ -129,7 +133,7 @@ Public repositories: - **Dependency graph**—enabled by default and cannot be disabled. - **Dependency review**—enabled by default and cannot be disabled. - **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. {% data variables.product.prodname_dotcom %} detects vulnerable dependencies and displays information in 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 %}. - You can also enable or disable 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](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/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-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." + You can also enable or disable 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](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." Private repositories: - **Dependency graph**—not enabled by default. The feature can be enabled by repository administrators. For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)." @@ -139,7 +143,7 @@ Private repositories: - **Dependency review**—available in private repositories owned by organizations provided you have a license for {% data variables.product.prodname_GH_advanced_security %} and the dependency graph enabled. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" and "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)." {% endif %} - **{% data variables.product.prodname_dependabot_alerts %}**—not enabled 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. - You can also enable or disable 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](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/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-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." + You can also enable or disable 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](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." Any repository type: - **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)." 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 409595d281..f0b9ba9358 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 @@ -7,7 +7,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: overview topics: @@ -44,6 +44,8 @@ The dependency graph includes all the dependencies of a repository that are deta The dependency graph identifies indirect dependencies{% ifversion fpt or ghec %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}. +For more information on how {% data variables.product.product_name %} helps you understand the dependencies in your environment, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)." + {% ifversion fpt or ghec %} ## Dependents included diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md index 6a97e2ccd0..1aa92c76df 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md @@ -5,7 +5,7 @@ shortTitle: 配置依赖项审查 versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -35,7 +35,7 @@ topics: {% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %} 1. 如果未启用“{% data variables.product.prodname_GH_advanced_security %}”，请单击该功能旁边的 **Enable（启用）**。 ![强调显示"启用"按钮的 GitHub Advanced Security 功能的屏幕截图](/assets/images/help/security/enable-ghas-private-repo.png) -{% elsif ghes or ghae %} +{% elsif ghes %} 为 {% data variables.product.product_location %} 启用依赖关系图并为组织或仓库启用{% data variables.product.prodname_advanced_security %} 时，依赖项审查可用。 更多信息请参阅“[为企业启用 {% data variables.product.prodname_GH_advanced_security %}](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)”。 ### 检查是否启用了依赖关系图 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md index 5498409a17..ea3f7eb81c 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md @@ -6,7 +6,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -25,7 +25,7 @@ shortTitle: 配置依赖关系图 {% ifversion fpt or ghec %} ## About configuring the dependency graph {% endif %} {% ifversion fpt or ghec %}要生成依赖关系图，{% data variables.product.product_name %} 需要对仓库的依赖项清单和锁定文件的只读访问权限。 依赖关系图自动为所有公共仓库生成，您可以选择为私有仓库启用它。 有关查看依赖关系图的更多信息，请参阅“[探索存储库的依赖关系](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)”。{% endif %} -{% ifversion ghes or ghae %} ## Enabling the dependency graph +{% ifversion ghes %} ## Enabling the dependency graph {% data reusables.dependabot.ghes-ghae-enabling-dependency-graph %}{% endif %}{% ifversion fpt or ghec %} ### 为私有仓库启用或禁用依赖关系图 diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index 25c0565ddd..c98252fbef 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -12,7 +12,7 @@ redirect_from: versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md index dea1ad4e18..3c84993150 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md @@ -3,7 +3,7 @@ title: 了解您的软件供应链 versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' topics: - Dependency graph diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md index 6de1b7a25d..0fe9cbaf0e 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md @@ -5,7 +5,7 @@ shortTitle: Troubleshoot dependency graph versions: fpt: '*' ghes: '*' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: @@ -59,4 +59,4 @@ Yes, the dependency graph has two categories of limits: - "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)" - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" - "[Troubleshooting the detection of vulnerable dependencies](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %} -- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} \ No newline at end of file +- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md index 13b0796de8..143a723a10 100644 --- a/translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md +++ b/translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md @@ -42,7 +42,7 @@ shortTitle: 灾难恢复 ## 选项 4：对本地容器化环境使用远程容器和 Docker -如果您的存储库具有 `devconconer.json`，请考虑在 Visual Studio Code 中使用[远程容器扩展](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume)构建并连接到仓库的本地开发容器。 此选项的设置时间将因您本地规格和开发容器设置的复杂性而异。 +If your repository has a `devcontainer.json`, consider using the [Remote-Containers extension](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) in {% data variables.product.prodname_vscode %} to build and attach to a local development container for your repository. 此选项的设置时间将因您本地规格和开发容器设置的复杂性而异。 {% note %} diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md index 34222a4754..2cf8e049fa 100644 --- a/translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md +++ b/translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md @@ -34,7 +34,7 @@ shortTitle: 代码空间中的安全性 ### 身份验证 -您可以使用 Web 浏览器或从 Visual Studio Code 连接到代码空间。 如果从 Visual Studio Code 进行连接，系统将提示您使用 {% data variables.product.product_name %} 进行身份验证。 +You can connect to a codespace using a web browser or from {% data variables.product.prodname_vscode %}. If you connect from {% data variables.product.prodname_vscode_shortname %}, you are prompted to authenticate with {% data variables.product.product_name %}. 每次创建或重新启动代码空间时，都会为其分配一个具有自动到期期的新 {% data variables.product.company_short %} 令牌。 此时间段允许您在代码空间中工作，而无需在典型的工作日内重新进行身份验证，但降低了在停止使用代码空间时使连接保持打开状态的可能性。 @@ -109,4 +109,4 @@ shortTitle: 代码空间中的安全性 #### 使用扩展 -您安装的任何其他 {% data variables.product.prodname_vscode %} 扩展都可能带来更多风险。 为了帮助降低此风险，请确保仅安装受信任的扩展，并使它们始终保持最新。 +您安装的任何其他 {% data variables.product.prodname_vscode_shortname %} 扩展都可能带来更多风险。 为了帮助降低此风险，请确保仅安装受信任的扩展，并使它们始终保持最新。 diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md index 0ff3d6d8cd..e0adf9cf1e 100644 --- a/translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md +++ b/translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md @@ -1,6 +1,6 @@ --- -title: Using GitHub Copilot in Codespaces -intro: You can use Copilot in Codespaces by adding the extension. +title: 在 Codespaces 中使用 GitHub Copilot +intro: 您可以通过添加扩展在 Codespaces 中使用 Copilot。 versions: fpt: '*' ghec: '*' @@ -10,14 +10,14 @@ topics: - Copilot - Visual Studio Code product: '{% data reusables.gated-features.codespaces %}' -shortTitle: Copilot in Codespaces +shortTitle: Codespaces 中的 Copilot redirect_from: - /codespaces/codespaces-reference/using-copilot-in-codespaces --- -## Using {% data variables.product.prodname_copilot %} +## 使用 {% data variables.product.prodname_copilot %} -[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), an AI pair programmer, can be used in any codespace. To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). +[{% data variables.product.prodname_copilot %}](https://copilot.github.com/) 是 AI 对编程工具，可用于任何代码空间。 To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot). -To include {% data variables.product.prodname_copilot_short %}, or other extensions, in all of your codespaces, enable Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." Additionally, to include {% data variables.product.prodname_copilot_short %} in a given project for all users, you can specify `GitHub.copilot` as an extension in your `devcontainer.json` file. For information about configuring a `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)." +要在所有代码空间中包含 {% data variables.product.prodname_copilot_short %} 或其他扩展，请启用“设置同步”。 更多信息请参阅“[为帐户个性化 {% data variables.product.prodname_codespaces %}](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)”。 此外，要在所有用户的给定项目中包含 {% data variables.product.prodname_copilot_short %}，可以在 `devcontainer.json` 文件中指定 `GitHub.copilot` 作为扩展名。 有关配置 `devcontainer.json` 文件的信息，请参阅“[开发容器简介](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)”。 diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md index 00c48172fc..76cfa0e0f6 100644 --- a/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md +++ b/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md @@ -15,13 +15,13 @@ redirect_from: - /codespaces/codespaces-reference/using-the-command-palette-in-codespaces --- -## 关于 {% data variables.product.prodname_vscode %} 命令面板 +## 关于 {% data variables.product.prodname_vscode_command_palette %} -命令调色板是 {% data variables.product.prodname_vscode %} 的重点功能之一，可用于代码空间。 {% data variables.product.prodname_vscode_command_palette %} 允许您访问 {% data variables.product.prodname_codespaces %} 和 {% data variables.product.prodname_vscode %} 的许多命令。 有关使用 {% data variables.product.prodname_vscode_command_palette %} 的更多信息，请参阅 visual Studio Code 文档中的 “[用户界面](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)”。 +命令调色板是 {% data variables.product.prodname_vscode %} 的重点功能之一，可用于代码空间。 {% data variables.product.prodname_vscode_command_palette %} 允许您访问 {% data variables.product.prodname_codespaces %} 和 {% data variables.product.prodname_vscode_shortname %} 的许多命令。 For more information on using the {% data variables.product.prodname_vscode_command_palette_shortname %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the {% data variables.product.prodname_vscode_shortname %} documentation. -## 访问 {% data variables.product.prodname_vscode_command_palette %} +## 访问 {% data variables.product.prodname_vscode_command_palette_shortname %} -您可以通过多种方式访问 {% data variables.product.prodname_vscode_command_palette %}。 +您可以通过多种方式访问 {% data variables.product.prodname_vscode_command_palette_shortname %}。 - Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux)。 @@ -33,7 +33,7 @@ redirect_from: ## {% data variables.product.prodname_github_codespaces %} 命令 -要查看与 {% data variables.product.prodname_github_codespaces %} 相关的所有命令， [访问 {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette)，然后开始键入 "Codespaces"。 +要查看与 {% data variables.product.prodname_github_codespaces %} 相关的所有命令， [访问 {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette)，然后开始键入 "Codespaces"。 ![与代码空间相关的所有命令列表](/assets/images/help/codespaces/codespaces-command-palette.png) @@ -41,13 +41,13 @@ redirect_from: 如果添加新密钥或更换机器类型，则必须停止并重新启动代码空间才能应用更改。 -要暂停或停止代码空间的容器，[访问 {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette)，然后开始键入"stop"。 选择 **Codespaces: Stop Current Codespace（Codespace：停止当前 Codespace）**。 +要暂停或停止代码空间的容器，[访问 {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette)，然后开始键入"stop"。 选择 **Codespaces: Stop Current Codespace（Codespace：停止当前 Codespace）**。 ![停止代码空间的命令](/assets/images/help/codespaces/codespaces-stop.png) ### 从模板添加开发容器 -要从模板添加开发容器，[访问 {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette)，然后开始键入 "dev container"。 选择 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** +要从模板添加开发容器，[访问 {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette)，然后开始键入 "dev container"。 选择 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** ![添加开发容器的命令](/assets/images/help/codespaces/add-prebuilt-container-command.png) @@ -55,14 +55,14 @@ redirect_from: 如果您添加 dev 容器或编辑任何配置文件（`devcontainer.json` 和 `Dockerfile`），则需要重建代码空间才可应用更改。 -要重建容器，[访问 {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette)，然后开始键入 "rebuild"。 选择 **Codespaces: Rebuild Container（代码空间：重建容器）**。 +要重建容器，[访问 {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette)，然后开始键入 "rebuild"。 选择 **Codespaces: Rebuild Container（代码空间：重建容器）**。 ![重建代码空间的命令](/assets/images/help/codespaces/codespaces-rebuild.png) ### Codespaces 日志 -可以使用 {% data variables.product.prodname_vscode_command_palette %} 访问代码空间创建日志，也可以使用它导出所有日志。 +可以使用 {% data variables.product.prodname_vscode_command_palette_shortname %} 访问代码空间创建日志，也可以使用它导出所有日志。 -要检索 Codespaces 的日志，[访问 {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette)，然后开始键入 "log"。 选择 **Codespaces: Export Logs（Codespaces：导出日志）**以导出所有与 Codespaces 相关的日志，或选择 **Codespaces: View Creation Logs（Codespaces：查看创建日志）**以查看与设置相关的日志。 +要检索 Codespaces 的日志，[访问 {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette)，然后开始键入 "log"。 选择 **Codespaces: Export Logs（Codespaces：导出日志）**以导出所有与 Codespaces 相关的日志，或选择 **Codespaces: View Creation Logs（Codespaces：查看创建日志）**以查看与设置相关的日志。 ![访问日志的命令](/assets/images/help/codespaces/codespaces-logs.png) diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 88a89871c4..271ce10ace 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -35,7 +35,7 @@ shortTitle: 创建代码空间 有关代码空间生命周期的更多信息，请参阅“[代码空间生命周期](/codespaces/developing-in-codespaces/codespaces-lifecycle)”。 -如果要将 Git 挂钩用于代码空间，则应在步骤 4 中使用 [`devcontainer.json` 生命周期脚本](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)设置挂钩，例如 `postCreateCommand`。 由于代码空间容器是在克隆仓库后创建的，因此在容器映像中配置的任何 [git template directory](https://git-scm.com/docs/git-init#_template_directory) 将不适用于代码空间。 在创建代码空间后，必须改为安装挂钩。 有关使用 `postCreateCommand` 的更多信息，请参阅 visual Studio Code 文档中的 [`devcontainer.json` 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) 。 +如果要将 Git 挂钩用于代码空间，则应在步骤 4 中使用 [`devcontainer.json` 生命周期脚本](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)设置挂钩，例如 `postCreateCommand`。 由于代码空间容器是在克隆仓库后创建的，因此在容器映像中配置的任何 [git template directory](https://git-scm.com/docs/git-init#_template_directory) 将不适用于代码空间。 在创建代码空间后，必须改为安装挂钩。 For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.codespaces.use-visual-studio-features %} diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md index a985c3a36c..ff505fbe49 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md @@ -33,7 +33,7 @@ shortTitle: Develop in a codespace 4. Panels - This is where you can see output and debug information, as well as the default place for the integrated Terminal. 5. Status Bar - This area provides you with useful information about your codespace and project. For example, the branch name, configured ports, and more. -For more information on using {% data variables.product.prodname_vscode %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode %} documentation. +For more information on using {% data variables.product.prodname_vscode_shortname %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.codespaces.connect-to-codespace-from-vscode %} @@ -54,7 +54,7 @@ For more information on using {% data variables.product.prodname_vscode %}, see ### Using the {% data variables.product.prodname_vscode_command_palette %} -The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)." +The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette_shortname %} in {% data variables.product.prodname_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)." ## Navigating to an existing codespace diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md index 59eb5ed129..3b81563de2 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md @@ -20,17 +20,17 @@ shortTitle: Visual Studio Code ## About {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %} -You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. To use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}, you need to install the {% data variables.product.prodname_github_codespaces %} extension. For more information on setting up Codespaces in {% data variables.product.prodname_vscode %}, see "[Prerequisites](#prerequisites)." +You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. To use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode_shortname %}, you need to install the {% data variables.product.prodname_github_codespaces %} extension. For more information on setting up Codespaces in {% data variables.product.prodname_vscode_shortname %}, see "[Prerequisites](#prerequisites)." -By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." +By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode_shortname %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_codespaces %}](/codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces)." -If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." +If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode_shortname %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." ## Prerequisites -To develop in a codespace directly in {% data variables.product.prodname_vscode %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode %} October 2020 Release 1.51 or later. +To develop in a codespace directly in {% data variables.product.prodname_vscode_shortname %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode_shortname %} October 2020 Release 1.51 or later. -Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode %} documentation. +Use the {% data variables.product.prodname_vscode_marketplace %} to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode_shortname %} documentation. {% mac %} @@ -40,8 +40,8 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png) -1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. -1. Sign in to {% data variables.product.product_name %} to approve the extension. +2. To authorize {% data variables.product.prodname_vscode_shortname %} to access your account on {% data variables.product.product_name %}, click **Allow**. +3. Sign in to {% data variables.product.product_name %} to approve the extension. {% endmac %} @@ -56,28 +56,28 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% ![Signing in to view {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png) -1. To authorize {% data variables.product.prodname_vscode %} to access your account on {% data variables.product.product_name %}, click **Allow**. +1. To authorize {% data variables.product.prodname_vscode_shortname %} to access your account on {% data variables.product.product_name %}, click **Allow**. 1. Sign in to {% data variables.product.product_name %} to approve the extension. {% endwindows %} -## Creating a codespace in {% data variables.product.prodname_vscode %} +## Creating a codespace in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.creating-a-codespace-in-vscode %} -## Opening a codespace in {% data variables.product.prodname_vscode %} +## Opening a codespace in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 1. Under "Codespaces", click the codespace you want to develop in. 1. Click the Connect to Codespace icon. - ![The Connect to Codespace icon in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) + ![The Connect to Codespace icon in {% data variables.product.prodname_vscode_shortname %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png) -## Changing the machine type in {% data variables.product.prodname_vscode %} +## Changing the machine type in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.codespaces-machine-types %} You can change the machine type of your codespace at any time. -1. In {% data variables.product.prodname_vscode %}, open the Command Palette (`shift command P` / `shift control P`). +1. In {% data variables.product.prodname_vscode_shortname %}, open the Command Palette (`shift command P` / `shift control P`). 1. Search for and select "Codespaces: Change Machine Type." ![Searching for a branch to create a new {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png) @@ -100,13 +100,13 @@ Use the {% data variables.product.prodname_vs %} Marketplace to install the [{% If you click **No**, or if the codespace is not currently running, the change will take effect the next time the codespace restarts. -## Deleting a codespace in {% data variables.product.prodname_vscode %} +## Deleting a codespace in {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.deleting-a-codespace-in-vscode %} -## Switching to the Insiders build of {% data variables.product.prodname_vscode %} +## Switching to the Insiders build of {% data variables.product.prodname_vscode_shortname %} -You can use the [Insiders Build of Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_codespaces %}. +You can use the [Insiders Build of {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_codespaces %}. 1. In bottom left of your {% data variables.product.prodname_codespaces %} window, select **{% octicon "gear" aria-label="The settings icon" %} Settings**. 2. From the list, select "Switch to Insiders Version". diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md index 089a99a913..68efad7449 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md @@ -24,6 +24,7 @@ You can work with {% data variables.product.prodname_codespaces %} in the {% da - [Delete a codespace](#delete-a-codespace) - [SSH into a codespace](#ssh-into-a-codespace) - [Open a codespace in {% data variables.product.prodname_vscode %}](#open-a-codespace-in-visual-studio-code) +- [Open a codespace in JupyterLab](#open-a-codespace-in-jupyterlab) - [Copying a file to/from a codespace](#copy-a-file-tofrom-a-codespace) - [Modify ports in a codespace](#modify-ports-in-a-codespace) - [Access codespace logs](#access-codespace-logs) @@ -113,6 +114,12 @@ gh codespace code -c codespace-name For more information, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code)." +### Open a codespace in JupyterLab + +```shell +gh codespace jupyter -c codespace-name +``` + ### Copy a file to/from a codespace ```shell diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md index f442e18f1d..f495894ca5 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md @@ -19,7 +19,7 @@ shortTitle: 源控制 您可以直接在代码空间内执行所需的所有 Git 操作。 例如，您可以从远程仓库获取更改、切换分支、创建新分支、提交和推送更改，以及创建拉取请求。 您可以使用代码空间内的集成终端输入 Git 命令，也可以单击图标和菜单选项以完成所有最常见的 Git 任务。 本指南解释如何使用图形用户界面来控制源代码。 -在 {% data variables.product.prodname_github_codespaces %} 中的源控制使用与 {% data variables.product.prodname_vscode %} 相同的工作流程。 更多信息请参阅 {% data variables.product.prodname_vscode %} 文档“[在 VS 代码中使用版本控制](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)”。 +在 {% data variables.product.prodname_github_codespaces %} 中的源控制使用与 {% data variables.product.prodname_vscode %} 相同的工作流程。 For more information, see the {% data variables.product.prodname_vscode_shortname %} documentation "[Using Version Control in {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)." 使用 {% data variables.product.prodname_github_codespaces %} 更新文件的典型工作流程将是： diff --git a/translations/zh-CN/content/codespaces/getting-started/deep-dive.md b/translations/zh-CN/content/codespaces/getting-started/deep-dive.md index 1e0b30c10c..8a7783e8e2 100644 --- a/translations/zh-CN/content/codespaces/getting-started/deep-dive.md +++ b/translations/zh-CN/content/codespaces/getting-started/deep-dive.md @@ -46,13 +46,13 @@ topics: ### 步骤 3：连接到代码空间 -创建容器并运行任何其他初始化后，您将连接到代码空间。 如果需要，您可以通过 Web 和/或 [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code) 连接。 +创建容器并运行任何其他初始化后，您将连接到代码空间。 You can connect to it through the web or via [{% data variables.product.prodname_vscode_shortname %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed. ### 步骤 4：创建后设置 连接到代码空间后，您的自动设置可能会根据您在 `devcontainer.json` 文件中指定的配置继续构建。 您可能会看到 `postCreateCommand` 和 `postAttachCommand` 运行。 -如果要在代码空间中使用 Git 挂钩，请使用 [`devcontainer.json` 生命周期脚本](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)设置挂钩，例如 `postCreateCommand`。 更多信息请参阅 Visual Studio Code 文档中的 [`devcontainer.json` 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) 。 +如果要在代码空间中使用 Git 挂钩，请使用 [`devcontainer.json` 生命周期脚本](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)设置挂钩，例如 `postCreateCommand`。 For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. 如果您有一个用于 {% data variables.product.prodname_codespaces %} 的公共 dotfile 存储库，则可以启用它以用于新的代码空间。 启用后，您的 dotfile 将被克隆到容器中，并且将调用安装脚本。 更多信息请参阅“[为帐户个性化 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)”。 @@ -67,7 +67,7 @@ topics: {% note %} -**注意：**除非已启用 [Auto Save（自动保存）](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save)，否则不会自动保存 {% data variables.product.prodname_vscode %} 代码空间中的更改。 +**注意：**除非已启用 [Auto Save（自动保存）](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save)，否则不会自动保存 {% data variables.product.prodname_vscode_shortname %} 代码空间中的更改。 {% endnote %} ### 关闭或停止代码空间 @@ -93,7 +93,7 @@ topics: ## 提交和推送更改 -默认情况下，Git 在代码空间中可用，因此您可以依赖现有的 Git 工作流程。 您可以通过终端或使用 [Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol) 的源代码管理 UI 在代码空间中使用 Git。 更多信息请参阅“[在代码空间中使用源控制](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)”。 +默认情况下，Git 在代码空间中可用，因此您可以依赖现有的 Git 工作流程。 You can work with Git in your codespace either via the Terminal or by using [{% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. 更多信息请参阅“[在代码空间中使用源控制](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)”。 ![在代码空间终端中运行 git 状态](/assets/images/help/codespaces/git-status.png) @@ -107,9 +107,9 @@ topics: ## 使用扩展个性化您的代码空间 -在代码空间中使用 {% data variables.product.prodname_vscode %} 可以访问 {% data variables.product.prodname_vscode %} 市场，以便您可以添加所需的任何扩展。 有关扩展如何在 {% data variables.product.prodname_codespaces %} 中运行的信息，请参阅 {% data variables.product.prodname_vscode %} 文档中的[支持远程开发和 GitHub 代码空间](https://code.visualstudio.com/api/advanced-topics/remote-extensions) 。 +Using {% data variables.product.prodname_vscode_shortname %} in your codespace gives you access to the {% data variables.product.prodname_vscode_marketplace %} so that you can add any extensions you need. 有关扩展如何在 {% data variables.product.prodname_codespaces %} 中运行的信息，请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的[支持远程开发和 GitHub 代码空间](https://code.visualstudio.com/api/advanced-topics/remote-extensions) 。 -如果您已使用 {% data variables.product.prodname_vscode %}，则可以使用[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)在本地实例和您创建的任何 {% data variables.product.prodname_codespaces %} 之间自动同步扩展程序、设置、主题和键盘快捷键。 +如果您已使用 {% data variables.product.prodname_vscode_shortname %}，则可以使用[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)在本地实例和您创建的任何 {% data variables.product.prodname_codespaces %} 之间自动同步扩展程序、设置、主题和键盘快捷键。 ## 延伸阅读 diff --git a/translations/zh-CN/content/codespaces/getting-started/quickstart.md b/translations/zh-CN/content/codespaces/getting-started/quickstart.md index 133be8baec..5eb2d0faa4 100644 --- a/translations/zh-CN/content/codespaces/getting-started/quickstart.md +++ b/translations/zh-CN/content/codespaces/getting-started/quickstart.md @@ -72,7 +72,7 @@ redirect_from: ## 使用扩展进行个性化设置 -在代码空间内，您可以访问 Visual Studio Code Marketplace。 在本示例中，您将安装可更改主题的扩展，但您可以安装对工作流程有用的任何扩展。 +Within a codespace, you have access to the {% data variables.product.prodname_vscode_marketplace %}. 在本示例中，您将安装可更改主题的扩展，但您可以安装对工作流程有用的任何扩展。 1. 在左侧栏中，单击扩展图标。 @@ -84,7 +84,7 @@ redirect_from: ![选择 fairyfloss 主题](/assets/images/help/codespaces/fairyfloss.png) -4. 在当前代码空间中对编辑器设置所做的更改，如主题和键盘绑定，将通过 [Settings Sync（设置同步）](https://code.visualstudio.com/docs/editor/settings-sync)自动同步到您打开的任何其他代码空间以及登录到您 GitHub 帐户的任何 Visual Studio Code 实例。 +4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to any other codespaces you open and any instances of {% data variables.product.prodname_vscode %} that are signed into your GitHub account. ## 后续步骤 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 0a97f25477..72ccdb769d 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 @@ -41,7 +41,7 @@ topics: ## 删除未使用的代码空间 -您的用户可以在 https://github.com/codespaces 和 Visual Studio Code 中删除其代码空间。 要减小代码空间的大小，用户可以使用终端或从 Visual Studio Code 中手动删除文件。 +Your users can delete their codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, users can manually delete files using the terminal or from within {% data variables.product.prodname_vscode_shortname %}. {% note %} diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md index 20b9f9bf62..3e48e427ec 100644 --- a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md +++ b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md @@ -25,7 +25,7 @@ redirect_from: 若要创建定义了自定义权限的代码空间，必须使用下列方法之一： * {% data variables.product.prodname_dotcom %} web UI * [{% data variables.product.prodname_dotcom %} CLI](https://github.com/cli/cli/releases/latest) 2.5.2 或更高版本 -* [{% data variables.product.prodname_github_codespaces %} Visual Studio Code 扩展](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 或更高版本 +* [{% data variables.product.prodname_github_codespaces %} {% data variables.product.prodname_vscode %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 or later ## 设置其他存储库权限 diff --git a/translations/zh-CN/content/codespaces/overview.md b/translations/zh-CN/content/codespaces/overview.md index 3ed3de03e6..1800b80d11 100644 --- a/translations/zh-CN/content/codespaces/overview.md +++ b/translations/zh-CN/content/codespaces/overview.md @@ -34,7 +34,7 @@ topics: 如果不添加开发容器配置， {% data variables.product.prodname_codespaces %} 会将存储库克隆到具有默认代码空间映像的环境中，该映像包含许多工具、语言和运行时环境。 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)”。 -您还可以通过使用公共 [dotfiles](https://dotfiles.github.io/tutorials/) 存储库和[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)来个性化代码空间环境的各个方面。 个性化设置可以包括 shell 首选项、其他工具、编辑器设置和 VS Code 扩展。 更多信息请参阅“[自定义代码空间](/codespaces/customizing-your-codespace)”。 +您还可以通过使用公共 [dotfiles](https://dotfiles.github.io/tutorials/) 存储库和[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)来个性化代码空间环境的各个方面。 Personalization can include shell preferences, additional tools, editor settings, and {% data variables.product.prodname_vscode_shortname %} extensions. 更多信息请参阅“[自定义代码空间](/codespaces/customizing-your-codespace)”。 ## 关于 {% data variables.product.prodname_codespaces %} 的计费 diff --git a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md index 793b90ac48..0d6d194897 100644 --- a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md +++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md @@ -94,7 +94,7 @@ permissions: People with admin access to a repository can configure prebuilds fo ## 配置要包含在预构建中的耗时任务 -您可以在 `devcontainer.json` 中使用 `onCreateCommand` 和 `updateContentCommand` 命令，以将耗时的过程作为预构建模板创建的一部分包括在内。 更多信息请参阅 Visual Studio Code 文档“[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)”。 +您可以在 `devcontainer.json` 中使用 `onCreateCommand` 和 `updateContentCommand` 命令，以将耗时的过程作为预构建模板创建的一部分包括在内。 For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)." `onCreateCommand` 仅在创建预构建模板时运行一次，而 `updateContentCommand` 在模板创建和后续模板更新时运行。 增量构建应包含在 `updateContentCommand` 中，因为它们表示项目的源代码，并且需要包含在每个预构建模板更新中。 diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md index d43eb627af..91af0f889a 100644 --- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md +++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md @@ -110,7 +110,7 @@ RUN apt-get update && bash /tmp/library-scripts/github-debian.sh } ``` -有关在开发容器配置中使用 Dockerfile 的详细信息，请参阅 {% data variables.product.prodname_vscode %} 文档“[创建开发容器](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)”。 +For more information about using a Dockerfile in a dev container configuration, see the {% data variables.product.prodname_vscode_shortname %} documentation "[Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)." ## 使用默认开发容器配置 @@ -122,7 +122,7 @@ RUN apt-get update && bash /tmp/library-scripts/github-debian.sh ## 使用预定义的开发容器配置 -可以从预定义配置列表中进行选择，以便为存储库创建开发容器配置。 这些配置为特定项目类型提供了常见设置，并可以帮助您快速开始使用已具有相应容器选项、{% data variables.product.prodname_vscode %} 设置和应安装的 {% data variables.product.prodname_vscode %} 扩展的配置。 +可以从预定义配置列表中进行选择，以便为存储库创建开发容器配置。 These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode_shortname %} settings, and {% data variables.product.prodname_vscode_shortname %} extensions that should be installed. 如果您需要一些额外的扩展性，使用预先定义的配置是一个好主意。 您也可以从预定义的配置开始，然后根据项目的需要对其进行修改。 @@ -192,9 +192,9 @@ RUN apt-get update && bash /tmp/library-scripts/github-debian.sh ### 编辑 devcontainer.json 文件 -您可以在 `devcontainer.json` 文件中添加和编辑支持的配置键，以指定代码空间环境的各个方面，例如将安装哪些 {% data variables.product.prodname_vscode %} 扩展。 {% data reusables.codespaces.more-info-devcontainer %} +You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode_shortname %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %} -`devcontainer.json` 文件是使用 JSONC 格式编写的。 这允许您在配置文件中包含注释。 更多信息请参阅 {% data variables.product.prodname_vscode %} 文档中的“[使用 Visual Studio Code 编辑 JSON](https://code.visualstudio.com/docs/languages/json#_json-with-comments)”。 +`devcontainer.json` 文件是使用 JSONC 格式编写的。 这允许您在配置文件中包含注释。 For more information, see "[Editing JSON with {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% note %} @@ -202,11 +202,11 @@ RUN apt-get update && bash /tmp/library-scripts/github-debian.sh {% endnote %} -### Visual Studio Code 的编辑器设置 +### Editor settings for {% data variables.product.prodname_vscode_shortname %} {% data reusables.codespaces.vscode-settings-order %} -您可以在两个地方定义 {% data variables.product.prodname_vscode %} 的默认编辑器设置。 +You can define default editor settings for {% data variables.product.prodname_vscode_shortname %} in two places. * 在存储库的 `.vscode/settings.json` 文件中定义的编辑器设置将作为代码空间中_工作区_范围的设置进行应用。 * `devcontainer.json` 文件的 `settings` 键中定义的编辑器设置在代码空间中用作 _Remote [Codespaces]_ 范围的设置。 diff --git a/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md b/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md index 087e959b0e..2671daa017 100644 --- a/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md +++ b/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md @@ -27,7 +27,7 @@ The {% data variables.product.prodname_serverless %} introduces a lightweight ed The {% data variables.product.prodname_serverless %} is available to everyone for free on {% data variables.product.prodname_dotcom_the_website %}. -The {% data variables.product.prodname_serverless %} provides many of the benefits of {% data variables.product.prodname_vscode %}, such as search, syntax highlighting, and a source control view. You can also use Settings Sync to share your own {% data variables.product.prodname_vscode %} settings with the editor. For more information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode %} documentation. +The {% data variables.product.prodname_serverless %} provides many of the benefits of {% data variables.product.prodname_vscode %}, such as search, syntax highlighting, and a source control view. You can also use Settings Sync to share your own {% data variables.product.prodname_vscode_shortname %} settings with the editor. For more information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation. The {% data variables.product.prodname_serverless %} runs entirely in your browser’s sandbox. The editor doesn’t clone the repository, but instead uses the [GitHub Repositories extension](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) to carry out most of the functionality that you will use. Your work is saved in the browser’s local storage until you commit it. You should commit your changes regularly to ensure that they're always accessible. @@ -49,7 +49,7 @@ Both the {% data variables.product.prodname_serverless %} and {% data variables. | **Start up** | The {% data variables.product.prodname_serverless %} opens instantly with a key-press and you can start using it right away, without having to wait for additional configuration or installation. | When you create or resume a codespace, the codespace is assigned a VM and the container is configured based on the contents of a `devcontainer.json` file. This set up may take a few minutes to create the environment. For more information, see "[Creating a Codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." | | **Compute** | There is no associated compute, so you won’t be able to build and run your code or use the integrated terminal. | With {% data variables.product.prodname_codespaces %}, you get the power of dedicated VM on which you can run and debug your application.| | **Terminal access** | None. | {% data variables.product.prodname_codespaces %} provides a common set of tools by default, meaning that you can use the Terminal exactly as you would in your local environment.| -| **Extensions** | Only a subset of extensions that can run in the web will appear in the Extensions View and can be installed. For more information, see "[Using extensions](#using-extensions)."| With Codespaces, you can use most extensions from the Visual Studio Code Marketplace.| +| **Extensions** | Only a subset of extensions that can run in the web will appear in the Extensions View and can be installed. For more information, see "[Using extensions](#using-extensions)."| With Codespaces, you can use most extensions from the {% data variables.product.prodname_vscode_marketplace %}.| ### Continue working on {% data variables.product.prodname_codespaces %} @@ -61,9 +61,9 @@ To continue your work in a codespace, click **Continue Working on…** and selec ## Using source control -When you use the {% data variables.product.prodname_serverless %}, all actions are managed through the Source Control View, which is located in the Activity Bar on the left hand side. For more information on the Source Control View, see "[Version Control](https://code.visualstudio.com/docs/editor/versioncontrol)" in the {% data variables.product.prodname_vscode %} documentation. +When you use the {% data variables.product.prodname_serverless %}, all actions are managed through the Source Control View, which is located in the Activity Bar on the left hand side. For more information on the Source Control View, see "[Version Control](https://code.visualstudio.com/docs/editor/versioncontrol)" in the {% data variables.product.prodname_vscode_shortname %} documentation. -Because the web-based editor uses the GitHub Repositories extension to power its functionality, you can switch branches without needing to stash changes. For more information, see "[GitHub Repositories](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" in the {% data variables.product.prodname_vscode %} documentation. +Because the web-based editor uses the GitHub Repositories extension to power its functionality, you can switch branches without needing to stash changes. For more information, see "[GitHub Repositories](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension)" in the {% data variables.product.prodname_vscode_shortname %} documentation. ### Create a new branch @@ -88,9 +88,9 @@ You can use the {% data variables.product.prodname_serverless %} to work with an ## Using extensions -The {% data variables.product.prodname_serverless %} supports {% data variables.product.prodname_vscode %} extensions that have been specifically created or updated to run in the web. These extensions are known as "web extensions". To learn how you can create a web extension or update your existing extension to work for the web, see "[Web extensions](https://code.visualstudio.com/api/extension-guides/web-extensions)" in the {% data variables.product.prodname_vscode %} documentation. +The {% data variables.product.prodname_serverless %} supports {% data variables.product.prodname_vscode_shortname %} extensions that have been specifically created or updated to run in the web. These extensions are known as "web extensions". To learn how you can create a web extension or update your existing extension to work for the web, see "[Web extensions](https://code.visualstudio.com/api/extension-guides/web-extensions)" in the {% data variables.product.prodname_vscode_shortname %} documentation. -Extensions that can run in the {% data variables.product.prodname_serverless %} will appear in the Extensions View and can be installed. If you use Settings Sync, any compatible extensions are also installed automatically. For information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode %} documentation. +Extensions that can run in the {% data variables.product.prodname_serverless %} will appear in the Extensions View and can be installed. If you use Settings Sync, any compatible extensions are also installed automatically. For information, see "[Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync)" in the {% data variables.product.prodname_vscode_shortname %} documentation. ## Troubleshooting @@ -104,5 +104,5 @@ If you have issues opening the {% data variables.product.prodname_serverless %}, ### Known limitations - The {% data variables.product.prodname_serverless %} is currently supported in Chrome (and various other Chromium-based browsers), Edge, Firefox, and Safari. We recommend that you use the latest versions of these browsers. -- Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "[Known limitations and adaptations](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" section of the {% data variables.product.prodname_vscode %} documentation. +- Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "[Known limitations and adaptations](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations)" section of the {% data variables.product.prodname_vscode_shortname %} documentation. - `.` may not work to open the {% data variables.product.prodname_serverless %} according to your local keyboard layout. In that case, you can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} by changing the URL from `github.com` to `github.dev`. diff --git a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md index 86c1abd921..38ead679c2 100644 --- a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md +++ b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -22,11 +22,11 @@ miniTocMaxHeadingLevel: 3 ![可用计算机类型的列表](/assets/images/help/codespaces/choose-custom-machine-type.png) -如果将 {% data variables.product.prodname_codespaces %} 编辑器首选项设置为“Visual Studio Code for Web”，则“设置代码空间”页面将显示消息“找到预构建的代码空间”（如果正在使用预构建）。 +If you have your {% data variables.product.prodname_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used. ![“找到预构建的代码空间”消息](/assets/images/help/codespaces/prebuilt-codespace-found.png) -同样，如果您的编辑器首选项是“Visual Studio Code”，则当您创建新代码空间时，集成终端将包含消息“您正在使用由存储库的预构建配置定义的预构建代码空间”。 更多信息请参阅“[设置代码空间的默认编辑器](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)”。 +Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. 更多信息请参阅“[设置代码空间的默认编辑器](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)”。 创建代码空间后，可以通过在终端中运行以下 {% data variables.product.prodname_cli %} 命令来检查它是否是从预构建创建的： diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/index.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/index.md index a578e2ad3f..a71d9257ff 100644 --- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/index.md +++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/index.md @@ -16,7 +16,7 @@ children: - /managing-disruptive-comments - /locking-conversations - /limiting-interactions-in-your-repository - - /limiting-interactions-for-your-user-account + - /limiting-interactions-for-your-personal-account - /limiting-interactions-in-your-organization - /tracking-changes-in-a-comment - /managing-how-contributors-report-abuse-in-your-organizations-repository 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-personal-account.md similarity index 92% rename from translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md rename to translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md index 8465020341..f3fa07d5cd 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-personal-account.md @@ -1,5 +1,5 @@ --- -title: 限制用户帐户的交互 +title: 限制个人帐户的交互 intro: 您可以在个人帐户拥有的所有公共仓库中对某些用户临时限制活动一段时间。 versions: fpt: '*' @@ -7,6 +7,7 @@ versions: permissions: Anyone can limit interactions for their own personal account. redirect_from: - /github/building-a-strong-community/limiting-interactions-for-your-user-account + - /communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account topics: - Community shortTitle: 限制帐户中的交互 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 e754fc2aae..177828985c 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 @@ -22,7 +22,7 @@ shortTitle: 限制仓库中的交互 {% data reusables.community.types-of-interaction-limits %} -您也可以为个人帐户或组织拥有的所有仓库启用或活动限制。 如果启用了用户范围或组织范围的限制，则不能限制帐户拥有的单个仓库的活动。 更多信息请参阅“[限制个人帐户的交互](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account)”和“[限制组织中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)”。 +您也可以为个人帐户或组织拥有的所有仓库启用或活动限制。 如果启用了用户范围或组织范围的限制，则不能限制帐户拥有的单个仓库的活动。 更多信息请参阅“[限制个人帐户的交互](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account)”和“[限制组织中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)”。 ## 限制仓库中的交互 diff --git a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md index 2268f0da21..e9f9e7686e 100644 --- a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md +++ b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md @@ -36,9 +36,7 @@ shortTitle: 关于模板 通过议题表单，您可以使用 {% data variables.product.prodname_dotcom %} 表单架构创建具有 Web 表单字段的模板。 当贡献者使用议题表单打开议题时，表单输入将转换为标准 Markdown 议题评论。 您可以指定不同的输入类型并根据需要设置输入，以帮助贡献者打开仓库中可操作的议题。 更多信息请参阅“[为仓库配置议题模板](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)”和“[议题表单的语法](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)”。 {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} {% data reusables.repositories.issue-template-config %}更多信息请参阅“[为仓库配置议题模板](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser)”。 -{% endif %} 议题模板存储在仓库的默认分支的隐藏目录 `.github/ISSUE_TEMPLATE` 中。 如果您在另一个分支中创建模板，协作者将无法使用。 议题模板文件名不区分大小写，并且需要 *.md* 扩展名。{% ifversion fpt or ghec %} 使用议题表单创建的议题模板需要 *.yml* 扩展名。{% endif %} {% data reusables.repositories.valid-community-issues %} diff --git a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md index 819c208778..5843a7c2e4 100644 --- a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md +++ b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md @@ -21,12 +21,8 @@ shortTitle: 配置 {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} - ## 创建议题模板 -{% endif %} - {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 3. 在“Features（功能）”部分的“Issues（议题）”下，单击 **Set up templates（设置模板）**。 ![开始模板设置按钮](/assets/images/help/repository/set-up-templates.png) @@ -62,7 +58,6 @@ shortTitle: 配置 {% endif %} -{% ifversion fpt or ghae or ghes or ghec %} ## 配置模板选择器 {% data reusables.repositories.issue-template-config %} @@ -99,7 +94,6 @@ contact_links: {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -{% endif %} ## 延伸阅读 diff --git a/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md b/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md index 1912d44edc..56c06d64fb 100644 --- a/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md +++ b/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md @@ -17,7 +17,7 @@ shortTitle: 配置默认编辑器 - [Atom](https://atom.io/) - [MacVim](https://macvim-dev.github.io/macvim/) -- [Visual Studio Code](https://code.visualstudio.com/) +- [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) - [Visual Studio Codium](https://vscodium.com/) - [Sublime Text](https://www.sublimetext.com/) - [BBEdit](http://www.barebones.com/products/bbedit/) @@ -44,7 +44,7 @@ shortTitle: 配置默认编辑器 {% windows %} - [Atom](https://atom.io/) -- [Visual Studio Code](https://code.visualstudio.com/) +- [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) - [Visual Studio Codium](https://vscodium.com/) - [Sublime Text](https://www.sublimetext.com/) - [ColdFusion Builder](https://www.adobe.com/products/coldfusion-builder.html) 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 b213198207..5e2d276dce 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 @@ -89,7 +89,7 @@ shortTitle: 应用程序创建查询参数 | [`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/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 %} +| [`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 or ghec %} | `vulnerability_alerts` | 授予接收存储库中易受攻击的依赖项 {% data variables.product.prodname_dependabot_alerts %}。 请参阅“[关于 {% data variables.product.prodname_dependabot_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 e5f2a0c328..820eaf1b4b 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 @@ -239,8 +239,8 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre * [列出部署](/rest/reference/deployments#list-deployments) * [创建部署](/rest/reference/deployments#create-a-deployment) -* [获取部署](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %} -* [删除部署](/rest/reference/deployments#delete-a-deployment){% endif %} +* [获取部署](/rest/reference/deployments#get-a-deployment) +* [删除部署](/rest/reference/deployments#delete-a-deployment) #### 事件 @@ -422,14 +422,12 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre * [删除组织的预接收挂钩实施](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} #### 组织团队项目 * [列出团队项目](/rest/reference/teams#list-team-projects) * [检查项目的团队权限](/rest/reference/teams#check-team-permissions-for-a-project) * [添加或更新团队项目权限](/rest/reference/teams#add-or-update-team-project-permissions) * [从团队删除项目](/rest/reference/teams#remove-a-project-from-a-team) -{% endif %} #### 组织团队仓库 @@ -575,7 +573,7 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre #### 反应 -{% ifversion fpt or ghes or ghae or ghec %}* [删除反应](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [删除反应](/rest/reference/reactions#delete-a-reaction){% endif %} +* [删除反应](/rest/reference/reactions) * [列出提交注释的反应](/rest/reference/reactions#list-reactions-for-a-commit-comment) * [创建提交注释的反应](/rest/reference/reactions#create-reaction-for-a-commit-comment) * [列出议题的反应](/rest/reference/reactions#list-reactions-for-an-issue) @@ -587,13 +585,13 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre * [列出团队讨论注释的反应](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) * [创建团队讨论注释的反应](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) * [列出团队讨论的反应](/rest/reference/reactions#list-reactions-for-a-team-discussion) -* [创建团队讨论的反应](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %} +* [为团队讨论创建反应](/rest/reference/reactions#create-reaction-for-a-team-discussion) * [删除提交注释反应](/rest/reference/reactions#delete-a-commit-comment-reaction) * [删除议题反应](/rest/reference/reactions#delete-an-issue-reaction) * [删除对提交注释的反应](/rest/reference/reactions#delete-an-issue-comment-reaction) * [删除拉取请求注释反应](/rest/reference/reactions#delete-a-pull-request-comment-reaction) * [删除团队讨论反应](/rest/reference/reactions#delete-team-discussion-reaction) -* [删除团队讨论注释反应](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %} +* [删除团队讨论评论反应](/rest/reference/reactions#delete-team-discussion-comment-reaction) #### 仓库 @@ -707,11 +705,9 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre * [获取仓库自述文件](/rest/reference/repos#get-a-repository-readme) * [获取仓库许可](/rest/reference/licenses#get-the-license-for-a-repository) -{% ifversion fpt or ghes or ghae or ghec %} #### 仓库事件调度 * [创建仓库调度事件](/rest/reference/repos#create-a-repository-dispatch-event) -{% 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 e81f5f7f50..94bdb8a9cb 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 @@ -333,7 +333,7 @@ http://127.0.0.1:1234/path * "[对授权请求错误进行故障排除](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)" * "[对 OAuth 应用程序访问令牌请求错误进行故障排除](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)" -* "[设备流错误](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} +* "[设备流错误](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %} * "[令牌到期和撤销](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %} ## 延伸阅读 diff --git a/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md index eec4a49f78..b2ddf4a8d6 100644 --- a/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md +++ b/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md @@ -84,7 +84,7 @@ Keep these ideas in mind when using personal access tokens: * You can perform one-off cURL requests. * You can run personal scripts. * Don't set up a script for your whole team or company to use. -* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %} +* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae or ghec %} * Do set an expiration for your personal access tokens, to help keep your information secure.{% endif %} ## Determining which integration to build diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md index a71679f235..bc200e0243 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md @@ -89,4 +89,4 @@ end * **不建议**使用普通的 `==` 运算符。 像 [`secure_compare`][secure_compare] 这样的方法执行“恒定时间”字符串比较，这有助于减轻针对常规相等运算符的某些定时攻击。 -[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare +[secure_compare]: https://rubydoc.info/github/rack/rack/main/Rack/Utils:secure_compare diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 8d2c487aa3..517f94bf5d 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -1,6 +1,6 @@ --- -title: Web 挂钩事件和有效负载 -intro: 对于每个 web 挂钩事件，您可以查看事件发生的时间、示例有效负载以及有关有效负载对象参数的说明。 +title: Webhook events and payloads +intro: 'For each webhook event, you can review when the event occurs, an example payload, and descriptions about the payload object parameters.' product: '{% data reusables.gated-features.enterprise_account_webhooks %}' redirect_from: - /early-access/integrations/webhooks @@ -14,53 +14,52 @@ versions: ghec: '*' topics: - Webhooks -shortTitle: Web 挂钩事件和有效负载 +shortTitle: Webhook events & payloads --- - {% ifversion fpt or ghec %} {% endif %} {% data reusables.webhooks.webhooks_intro %} -您可以创建订阅此页所列事件的 web 挂钩。 每个 web 挂钩事件都包括 web 挂钩属性的说明和示例有效负载。 更多信息请参阅“[创建 web 挂钩](/webhooks/creating/)”。 +You can create webhooks that subscribe to the events listed on this page. Each webhook event includes a description of the webhook properties and an example payload. For more information, see "[Creating webhooks](/webhooks/creating/)." -## Web 挂钩有效负载对象共有属性 +## Webhook payload object common properties -每个 web 挂钩事件有效负载还包含特定于事件的属性。 您可以在各个事件类型部分中找到这些独特属性。 +Each webhook event payload also contains properties unique to the event. You can find the unique properties in the individual event type sections. -| 键 | 类型 | 描述 | -| -------- | ----- | -------------------------------------------- | -| `action` | `字符串` | 大多数 web 挂钩有效负载都包括 `action` 属性，其中包含触发事件的特定活动。 | -{% data reusables.webhooks.sender_desc %} 此属性包含在每个 web 挂钩有效负载中。 -{% data reusables.webhooks.repo_desc %} 当事件发生源于仓库中的活动时，web 挂钩有效负载包含 `repository` 属性。 +Key | Type | Description +----|------|------------- +`action` | `string` | Most webhook payloads contain an `action` property that contains the specific activity that triggered the event. +{% data reusables.webhooks.sender_desc %} This property is included in every webhook payload. +{% data reusables.webhooks.repo_desc %} Webhook payloads contain the `repository` property when the event occurs from activity in a repository. {% data reusables.webhooks.org_desc %} -{% data reusables.webhooks.app_desc %} 更多信息请参阅“[构建 {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)”。 +{% data reusables.webhooks.app_desc %} For more information, see "[Building {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)." -Web 挂钩事件的独特属性与您使用[事件 API](/rest/reference/activity#events) 时在 `payload` 属性中发现的属性相同。 唯一的例外是 [`push` 事件](#push)。 `push` 事件 web 挂钩有效负载的独特属性与 Events API 中的 `payload` 属性不同。 Web 挂钩有效负载包含更详细的信息。 +The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/rest/reference/activity#events). One exception is the [`push` event](#push). The unique properties of the `push` event webhook payload and the `payload` property in the Events API differ. The webhook payload contains more detailed information. {% tip %} -**注：**有效负载的上限为 25 MB。 如果事件生成了更大的有效负载，web 挂钩将不会触发。 例如，如果同时推送多个分支或标记，这种情况可能会发生在 `create` 事件中。 我们建议监控有效负载的大小以确保成功递送。 +**Note:** Payloads are capped at 25 MB. If your event generates a larger payload, a webhook will not be fired. This may happen, for example, on a `create` event if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery. {% endtip %} -### 递送标头 +### Delivery headers -递送到 web 挂钩已配置 URL 端点的 HTTP POST 有效负载将包含几个特殊标头： +HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers: -| 标头 | 描述 | -| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `X-GitHub-Event` | 触发递送的事件名称。 | -| `X-GitHub-Delivery` | 用于标识递送的 [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier)。{% ifversion ghes or ghae %} -| `X-GitHub-Enterprise-Version` | 发送 HTTP POST 有效负载的 {% data variables.product.prodname_ghe_server %} 实例的版本。 | -| `X-GitHub-Enterprise-Host` | 发送 HTTP POST 有效负载的 {% data variables.product.prodname_ghe_server %} 实例的主机名。{% endif %}{% ifversion not ghae %} -| `X-Hub-Signature` | 如果使用 [`secret`](/rest/reference/repos#create-hook-config-params) 配置了 web 挂钩，则发送此标头。 这是请求正文的 HMAC 十六进制摘要，是使用 SHA-1 哈希函数和作为 HMAC `密钥`的`机密` 生成的。{% ifversion fpt or ghes or ghec %} 提供了`X-Hub-Signature`，以便与现有集成兼容，我们建议您改用更安全的 `X-Hub-Signature-256`。{% endif %}{% endif %} -| `X-Hub-Signature-256` | 如果使用 [`secret`](/rest/reference/repos#create-hook-config-params) 配置了 web 挂钩，则发送此标头。 这是请求正文的 HMAC 十六进制摘要，它是使用 SHA-256 哈希函数和作为 HMAC `key` 的 `secret` 生成的。 | +Header | Description +-------|-------------| +`X-GitHub-Event`| Name of the event that triggered the delivery. +`X-GitHub-Delivery`| A [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) to identify the delivery.{% ifversion ghes or ghae %} +`X-GitHub-Enterprise-Version` | The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload. +`X-GitHub-Enterprise-Host` | The hostname of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.{% endif %}{% ifversion not ghae %} +`X-Hub-Signature`| This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% ifversion fpt or ghes or ghec %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %} +`X-Hub-Signature-256`| This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`. -此外，请求的 `User-Agent` 将含有前缀 `GitHub-Hookshot/`。 +Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`. -### 递送示例 +### Example delivery ```shell > POST /payload HTTP/2 @@ -104,26 +103,26 @@ Web 挂钩事件的独特属性与您使用[事件 API](/rest/reference/activity {% ifversion fpt or ghes > 3.2 or ghae or ghec %} ## branch_protection_rule -与分支保护规则相关的活动。 更多信息请参阅“[关于分支保护规则](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules)”。 +Activity related to a branch protection rule. For more information, see "[About branch protection rules](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules)." -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 对仓库管理至少拥有 `read-only` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with at least `read-only` access on repositories administration -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| --------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是 `created`、`edited` 或 `deleted`。 | -| `rule` | `对象` | 分支保护规则。 包括 `name` 以及适用于与名称匹配的分支的所有 [分支保护设置](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-settings)。 二进制设置是布尔值。 多级配置是 `off`、`non_admins` 或 `everyone` 之一。 执行者和构建列表是字符串数组。 | -| `changes` | `对象` | 如果操作是 `edited`，则为规则的更改。 | +Key | Type | Description +----|------|------------- +`action` |`string` | The action performed. Can be `created`, `edited`, or `deleted`. +`rule` | `object` | The branch protection rule. Includes a `name` and all the [branch protection settings](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-settings) applied to branches that match the name. Binary settings are boolean. Multi-level configurations are one of `off`, `non_admins`, or `everyone`. Actor and build lists are arrays of strings. +`changes` | `object` | If the action was `edited`, the changes to the rule. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.branch_protection_rule.edited }} {% endif %} @@ -131,26 +130,26 @@ Web 挂钩事件的独特属性与您使用[事件 API](/rest/reference/activity {% ifversion ghes > 3.3 %} ## cache_sync -Git 引用已成功同步到缓存副本。 更多信息请参阅“[关于仓库缓存](/admin/enterprise-management/caching-repositories/about-repository-caching)”。 +A Git ref has been successfully synced to a cache replica. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)." -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 +- Repository webhooks +- Organization webhooks -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| ---------------- | ----- | ----------------- | -| `cache_location` | `字符串` | 已更新的缓存服务器的位置。 | -| `ref` | `字符串` | 已更新的引用。 | -| `before` | `字符串` | 缓存副本在更新之前引用的 OID。 | -| `after` | `字符串` | 更新后缓存副本上引用的 OID。 | +Key | Type | Description +----|------|------------- +`cache_location` |`string` | The location of the cache server that has been updated. +`ref` | `string` | The ref that has been updated. +`before` | `string` | The OID of the ref on the cache replica before it was updated. +`after` | `string` | The OID of the ref on the cache replica after the update. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.cache_sync.synced }} {% endif %} @@ -161,13 +160,13 @@ Git 引用已成功同步到缓存副本。 更多信息请参阅“[关于仓 {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %} -### 可用性 +### Availability -- 仓库 web 挂钩只接收仓库中 `created` 和 `completed` 事件类型的有效负载 -- 组织 web 挂钩只接收仓库中 `created` 和 `completed` 事件类型的有效负载 -- 具有 `checks:read` 权限的 {% data variables.product.prodname_github_apps %} 接收应用程序所在仓库中发生的 `created` 和 `completed` 事件的有效负载。 应用程序必须具有 `checks:write` 权限才能接收 `rerequested` 和 `requested_action` 事件类型。 `rerequested` 和 `requested_action` 事件类型有效负载仅发送到被请求的 {% data variables.product.prodname_github_app %}。 具有 `checks:write` 权限的 {% data variables.product.prodname_github_apps %} 会自动订阅此 web 挂钩事件。 +- Repository webhooks only receive payloads for the `created` and `completed` event types in a repository +- Organization webhooks only receive payloads for the `created` and `completed` event types in repositories +- {% data variables.product.prodname_github_apps %} with the `checks:read` permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have the `checks:write` permission to receive the `rerequested` and `requested_action` event types. The `rerequested` and `requested_action` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_apps %} with the `checks:write` are automatically subscribed to this webhook event. -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.check_run_properties %} {% data reusables.webhooks.repo_desc %} @@ -175,7 +174,7 @@ Git 引用已成功同步到缓存副本。 更多信息请参阅“[关于仓 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.check_run.created }} @@ -185,13 +184,13 @@ Git 引用已成功同步到缓存副本。 更多信息请参阅“[关于仓 {% data reusables.apps.undetected-pushes-to-a-forked-repository-for-check-suites %} -### 可用性 +### Availability -- 仓库 web 挂钩只接收仓库中 `completed` 事件类型的有效负载 -- 组织 web 挂钩只接收仓库中 `completed` 事件类型的有效负载 -- 具有 `checks:read` 权限的 {% data variables.product.prodname_github_apps %} 接收应用程序所在仓库中发生的 `created` 和 `completed` 事件的有效负载。 应用程序必须具有 `checks:write` 权限才能接收 `requested` 和 `rerequested` 事件类型。 `requested` 和 `rerequested` 事件类型有效负载仅发送到被请求的 {% data variables.product.prodname_github_app %}。 具有 `checks:write` 权限的 {% data variables.product.prodname_github_apps %} 会自动订阅此 web 挂钩事件。 +- Repository webhooks only receive payloads for the `completed` event types in a repository +- Organization webhooks only receive payloads for the `completed` event types in repositories +- {% data variables.product.prodname_github_apps %} with the `checks:read` permission receive payloads for the `created` and `completed` events that occur in the repository where the app is installed. The app must have the `checks:write` permission to receive the `requested` and `rerequested` event types. The `requested` and `rerequested` event type payloads are only sent to the {% data variables.product.prodname_github_app %} being requested. {% data variables.product.prodname_github_apps %} with the `checks:write` are automatically subscribed to this webhook event. -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.check_suite_properties %} {% data reusables.webhooks.repo_desc %} @@ -199,7 +198,7 @@ Git 引用已成功同步到缓存副本。 更多信息请参阅“[关于仓 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.check_suite.completed }} @@ -207,21 +206,21 @@ Git 引用已成功同步到缓存副本。 更多信息请参阅“[关于仓 {% data reusables.webhooks.code_scanning_alert_event_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `security_events :read` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.code_scanning_alert_event_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} -`sender` | `object` | 如果 `action` 是 `reopened_by_user` 或 `closed_by_user`，则 `sender` 对象将是触发事件的用户。 `sender` 对象对所有其他操作是 {% ifversion fpt or ghec %}`github` {% elsif ghes or ghae %}`github-enterprise` {% else %}空 {% endif %}。 +`sender` | `object` | If the `action` is `reopened_by_user` or `closed_by_user`, the `sender` object will be the user that triggered the event. The `sender` object is {% ifversion fpt or ghec %}`github`{% elsif ghes or ghae %}`github-enterprise`{% else %}empty{% endif %} for all other actions. -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.code_scanning_alert.reopened }} @@ -229,13 +228,13 @@ Git 引用已成功同步到缓存副本。 更多信息请参阅“[关于仓 {% data reusables.webhooks.commit_comment_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `contents` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.commit_comment_properties %} {% data reusables.webhooks.repo_desc %} @@ -243,7 +242,7 @@ Git 引用已成功同步到缓存副本。 更多信息请参阅“[关于仓 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.commit_comment.created }} @@ -252,13 +251,13 @@ Git 引用已成功同步到缓存副本。 更多信息请参阅“[关于仓 {% data reusables.webhooks.content_reference_short_desc %} -Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如果您注册了一个子域 (`https://subdomain.example.com`)，则只有该子域的 URL 才会触发此事件。 如果您注册了一个域 (`https://example.com`)，则该域及所有子域的 URL 都会触发此事件。 请参阅“[创建内容附件](/rest/reference/apps#create-a-content-attachment)”以创建新的内容附件。 +Webhook events are triggered based on the specificity of the domain you register. For example, if you register a subdomain (`https://subdomain.example.com`) then only URLs for the subdomain trigger this event. If you register a domain (`https://example.com`) then URLs for domain and all subdomains trigger this event. See "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" to create a new content attachment. -### 可用性 +### Availability -- 具有 `content_references:write` 权限的 {% data variables.product.prodname_github_apps %} +- {% data variables.product.prodname_github_apps %} with the `content_references:write` permission -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.content_reference.created }} @@ -269,17 +268,17 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% note %} -**注：**同时创建三个以上的标记时不会收到此事件的 web 挂钩。 +**Note:** You will not receive a webhook for this event when you create more than three tags at once. {% endnote %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `contents` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.create_properties %} {% data reusables.webhooks.pusher_type_desc %} @@ -288,7 +287,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.create }} @@ -298,17 +297,17 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% note %} -**注：**同时删除三个以上的标记时不会收到此事件的 web 挂钩。 +**Note:** You will not receive a webhook for this event when you delete more than three tags at once. {% endnote %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `contents` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.delete_properties %} {% data reusables.webhooks.pusher_type_desc %} @@ -317,7 +316,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.delete }} @@ -325,19 +324,19 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.deploy_key_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 +- Repository webhooks +- Organization webhooks -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.deploy_key_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.deploy_key.created }} @@ -345,24 +344,24 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.deployment_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `deployments` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `deployments` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| ------------ | ------------------------------------------- | --------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} -| `action` | `字符串` | 执行的操作。 可以是 `created`。{% endif %} -| `deployment` | `对象` | [部署](/rest/reference/deployments#list-deployments)。 | +Key | Type | Description +----|------|------------- +`action` |`string` | The action performed. Can be `created`. +`deployment` |`object` | The [deployment](/rest/reference/deployments#list-deployments). {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.deployment }} @@ -370,54 +369,54 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.deployment_status_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `deployments` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `deployments` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| ---------------------------------- | ------------------------------------------- | ------------------------------------------------------------- |{% ifversion fpt or ghes or ghae or ghec %} -| `action` | `字符串` | 执行的操作。 可以是 `created`。{% endif %} -| `deployment_status` | `对象` | [部署状态](/rest/reference/deployments#list-deployment-statuses)。 | -| `deployment_status["state"]` | `字符串` | 新状态。 可以是 `pending`、`success`、`failure` 或 `error`。 | -| `deployment_status["target_url"]` | `字符串` | 添加到状态的可选链接。 | -| `deployment_status["description"]` | `字符串` | 添加到状态的可选人类可读说明。 | -| `deployment` | `对象` | 此状态关联的[部署](/rest/reference/deployments#list-deployments)。 | +Key | Type | Description +----|------|------------- +`action` |`string` | The action performed. Can be `created`. +`deployment_status` |`object` | The [deployment status](/rest/reference/deployments#list-deployment-statuses). +`deployment_status["state"]` |`string` | The new state. Can be `pending`, `success`, `failure`, or `error`. +`deployment_status["target_url"]` |`string` | The optional link added to the status. +`deployment_status["description"]`|`string` | The optional human-readable description added to the status. +`deployment` |`object` | The [deployment](/rest/reference/deployments#list-deployments) that this status is associated with. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.deployment_status }} {% ifversion fpt or ghec %} -## 讨论 +## discussion {% data reusables.webhooks.discussions-webhooks-beta %} -与讨论有关的活动。 更多信息请参阅“[使用 GraphQL API 进行讨论]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)”。 -### 可用性 +Activity related to a discussion. For more information, see the "[Using the GraphQL API for discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)." +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `discussions` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `discussions` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| -------- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是 `created`、`edited`、`deleted`、`pinned`、`unpinned`、`locked`、`unlocked`、`transferred`、`category_changed`、`answered`、`unanswered`、`labeled` 或 `unlabeled`。 | +Key | Type | Description +----|------|------------- +`action` |`string` | The action performed. Can be `created`, `edited`, `deleted`, `pinned`, `unpinned`, `locked`, `unlocked`, `transferred`, `category_changed`, `answered`, `unanswered`, `labeled`, or `unlabeled`. {% data reusables.webhooks.discussion_desc %} {% data reusables.webhooks.repo_desc_graphql %} {% data reusables.webhooks.org_desc_graphql %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.discussion.created }} @@ -425,63 +424,63 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.discussions-webhooks-beta %} -与讨论中的评论相关的活动。 更多信息请参阅“[使用 GraphQL API 进行讨论]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)”。 +Activity related to a comment in a discussion. For more information, see "[Using the GraphQL API for discussions]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions)." -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `discussions` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `discussions` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| -------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是 `created`、`edited` 或 `deleted`。 | -| `注释，评论` | `对象` | [`discussion comment`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions#discussioncomment) 资源。 | +Key | Type | Description +----|------|------------- +`action` |`string` | The action performed. Can be `created`, `edited`, or `deleted`. +`comment` | `object` | The [`discussion comment`]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/using-the-graphql-api-for-discussions#discussioncomment) resource. {% data reusables.webhooks.discussion_desc %} {% data reusables.webhooks.repo_desc_graphql %} {% data reusables.webhooks.org_desc_graphql %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.discussion_comment.created }} {% endif %} {% ifversion ghes or ghae %} -## 企业 +## enterprise {% data reusables.webhooks.enterprise_short_desc %} -### 可用性 +### Availability -- GitHub Enterprise web 挂钩。 更多信息请参阅“[全局 web 挂钩](/rest/reference/enterprise-admin#global-webhooks/)”。 +- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)." -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| -------- | ----- | -------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是 `anonymous_access_enabled` 或 `anonymous_access_disabled`。 | +Key | Type | Description +----|------|------------- +`action` |`string` | The action performed. Can be `anonymous_access_enabled` or `anonymous_access_disabled`. -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.enterprise.anonymous_access_enabled }} {% endif %} -## 复刻 +## fork {% data reusables.webhooks.fork_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `contents` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.fork_properties %} {% data reusables.webhooks.repo_desc %} @@ -489,28 +488,28 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.fork }} ## github_app_authorization -当有人撤销对 {% data variables.product.prodname_github_app %} 的授权时，将发生此事件。 {% data variables.product.prodname_github_app %} 默认情况下会接收此 web 挂钩，并且无法取消订阅此事件。 +When someone revokes their authorization of a {% data variables.product.prodname_github_app %}, this event occurs. A {% data variables.product.prodname_github_app %} receives this webhook by default and cannot unsubscribe from this event. -{% data reusables.webhooks.authorization_event %} 有关 user-to-server 请求（需要 {% data variables.product.prodname_github_app %} 授权）的详细信息，请参阅“[识别和授权 {% data variables.product.prodname_github_apps %} 用户](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)”。 +{% data reusables.webhooks.authorization_event %} For details about user-to-server requests, which require {% data variables.product.prodname_github_app %} authorization, see "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." -### 可用性 +### Availability - {% data variables.product.prodname_github_apps %} -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| -------- | ----- | --------------------- | -| `action` | `字符串` | 执行的操作。 可以是 `revoked`。 | +Key | Type | Description +----|------|------------- +`action` |`string` | The action performed. Can be `revoked`. {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.github_app_authorization.revoked }} @@ -518,13 +517,13 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.gollum_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `contents` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.gollum_properties %} {% data reusables.webhooks.repo_desc %} @@ -532,25 +531,25 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.gollum }} -## 安装 +## installation {% data reusables.webhooks.installation_short_desc %} -### 可用性 +### Availability - {% data variables.product.prodname_github_apps %} -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.installation_properties %} {% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.installation.deleted }} @@ -558,17 +557,17 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.installation_repositories_short_desc %} -### 可用性 +### Availability - {% data variables.product.prodname_github_apps %} -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.installation_repositories_properties %} {% data reusables.webhooks.app_always_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.installation_repositories.added }} @@ -576,13 +575,13 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.issue_comment_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `issues` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `issues` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.issue_comment_webhook_properties %} {% data reusables.webhooks.issue_comment_properties %} @@ -591,21 +590,21 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.issue_comment.created }} -## 议题 +## issues {% data reusables.webhooks.issues_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `issues` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `issues` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.issue_webhook_properties %} {% data reusables.webhooks.issue_properties %} @@ -614,72 +613,72 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### 有人编辑议题时的 web 挂钩示例 +### Webhook payload example when someone edits an issue {{ webhookPayloadsForCurrentVersion.issues.edited }} -## 标签 +## label {% data reusables.webhooks.label_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `metadata` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `metadata` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| ---------------------- | ----- | -------------------------------------------- | -| `action` | `字符串` | 执行的操作内容. 可以是 `created`、`edited` 或 `deleted`。 | -| `标签` | `对象` | 添加的标签。 | -| `changes` | `对象` | 对标签的更改（如果操作为 `edited`）。 | -| `changes[name][from]` | `字符串` | 名称的先前版本（如果操作为 `edited`）。 | -| `changes[color][from]` | `字符串` | 颜色的先前版本（如果操作为 `edited`）。 | +Key | Type | Description +----|------|------------- +`action`|`string` | The action that was performed. Can be `created`, `edited`, or `deleted`. +`label`|`object` | The label that was added. +`changes`|`object`| The changes to the label if the action was `edited`. +`changes[name][from]`|`string` | The previous version of the name if the action was `edited`. +`changes[color][from]`|`string` | The previous version of the color if the action was `edited`. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.label.deleted }} {% ifversion fpt or ghec %} ## marketplace_purchase -与 GitHub Marketplace 购买相关的活动。 {% data reusables.webhooks.action_type_desc %} 更多信息请参阅“[GitHub Marketplace](/marketplace/)”。 +Activity related to a GitHub Marketplace purchase. {% data reusables.webhooks.action_type_desc %} For more information, see the "[GitHub Marketplace](/marketplace/)." -### 可用性 +### Availability - {% data variables.product.prodname_github_apps %} -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| -------- | ----- | --------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 为 [GitHub Marketplace](https://github.com/marketplace) 计划执行的操作。 可以是以下选项之一：
  • `purchased` - 有人购买了 GitHub Marketplace 计划。 更改应立即对帐户生效。
  • `pending_change` - 当有人降级或取消了 GitHub Marketplace 计划以指示帐户上将发生更改时，您将收到 `pending_change` 事件。 新的计划或取消将在结算周期结束时生效。 当结算周期结束并且取消或新计划应生效时，将发送 `cancelled` 或 `changed` 事件类型。
  • `pending_change_cancelled` - 有人取消了待处理更改。 待处理更改包括将在结算周期结束时生效的计划取消和降级。
  • `changed` - 有人升级或降级了 GitHub Marketplace 计划，并且该更改应立即对帐户生效。
  • `cancelled` - 有人取消了 GitHub Marketplace 计划并且最后一个结算周期已结束。 更改应立即对帐户生效。
| +Key | Type | Description +----|------|------------- +`action` | `string` | The action performed for a [GitHub Marketplace](https://github.com/marketplace) plan. Can be one of:
  • `purchased` - Someone purchased a GitHub Marketplace plan. The change should take effect on the account immediately.
  • `pending_change` - You will receive the `pending_change` event when someone has downgraded or cancelled a GitHub Marketplace plan to indicate a change will occur on the account. The new plan or cancellation takes effect at the end of the billing cycle. The `cancelled` or `changed` event type will be sent when the billing cycle has ended and the cancellation or new plan should take effect.
  • `pending_change_cancelled` - Someone has cancelled a pending change. Pending changes include plan cancellations and downgrades that will take effect at the end of a billing cycle.
  • `changed` - Someone has upgraded or downgraded a GitHub Marketplace plan and the change should take effect on the account immediately.
  • `cancelled` - Someone cancelled a GitHub Marketplace plan and the last billing cycle has ended. The change should take effect on the account immediately.
-有关此有效负载和每种 `action` 类型的有效负载的详细说明，请参阅 [{% data variables.product.prodname_marketplace %} web 挂钩事件](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)。 +For a detailed description of this payload and the payload for each type of `action`, see [{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/). -### 有人购买计划时的 web 挂钩示例 +### Webhook payload example when someone purchases the plan {{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }} {% endif %} -## 成员 +## member {% data reusables.webhooks.member_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `members` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `members` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.member_webhook_properties %} {% data reusables.webhooks.member_properties %} @@ -688,7 +687,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.member.added }} @@ -696,57 +695,57 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.membership_short_desc %} -### 可用性 +### Availability -- 组织 web 挂钩 -- 具有 `members` 权限的 {% data variables.product.prodname_github_apps %} +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `members` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.membership_properties %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.membership.removed }} ## meta -配置此事件的 web 挂钩已被删除。 此事件将仅监听对安装此事件的特定挂钩的更改。 因此，必须为要接收元事件的每个挂钩选择它。 +The webhook this event is configured on was deleted. This event will only listen for changes to the particular hook the event is installed on. Therefore, it must be selected for each hook that you'd like to receive meta events for. -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 +- Repository webhooks +- Organization webhooks -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| --------- | ----- | ------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是 `deleted`。 | -| `hook_id` | `整数` | 修改后的 web 挂钩的 ID。 | -| `挂钩` | `对象` | 修改后的 web 挂钩。 它将包含基于 web 挂钩类型的不同键：repository、organization、business、app 或 GitHub Marketplace。 | +Key | Type | Description +----|------|------------- +`action` |`string` | The action performed. Can be `deleted`. +`hook_id` |`integer` | The id of the modified webhook. +`hook` |`object` | The modified webhook. This will contain different keys based on the type of webhook it is: repository, organization, business, app, or GitHub Marketplace. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.meta.deleted }} -## 里程碑 +## milestone {% data reusables.webhooks.milestone_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `pull_requests` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.milestone_properties %} {% data reusables.webhooks.repo_desc %} @@ -754,33 +753,33 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.milestone.created }} -## 组织 +## organization {% data reusables.webhooks.organization_short_desc %} -### 可用性 +### Availability {% ifversion ghes or ghae %} -- GitHub Enterprise web 挂钩只接收 `created` 和 `deleted` 事件。 更多信息请参阅“[全局 web 挂钩](/rest/reference/enterprise-admin#global-webhooks/)”。{% endif %} -- 组织 web 挂钩只接收 `deleted`、`added`、`removed`、`renamed` 和 `invited` 事件 -- 具有 `members` 权限的 {% data variables.product.prodname_github_apps %} +- GitHub Enterprise webhooks only receive `created` and `deleted` events. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/).{% endif %} +- Organization webhooks only receive the `deleted`, `added`, `removed`, `renamed`, and `invited` events +- {% data variables.product.prodname_github_apps %} with the `members` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| ------------ | ----- | ------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：{% ifversion ghes or ghae %}`created`、{% endif %}`deleted`、`renamed`、`member_added`、`member_removed` 或 `member_invited`。 | -| `邀请` | `对象` | 对用户的邀请或电子邮件邀请（如果操作为 `member_invited`）。 | -| `membership` | `对象` | 用户和组织之间的成员资格。 当操作为 `member_invited` 时不存在。 | +Key | Type | Description +----|------|------------- +`action` |`string` | The action that was performed. Can be one of:{% ifversion ghes or ghae %} `created`,{% endif %} `deleted`, `renamed`, `member_added`, `member_removed`, or `member_invited`. +`invitation` |`object` | The invitation for the user or email if the action is `member_invited`. +`membership` |`object` | The membership between the user and the organization. Not present when the action is `member_invited`. {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.organization.member_added }} @@ -790,22 +789,22 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.org_block_short_desc %} -### 可用性 +### Availability -- 组织 web 挂钩 -- 具有 `organization_administration` 权限的 {% data variables.product.prodname_github_apps %} +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `organization_administration` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| -------------- | ----- | ----------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是 `blocked` 或 `unblocked`。 | -| `blocked_user` | `对象` | 有关被阻止或取消阻止的用户的信息。 | +Key | Type | Description +----|------|------------ +`action` | `string` | The action performed. Can be `blocked` or `unblocked`. +`blocked_user` | `object` | Information about the user that was blocked or unblocked. {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.org_block.blocked }} @@ -813,21 +812,21 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 ## package -与 {% data variables.product.prodname_registry %} 有关的活动。 {% data reusables.webhooks.action_type_desc %}更多信息请参阅“[使用 {% data variables.product.prodname_registry %} 管理包](/github/managing-packages-with-github-packages)”以详细了解 {% data variables.product.prodname_registry %}。 +Activity related to {% data variables.product.prodname_registry %}. {% data reusables.webhooks.action_type_desc %} For more information, see "[Managing packages with {% data variables.product.prodname_registry %}](/github/managing-packages-with-github-packages)" to learn more about {% data variables.product.prodname_registry %}. -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 +- Repository webhooks +- Organization webhooks -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.package_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.package.published }} @@ -835,24 +834,24 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.page_build_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `pages` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `pages` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| ---- | ---- | ----------------------------------------------------------------------- | -| `id` | `整数` | 页面构建的唯一标识符。 | -| `构建` | `对象` | [列表 GitHub Pages 构建](/rest/reference/pages#list-github-pages-builds)本身。 | +Key | Type | Description +----|------|------------ +`id` | `integer` | The unique identifier of the page build. +`build` | `object` | The [List GitHub Pages builds](/rest/reference/pages#list-github-pages-builds) itself. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.page_build }} @@ -860,25 +859,25 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.ping_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- {% data variables.product.prodname_github_apps %} 接收带有用于注册应用程序的 `app_id` 的 ping 事件。 +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} receive a ping event with an `app_id` used to register the app -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| -------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `zen` | `字符串` | GitHub zen 的随机字符串。 | -| `hook_id` | `整数` | 触发 ping 的 web 挂钩的 ID。 | -| `挂钩` | `对象` | [web 挂钩配置](/rest/reference/webhooks#get-a-repository-webhook)。 | -| `hook[app_id]` | `整数` | 注册新的 {% data variables.product.prodname_github_app %} 时，{% data variables.product.product_name %} 将 ping 事件发送到您在注册过程中指定的 **web 挂钩 URL**。 该事件包含 `app_id`，这是[验证](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/)应用程序的必需项。 | +Key | Type | Description +----|------|------------ +`zen` | `string` | Random string of GitHub zen. +`hook_id` | `integer` | The ID of the webhook that triggered the ping. +`hook` | `object` | The [webhook configuration](/rest/reference/webhooks#get-a-repository-webhook). +`hook[app_id]` | `integer` | When you register a new {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} sends a ping event to the **webhook URL** you specified during registration. The event contains the `app_id`, which is required for [authenticating](/apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/) an app. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.ping }} @@ -886,21 +885,21 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.project_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `repository_projects` 或 `organization_projects` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission {% ifversion fpt or ghec %} {% note %} -**注意**：此事件对 Projects（测试版）不会发生。 +**Note**: This event does not occur for Projects (beta). {% endnote %} {% endif %} -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.project_properties %} {% data reusables.webhooks.repo_desc %} @@ -908,7 +907,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.project.created }} @@ -918,21 +917,21 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.project_card_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `repository_projects` 或 `organization_projects` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission {% ifversion fpt or ghec %} {% note %} -**注意**：此事件对 Projects（测试版）不会发生。 +**Note**: This event does not occur for Projects (beta). {% endnote %} {% endif %} -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.project_card_properties %} {% data reusables.webhooks.repo_desc %} @@ -940,7 +939,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.project_card.created }} @@ -948,13 +947,13 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.project_column_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `repository_projects` 或 `organization_projects` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.project_column_properties %} {% data reusables.webhooks.repo_desc %} @@ -962,30 +961,29 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.project_column.created }} ## public {% data reusables.webhooks.public_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `metadata` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `metadata` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| - | -- | -- | -| | | | +Key | Type | Description +----|------|------------- {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.public }} {% endif %} @@ -993,13 +991,13 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.pull_request_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `pull_requests` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.pull_request_webhook_properties %} {% data reusables.webhooks.pull_request_properties %} @@ -1008,9 +1006,9 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example -`review_requested` 和 `review_request_removed` 事件的递送将含有一个额外的字段，称为 `requested_reviewer`。 +Deliveries for `review_requested` and `review_request_removed` events will have an additional field called `requested_reviewer`. {{ webhookPayloadsForCurrentVersion.pull_request.opened }} @@ -1018,13 +1016,13 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.pull_request_review_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `pull_requests` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.pull_request_review_properties %} {% data reusables.webhooks.repo_desc %} @@ -1032,7 +1030,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.pull_request_review.submitted }} @@ -1040,13 +1038,13 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.pull_request_review_comment_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `pull_requests` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.pull_request_review_comment_webhook_properties %} {% data reusables.webhooks.pull_request_review_comment_properties %} @@ -1055,7 +1053,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.pull_request_review_comment.created }} @@ -1063,13 +1061,13 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.pull_request_review_thread_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `pull_requests` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `pull_requests` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.pull_request_thread_properties %} {% data reusables.webhooks.repo_desc %} @@ -1077,71 +1075,71 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.pull_request_review_thread.resolved }} -## 推送 +## push {% data reusables.webhooks.push_short_desc %} {% note %} -**注：**同时推送三个以上的标记时不会收到此事件的 web 挂钩。 +**Note:** You will not receive a webhook for this event when you push more than three tags at once. {% endnote %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `contents` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| -------------------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------- | -| `ref` | `字符串` | 被推送的完整 [`git ref`](/rest/reference/git#refs)。 例如： `refs/heads/main` 或 `refs/tags/v3.14.1`。 | -| `before` | `字符串` | 推送之前在 `ref` 上最近提交的 SHA。 | -| `after` | `字符串` | 推送之后在 `ref` 上最近提交的 SHA。 | -| `created` | `布尔值` | 此推送是否创建 `ref`。 | -| `deleted` | `布尔值` | 此推送是否删除 `ref`。 | -| `forced` | `布尔值` | 此推送是否为 `ref` 的强制推送。 | -| `head_commit` | `对象` | 对于 `after` 是提交对象或指向提交对象的推送，为该提交的扩展表示。 对于 `after` 指示注释标记对象的推送，注释标记指向的提交的扩展表示。 | -| `compare` | `字符串` | 显示此 `ref` 更新中更改的 URL，从 `before` 提交到 `after` 提交。 对于新创建的直接基于默认分支的 `ref`，这是默认分支的头部与 `after` 提交之间的比较。 否则，这将显示 `after` 提交之前的所有提交。 | -| `commits` | `数组` | 描述所推送提交的提交对象数组。 （推送的提交是指包含在 `compare` 中 `before` 提交与 `after` 提交之间的所有提交） | -| `commits[][id]` | `字符串` | 提交的 SHA。 | -| `commits[][timestamp]` | `字符串` | 提交的 ISO 8601 时间戳。 | -| `commits[][message]` | `字符串` | 提交消息. | -| `commits[][author]` | `对象` | 提交的 Git 作者。 | -| `commits[][author][name]` | `字符串` | Git 作者的名称。 | -| `commits[][author][email]` | `字符串` | Git 作者的电子邮件地址。 | -| `commits[][url]` | `url` | 指向提交 API 资源的 URL。 | -| `commits[][distinct]` | `布尔值` | 此提交是否与之前推送的任何提交不同。 | -| `commits[][added]` | `数组` | 在提交中添加的文件数组。 | -| `commits[][modified]` | `数组` | 由提交修改的文件数组。 | -| `commits[][removed]` | `数组` | 在提交中删除的文件数组。 | -| `pusher` | `对象` | 推送提交的用户。 | +Key | Type | Description +----|------|------------- +`ref`|`string` | The full [`git ref`](/rest/reference/git#refs) that was pushed. Example: `refs/heads/main` or `refs/tags/v3.14.1`. +`before`|`string` | The SHA of the most recent commit on `ref` before the push. +`after`|`string` | The SHA of the most recent commit on `ref` after the push. +`created`|`boolean` | Whether this push created the `ref`. +`deleted`|`boolean` | Whether this push deleted the `ref`. +`forced`|`boolean` | Whether this push was a force push of the `ref`. +`head_commit`|`object` | For pushes where `after` is or points to a commit object, an expanded representation of that commit. For pushes where `after` refers to an annotated tag object, an expanded representation of the commit pointed to by the annotated tag. +`compare`|`string` | URL that shows the changes in this `ref` update, from the `before` commit to the `after` commit. For a newly created `ref` that is directly based on the default branch, this is the comparison between the head of the default branch and the `after` commit. Otherwise, this shows all commits until the `after` commit. +`commits`|`array` | An array of commit objects describing the pushed commits. (Pushed commits are all commits that are included in the `compare` between the `before` commit and the `after` commit.) +`commits[][id]`|`string` | The SHA of the commit. +`commits[][timestamp]`|`string` | The ISO 8601 timestamp of the commit. +`commits[][message]`|`string` | The commit message. +`commits[][author]`|`object` | The git author of the commit. +`commits[][author][name]`|`string` | The git author's name. +`commits[][author][email]`|`string` | The git author's email address. +`commits[][url]`|`url` | URL that points to the commit API resource. +`commits[][distinct]`|`boolean` | Whether this commit is distinct from any that have been pushed before. +`commits[][added]`|`array` | An array of files added in the commit. +`commits[][modified]`|`array` | An array of files modified by the commit. +`commits[][removed]`|`array` | An array of files removed in the commit. +`pusher` | `object` | The user who pushed the commits. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.push }} -## 发行版 +## release {% data reusables.webhooks.release_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `contents` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `contents` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.release_webhook_properties %} {% data reusables.webhooks.release_properties %} @@ -1150,66 +1148,64 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.release.published }} -{% ifversion fpt or ghes or ghae or ghec %} ## repository_dispatch -当 {% data variables.product.prodname_github_app %} 将 `POST` 请求发送到“[创建仓库分发事件](/rest/reference/repos#create-a-repository-dispatch-event)”端点时，此事件发生。 +This event occurs when a {% data variables.product.prodname_github_app %} sends a `POST` request to the "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)" endpoint. -### 可用性 +### Availability -- {% data variables.product.prodname_github_apps %} 必须具有 `contents` 权限才能接收此 web 挂钩。 +- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook. -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.repository_dispatch }} -{% endif %} -## 仓库 +## repository {% data reusables.webhooks.repository_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩接收除 `deleted` 之外的所有事件类型 -- 组织 web 挂钩 -- 具有 `metadata` 权限的 {% data variables.product.prodname_github_apps %} 接收除 `deleted` 之外的所有事件类型 +- Repository webhooks receive all event types except `deleted` +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `metadata` permission receive all event types except `deleted` -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| -------- | ----- | -------------------------------------------- | -| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：
  • `created` - 创建了仓库。
  • `deleted` - 仓库被删除。
  • `archived` - 仓库被存档。
  • `unarchived` - 仓库被取消存档。
    • {% ifversion ghes or ghae %}
  • “anonymous_access_enabled” - 存储库 [已启用匿名 Git 访问](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise), `anonymous_access_disabled` - 存储库 [已禁用匿名 Git 访问] (/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)
    • {% endif %}
  • `edited` - 仓库的信息被编辑。
  • `renamed` - 仓库被重命名。
  • `transferred` - 仓库被转让。
  • `publicized` - 仓库被设为公共。
  • `privatized` - 仓库被设为私有。
| +Key | Type | Description +----|------|------------- +`action` |`string` | The action that was performed. This can be one of:
  • `created` - A repository is created.
  • `deleted` - A repository is deleted.
  • `archived` - A repository is archived.
  • `unarchived` - A repository is unarchived.
    • {% ifversion ghes or ghae %}
  • `anonymous_access_enabled` - A repository is [enabled for anonymous Git access](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise), `anonymous_access_disabled` - A repository is [disabled for anonymous Git access](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)
    • {% endif %}
  • `edited` - A repository's information is edited.
  • `renamed` - A repository is renamed.
  • `transferred` - A repository is transferred.
  • `publicized` - A repository is made public.
  • `privatized` - A repository is made private.
{% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.repository.publicized }} {% ifversion fpt or ghec %} ## repository_import -{% data reusables.webhooks.repository_import_short_desc %} 要在个人仓库中接收此事件，必须在导入之前创建一个空仓库。 此事件可使用 [GitHub 导入工具](/articles/importing-a-repository-with-github-importer/)或[来源导入 API](/rest/reference/migrations#source-imports) 触发。 +{% data reusables.webhooks.repository_import_short_desc %} To receive this event for a personal repository, you must create an empty repository prior to the import. This event can be triggered using either the [GitHub Importer](/articles/importing-a-repository-with-github-importer/) or the [Source imports API](/rest/reference/migrations#source-imports). -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 +- Repository webhooks +- Organization webhooks -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.repository_import_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.repository_import }} @@ -1217,19 +1213,19 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.repository_vulnerability_alert_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 +- Repository webhooks +- Organization webhooks -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.repository_vulnerability_alert_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.repository_vulnerability_alert.create }} @@ -1241,21 +1237,21 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.secret_scanning_alert_event_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `secret_scanning_alerts:read` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `secret_scanning_alerts:read` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.secret_scanning_alert_event_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} -`sender` | `object` | 如果 `action` 是 `resolved` 或 `reopened`，则 `sender` 对象将是触发事件的用户。 对于所有其他操作，`sender` 对象都为空。 +`sender` | `object` | If the `action` is `resolved` or `reopened`, the `sender` object will be the user that triggered the event. The `sender` object is empty for all other actions. -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.secret_scanning_alert.reopened }} {% endif %} @@ -1265,20 +1261,20 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.secret_scanning_alert_location_event_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `secret_scanning_alerts:read` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `secret_scanning_alerts:read` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.secret_scanning_alert_location_event_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.secret_scanning_alert_location.created }} {% endif %} @@ -1286,22 +1282,22 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% ifversion fpt or ghes or ghec %} ## security_advisory -与已由 {% data variables.product.company_short %} 审查的安全通告相关的活动。 经过 {% data variables.product.company_short %} 审查的安全通告提供了有关 {% data variables.product.prodname_dotcom %}上软件中安全相关漏洞的信息。 +Activity related to a security advisory that has been reviewed by {% data variables.product.company_short %}. A {% data variables.product.company_short %}-reviewed security advisory provides information about security-related vulnerabilities in software on {% data variables.product.prodname_dotcom %}. -安全通告数据集还为 GitHub {% data variables.product.prodname_dependabot_alerts %} 提供支持。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %} 警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)”。 +The security advisory dataset also powers the GitHub {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)." -### 可用性 +### Availability -- 具有 `security_events` 权限的 {% data variables.product.prodname_github_apps %} +- {% data variables.product.prodname_github_apps %} with the `security_events` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| ------------------- | ----- | --------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作内容. 对于所有新事件，该操作可以是 `published`、`updated`、`performed` 或 `withdrawn` 之一。 | -| `security_advisory` | `对象` | 安全通告的详细信息，包括摘要、说明和严重程度。 | +Key | Type | Description +----|------|------------- +`action` |`string` | The action that was performed. The action can be one of `published`, `updated`, `performed`, or `withdrawn` for all new events. +`security_advisory` |`object` | The details of the security advisory, including summary, description, and severity. -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.security_advisory.published }} @@ -1312,104 +1308,104 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.sponsorship_short_desc %} -您只能在 {% data variables.product.prodname_dotcom %} 上创建赞助 web 挂钩。 更多信息请参阅“[为赞助帐户中的事件配置 web 挂钩](/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)”。 +You can only create a sponsorship webhook on {% data variables.product.prodname_dotcom %}. For more information, see "[Configuring webhooks for events in your sponsored account](/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account)". -### 可用性 +### Availability -- 赞助帐户 +- Sponsored accounts -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.sponsorship_webhook_properties %} {% data reusables.webhooks.sponsorship_properties %} {% data reusables.webhooks.sender_desc %} -### 有人创建赞助时的 web 挂钩示例 +### Webhook payload example when someone creates a sponsorship {{ webhookPayloadsForCurrentVersion.sponsorship.created }} -### 有人降级赞助时的 web 挂钩示例 +### Webhook payload example when someone downgrades a sponsorship {{ webhookPayloadsForCurrentVersion.sponsorship.downgraded }} {% endif %} -## 星标 +## star {% data reusables.webhooks.star_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 +- Repository webhooks +- Organization webhooks -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.star_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.star.created }} -## 状态 +## status {% data reusables.webhooks.status_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `statuses` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `statuses` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| ------------ | ----- | ------------------------------------------------------------------- | -| `id` | `整数` | 状态的唯一标识符。 | -| `sha` | `字符串` | 提交 SHA。 | -| `state` | `字符串` | 新状态。 可以是 `pending`、`success`、`failure` 或 `error`。 | -| `说明` | `字符串` | 添加到状态的可选人类可读说明。 | -| `target_url` | `字符串` | 添加到状态的可选链接。 | -| `分支` | `数组` | 包含状态的 SHA 的分支对象数组。 每个分支都包含给定的 SHA，但 SHA 不一定是该分支的头部。 该数组最多包含 10 个分支。 | +Key | Type | Description +----|------|------------- +`id` | `integer` | The unique identifier of the status. +`sha`|`string` | The Commit SHA. +`state`|`string` | The new state. Can be `pending`, `success`, `failure`, or `error`. +`description`|`string` | The optional human-readable description added to the status. +`target_url`|`string` | The optional link added to the status. +`branches`|`array` | An array of branch objects containing the status' SHA. Each branch contains the given SHA, but the SHA may or may not be the head of the branch. The array includes a maximum of 10 branches. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.status }} -## 团队 +## team {% data reusables.webhooks.team_short_desc %} -### 可用性 +### Availability -- 组织 web 挂钩 -- 具有 `members` 权限的 {% data variables.product.prodname_github_apps %} +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `members` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| ----------------------------------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作内容. 可以是 `created`、`deleted`、`edited`、`added_to_repository` 或 `removed_from_repository` 之一。 | -| `团队` | `对象` | 团队本身。 | -| `changes` | `对象` | 对团队的更改（如果操作为 `edited`）。 | -| `changes[description][from]` | `字符串` | 说明的先前版本（如果操作为 `edited`）。 | -| `changes[name][from]` | `字符串` | 名称的先前版本（如果操作为 `edited`）。 | -| `changes[privacy][from]` | `字符串` | 团队隐私的先前版本（如果操作为 `edited`）。 | -| `changes[repository][permissions][from][admin]` | `布尔值` | 团队成员对仓库 `admin` 权限的先前版本（如果操作为 `edited`）。 | -| `changes[repository][permissions][from][pull]` | `布尔值` | 团队成员对仓库 `pull` 权限的先前版本（如果操作为 `edited`）。 | -| `changes[repository][permissions][from][push]` | `布尔值` | 团队成员对仓库 `push` 权限的先前版本（如果操作为 `edited`）。 | -| `仓库` | `对象` | 在团队权限范围中添加或删除的仓库（如果操作为 `added_to_repository`、`removed_from_repository` 或 `edited`）。 对于 `edited` 操作，`repository` 还包含团队对仓库的新权限级别。 | +Key | Type | Description +----|------|------------- +`action` |`string` | The action that was performed. Can be one of `created`, `deleted`, `edited`, `added_to_repository`, or `removed_from_repository`. +`team` |`object` | The team itself. +`changes`|`object` | The changes to the team if the action was `edited`. +`changes[description][from]` |`string` | The previous version of the description if the action was `edited`. +`changes[name][from]` |`string` | The previous version of the name if the action was `edited`. +`changes[privacy][from]` |`string` | The previous version of the team's privacy if the action was `edited`. +`changes[repository][permissions][from][admin]` | `boolean` | The previous version of the team member's `admin` permission on a repository, if the action was `edited`. +`changes[repository][permissions][from][pull]` | `boolean` | The previous version of the team member's `pull` permission on a repository, if the action was `edited`. +`changes[repository][permissions][from][push]` | `boolean` | The previous version of the team member's `push` permission on a repository, if the action was `edited`. +`repository`|`object` | The repository that was added or removed from to the team's purview if the action was `added_to_repository`, `removed_from_repository`, or `edited`. For `edited` actions, `repository` also contains the team's new permission levels for the repository. {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.team.added_to_repository }} @@ -1417,54 +1413,54 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.team_add_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `members` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `members` permission -### Web 挂钩有效负载对象 +### Webhook payload object -| 键 | 类型 | 描述 | -| ---- | ---- | ------------------------------------------------------------ | -| `团队` | `对象` | 被修改的[团队](/rest/reference/teams)。 **注：**较旧的事件可能不会在有效负载中包括此值。 | +Key | Type | Description +----|------|------------- +`team`|`object` | The [team](/rest/reference/teams) that was modified. **Note:** Older events may not include this in the payload. {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.team_add }} {% ifversion ghes or ghae %} -## 用户 +## user -当用户被 `created` 或 `deleted` 时。 +When a user is `created` or `deleted`. -### 可用性 -- GitHub Enterprise web 挂钩。 更多信息请参阅“[全局 web 挂钩](/rest/reference/enterprise-admin#global-webhooks/)”。 +### Availability +- GitHub Enterprise webhooks. For more information, "[Global webhooks](/rest/reference/enterprise-admin#global-webhooks/)." -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.user.created }} {% endif %} -## 查看 +## watch {% data reusables.webhooks.watch_short_desc %} -事件的执行者是标星仓库的[用户](/rest/reference/users)，并且事件的仓库是被标星的[仓库](/rest/reference/repos)。 +The event’s actor is the [user](/rest/reference/users) who starred a repository, and the event’s repository is the [repository](/rest/reference/repos) that was starred. -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 具有 `metadata` 权限的 {% data variables.product.prodname_github_apps %} +- Repository webhooks +- Organization webhooks +- {% data variables.product.prodname_github_apps %} with the `metadata` permission -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.watch_properties %} {% data reusables.webhooks.repo_desc %} @@ -1472,44 +1468,44 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.app_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.watch.started }} {% ifversion fpt or ghes or ghec %} ## workflow_dispatch -当有人触发 GitHub 上的工作流程运行或将 `POST` 请求发送到“[创建工作流程分发事件](/rest/reference/actions/#create-a-workflow-dispatch-event)”端点时，此事件发生。 更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#workflow_dispatch)”。 +This event occurs when someone triggers a workflow run on GitHub or sends a `POST` request to the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)" endpoint. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)." -### 可用性 +### Availability -- {% data variables.product.prodname_github_apps %} 必须具有 `contents` 权限才能接收此 web 挂钩。 +- {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook. -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.workflow_dispatch }} {% endif %} -{% ifversion fpt or ghes > 3.2 or ghec or ghae-issue-4462 %} +{% ifversion fpt or ghes > 3.2 or ghec or ghae %} ## workflow_job {% data reusables.webhooks.workflow_job_short_desc %} -### 可用性 +### Availability -- 仓库 web 挂钩 -- 组织 web 挂钩 -- 企业 web 挂钩 +- Repository webhooks +- Organization webhooks +- Enterprise webhooks -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.workflow_job_properties %} {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.org_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.workflow_job }} @@ -1517,13 +1513,13 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% ifversion fpt or ghes or ghec %} ## workflow_run -当 {% data variables.product.prodname_actions %} 工作流程运行被请求或完成时。 更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows#workflow_run)”。 +When a {% data variables.product.prodname_actions %} workflow run is requested or completed. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_run)." -### 可用性 +### Availability -- 具有 `actions` 或 `contents` 权限的 {% data variables.product.prodname_github_apps %}。 +- {% data variables.product.prodname_github_apps %} with the `actions` or `contents` permissions. -### Web 挂钩有效负载对象 +### Webhook payload object {% data reusables.webhooks.workflow_run_properties %} {% data reusables.webhooks.workflow_desc %} @@ -1531,7 +1527,7 @@ Web 挂钩事件是基于您注册的域的特异性而触发的。 例如，如 {% data reusables.webhooks.repo_desc %} {% data reusables.webhooks.sender_desc %} -### Web 挂钩有效负载示例 +### Webhook payload example {{ webhookPayloadsForCurrentVersion.workflow_run }} {% endif %} diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md index 8a3e0e9233..e8ac979c34 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md @@ -1,39 +1,39 @@ --- title: 关于将 Visual Studio Code 与 GitHub Classroom 配合使用 shortTitle: 关于使用 Visual Studio Code -intro: '您可以将 Visual Studio Code 配置为 {% data variables.product.prodname_classroom %} 中任务的首选编辑器。' +intro: 'You can configure {% data variables.product.prodname_vscode %} as the preferred editor for assignments in {% data variables.product.prodname_classroom %}.' versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/about-using-vs-code-with-github-classroom --- -## 关于 Visual Studio Code +## 关于 {% data variables.product.prodname_vscode %} -Visual Studio Code 是一个轻量级但功能强大的源代码编辑器，可在桌面上运行，适用于 Windows、macOS 和 Linux。 借助 [Visual Studio Code 的 GitHub Classroom 扩展](https://aka.ms/classroom-vscode-ext)，学生可以轻松浏览、编辑、提交、协作和测试他们的课堂作业。 有关 IDE 和 {% data variables.product.prodname_classroom %} 的更多信息，请参阅“[集成 {% data variables.product.prodname_classroom %} 与 IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)”。 +{% data variables.product.prodname_vscode %} is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. With the [GitHub Classroom extension for {% data variables.product.prodname_vscode_shortname %}](https://aka.ms/classroom-vscode-ext), students can easily browse, edit, submit, collaborate, and test their Classroom Assignments. 有关 IDE 和 {% data variables.product.prodname_classroom %} 的更多信息，请参阅“[集成 {% data variables.product.prodname_classroom %} 与 IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)”。 ### 您学生的首选编辑器 -GitHub Classroom 与 Visual Studio Code 的集成为学生提供了一个扩展包，其中包含： +The GitHub Classroom integration with {% data variables.product.prodname_vscode_shortname %} provides students with an extension pack which contains: 1. [GitHub 课程扩展](https://aka.ms/classroom-vscode-ext)，其中包含自定义摘要，便于学生轻松入门。 2. [Visual Studio 实时分享扩展](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare-pack)，集成到学生视图中，以便轻松获取助教和同学的帮助与协作。 3. [GitHub 拉取请求扩展](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github)，允许学生在编辑器中查看教师的反馈。 -### 如何在 Visual Studio Code 中启动作业 -创建作业时，可以将 Visual Studio Code 添加为作业的首选编辑器。 有关详细信息，请参阅“[集成 {% data variables.product.prodname_classroom %} 与 IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)”。 +### How to launch the assignment in {% data variables.product.prodname_vscode_shortname %} +When creating an assignment, {% data variables.product.prodname_vscode_shortname %} can be added as the preferred editor for an assignment. 有关详细信息，请参阅“[集成 {% data variables.product.prodname_classroom %} 与 IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)”。 -这将包括所有学生仓库中的“在 Visual Studio 代码中打开”徽章。 此徽章处理安装 Visual Studio Code（课堂扩展包）以及一键打开活动的作业。 +This will include an "Open in {% data variables.product.prodname_vscode_shortname %}" badge in all student repositories. This badge handles installing {% data variables.product.prodname_vscode_shortname %}, the Classroom extension pack, and opening to the active assignment with one click. {% note %} -**注意：**学生必须在其计算机上安装 Git 才能将代码从 Visual Studio Code 推送到其存储库。 单击**在 Visual Studio 代码中打开**按钮时不自动安装。 学生可以从[这里](https://git-scm.com/downloads)下载 Git。 +**Note:** The student must have Git installed on their computer to push code from {% data variables.product.prodname_vscode_shortname %} to their repository. This is not automatically installed when clicking the **Open in {% data variables.product.prodname_vscode_shortname %}** button. 学生可以从[这里](https://git-scm.com/downloads)下载 Git。 {% endnote %} ### 如何使用 GitHub 课堂扩展包 GitHub 课堂扩展有两个主要组件：“课堂”视图和“活动的作业”视图。 -当学生首次启动扩展时，他们将自动导航到 Visual Studio Code 中的 Explorer 选项卡，在其中可以看到“活动的作业”视图以及存储库中文件的树视图。 +When the student launches the extension for the first time, they are automatically navigated to the Explorer tab in {% data variables.product.prodname_vscode_shortname %}, where they can see the "Active Assignment" view alongside the tree-view of files in the repository. ![GitHub 课堂活动作业视图](/assets/images/help/classroom/vs-code-active-assignment.png) diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md index ce0ae6eed4..2d70d0a80d 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md @@ -25,7 +25,7 @@ redirect_from: |:--------------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | {% data variables.product.prodname_github_codespaces %} | “[将 {% data variables.product.prodname_github_codespaces %} 与 {% data variables.product.prodname_classroom %} 一起使用](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)” | | Microsoft MakeCode Arcade | "[关于结合使用 MakeCode Arcade 与 {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" | -| Visual Studio Code | Visual Studio Marketplace 中的 [{% data variables.product.prodname_classroom %} 扩展](http://aka.ms/classroom-vscode-ext) | +| {% data variables.product.prodname_vscode %} | Visual Studio Marketplace 中的 [{% data variables.product.prodname_classroom %} 扩展](http://aka.ms/classroom-vscode-ext) | 我们知道云 IDE 集成对您的课堂非常重要，正在努力提供更多选择。 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 index 870d2fc97a..d775663d97 100644 --- 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 @@ -14,7 +14,7 @@ shortTitle: 扩展和集成 ## 编辑器工具 -您可以在第三方编辑器工具中连接到 {% data variables.product.product_name %} 仓库，例如 Atom、Unity 和 Visual Studio 等工具。 +You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and {% data variables.product.prodname_vs %}. ### {% data variables.product.product_name %} for Atom @@ -24,13 +24,13 @@ shortTitle: 扩展和集成 使用 {% 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 {% data variables.product.prodname_vs %} -使用 {% 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)。 +With the {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} extension, you can work in {% data variables.product.product_name %} repositories without leaving {% data variables.product.prodname_vs %}. For more information, see the official {% data variables.product.prodname_vs %} extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs). -### {% data variables.product.prodname_dotcom %} for Visual Studio Code +### {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} -使用 {% 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)。 +With the {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} extension, you can review and manage {% data variables.product.product_name %} pull requests in {% data variables.product.prodname_vscode_shortname %}. For more information, see the official {% data variables.product.prodname_vscode_shortname %} extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github). ## 项目管理工具 diff --git a/translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md b/translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md index ab98ff230a..64d7144396 100644 --- a/translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md +++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md @@ -15,7 +15,7 @@ topics: ## About followers on {% data variables.product.product_name %} -When you follow organizations, you'll see their public activity on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)." +When you follow organizations, you'll see their public activity on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)." You can unfollow an organization if you do not wish to see their {% ifversion fpt or ghec %}public{% endif %} activity on {% data variables.product.product_name %}. diff --git a/translations/zh-CN/content/get-started/exploring-projects-on-github/following-people.md b/translations/zh-CN/content/get-started/exploring-projects-on-github/following-people.md index 6ea399d0f9..68ceafd5d1 100644 --- a/translations/zh-CN/content/get-started/exploring-projects-on-github/following-people.md +++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/following-people.md @@ -17,7 +17,7 @@ topics: ## 关于 {% data variables.product.product_name %} 上的关注者 -关注用户后，您会在个人信息中心看到他们的公开活动。{% ifversion fpt or ghec %} 如果您关注的人将某个公共存储库标星， {% data variables.product.product_name %} 可能会向您推荐该存储库。{% endif %} 更多信息请参阅“[关于个人仪表板](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)”。 +When you follow people, you'll see their public activity on your personal dashboard.{% ifversion fpt or ghec %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you.{% endif %} For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)." 如果您不希望在 {% data variables.product.product_name %} 上看到某人的公开活动，则可以取消关注他们。 diff --git a/translations/zh-CN/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md b/translations/zh-CN/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md index 6af2c9f107..8787cd94e9 100644 --- a/translations/zh-CN/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md +++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md @@ -26,7 +26,7 @@ shortTitle: 保存有星标的仓库 标星操作便于以后再次找到仓库或主题。 您可以到 {% data variables.explore.your_stars_page %} 查看已经加星标的所有仓库和主题。 {% ifversion fpt or ghec %} -您可以对仓库和主题加星标以在 {% data variables.product.product_name %} 上发现类似的项目。 当您为存储库或主题添加星标时， {% data variables.product.product_name %} 可能会在您的个人仪表板上推荐相关内容。 更多信息请参阅“[查找参与 {% data variables.product.prodname_dotcom %} 上的开源项目的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”和“[关于个人仪表板](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)”。 +您可以对仓库和主题加星标以在 {% data variables.product.product_name %} 上发现类似的项目。 当您为存储库或主题添加星标时， {% data variables.product.product_name %} 可能会在您的个人仪表板上推荐相关内容。 更多信息请参阅“[查找参与 {% data variables.product.prodname_dotcom %} 上的开源项目的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”和“[关于个人仪表板](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)”。 {% endif %} 对仓库加星标也可表示赞赏仓库维护员的工作。 许多 {% data variables.product.prodname_dotcom %} 的仓库评级取决于仓库拥有的星标数。 此外，[Explore](https://github.com/explore) 也会根据星标数显示最受欢迎的仓库。 diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md index b706d97d92..612bb78690 100644 --- a/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md +++ b/translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md @@ -81,14 +81,10 @@ When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote reposit {% endtip %} -{% ifversion fpt or ghes or ghae or ghec %} - ## Cloning with {% data variables.product.prodname_cli %} You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} workflows in your terminal. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." -{% endif %} - {% ifversion not ghae %} ## Cloning with Subversion 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 479063689d..58175b2bd1 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 @@ -28,9 +28,9 @@ shortTitle: 关联文本编辑器 $ git config --global core.editor "atom --wait" ``` -## 使用 Visual Studio Code 作为编辑器 +## Using {% data variables.product.prodname_vscode %} as your editor -1. 安装 [Visual Studio Code](https://code.visualstudio.com/) (VS Code)。 更多信息请参阅 VS Code 文档中的“[设置 Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)”。 +1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.command_line.open_the_multi_os_terminal %} 3. 输入此命令： ```shell @@ -68,9 +68,9 @@ shortTitle: 关联文本编辑器 $ git config --global core.editor "atom --wait" ``` -## 使用 Visual Studio Code 作为编辑器 +## Using {% data variables.product.prodname_vscode %} as your editor -1. 安装 [Visual Studio Code](https://code.visualstudio.com/) (VS Code)。 更多信息请参阅 VS Code 文档中的“[设置 Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)”。 +1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.command_line.open_the_multi_os_terminal %} 3. 输入此命令： ```shell @@ -107,9 +107,9 @@ shortTitle: 关联文本编辑器 $ git config --global core.editor "atom --wait" ``` -## 使用 Visual Studio Code 作为编辑器 +## Using {% data variables.product.prodname_vscode %} as your editor -1. 安装 [Visual Studio Code](https://code.visualstudio.com/) (VS Code)。 更多信息请参阅 VS Code 文档中的“[设置 Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)”。 +1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation. {% data reusables.command_line.open_the_multi_os_terminal %} 3. 输入此命令： ```shell 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 7616cc276e..8eaea418ac 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 @@ -30,7 +30,7 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th - **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository.{% if secret-scanning-push-protection %} If push protection is enabled, also detects secrets when they are pushed to your repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)" and "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."{% else %} For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)."{% endif %} -{% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4864 %} +{% ifversion fpt or ghes > 3.1 or ghec or ghae %} - **Dependency review** - 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 %} @@ -113,4 +113,4 @@ For more information on starter workflows, see "[Setting up {% data variables.pr - "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)" {% endif %} -{% endif %} \ No newline at end of file +{% endif %} diff --git a/translations/zh-CN/content/get-started/learning-about-github/about-versions-of-github-docs.md b/translations/zh-CN/content/get-started/learning-about-github/about-versions-of-github-docs.md index 3e0c3f751b..90891c4225 100644 --- a/translations/zh-CN/content/get-started/learning-about-github/about-versions-of-github-docs.md +++ b/translations/zh-CN/content/get-started/learning-about-github/about-versions-of-github-docs.md @@ -37,7 +37,7 @@ In a wide browser window, there is no text that immediately follows the {% data On {% data variables.product.prodname_dotcom_the_website %}, each account has its own plan. Each personal account has an associated plan that provides access to certain features, and each organization has a different associated plan. If your personal account is a member of an organization on {% data variables.product.prodname_dotcom_the_website %}, you may have access to different features when you use resources owned by that organization than when you use resources owned by your personal account. For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)." -If you don't know whether an organization uses {% data variables.product.prodname_ghe_cloud %}, ask an organization owner. For more information, see "[Viewing people's roles in an organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)." +If you don't know whether an organization uses {% data variables.product.prodname_ghe_cloud %}, ask an organization owner. For more information, see "[Viewing people's roles in an organization](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)." ### {% data variables.product.prodname_ghe_server %} diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md index fb8cf05ac1..2e0c446eb0 100644 --- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -75,7 +75,7 @@ For more information about how to authenticate to {% data variables.product.prod | ------------- | ------------- | ------------- | | Browse to {% data variables.product.prodname_dotcom_the_website %} | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests.| This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally. | | {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} extends and simplifies your {% data variables.product.prodname_dotcom_the_website %} workflow, using a visual interface instead of text commands on the command line. For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}. | -| IDE or text editor | You can set a default text editor, like [Atom](https://atom.io/) or [Visual Studio Code](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. | +| IDE or text editor | You can set a default text editor, like [Atom](https://atom.io/) or [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. | | Command line, with or without {% data variables.product.prodname_cli %} | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."

{% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line. | | {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)." | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. | ### 4. Writing on {% data variables.product.product_name %} diff --git a/translations/zh-CN/content/get-started/quickstart/communicating-on-github.md b/translations/zh-CN/content/get-started/quickstart/communicating-on-github.md index 3f155a9a7e..a4328502c5 100644 --- a/translations/zh-CN/content/get-started/quickstart/communicating-on-github.md +++ b/translations/zh-CN/content/get-started/quickstart/communicating-on-github.md @@ -116,7 +116,6 @@ This example shows the {% data variables.product.prodname_discussions %} welcome This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository. {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} ### Scenarios for team discussions - I have a question that's not necessarily related to specific files in the repository. @@ -139,8 +138,6 @@ The `octocat` team member posted a team discussion, informing the team of variou - There is a blog post describing how the teams use {% data variables.product.prodname_actions %} to produce their docs. - Material about the April All Hands is now available for all team members to view. -{% endif %} - ## Next steps These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs. 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 293ae6772c..751f81b7a9 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 @@ -153,7 +153,7 @@ These commands are available from all scopes. |`New organization`|Create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." | |`New project`|Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)." | |`New repository`|Create a new repository from scratch. For more information, see "[Creating a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository)." | -|`Switch theme to `|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." | +|`Switch theme to `|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)." | ### Organization commands diff --git a/translations/zh-CN/content/get-started/using-github/github-mobile.md b/translations/zh-CN/content/get-started/using-github/github-mobile.md index e99da062ad..fe88929e61 100644 --- a/translations/zh-CN/content/get-started/using-github/github-mobile.md +++ b/translations/zh-CN/content/get-started/using-github/github-mobile.md @@ -25,10 +25,13 @@ With {% data variables.product.prodname_mobile %} you can: - Read, review, and collaborate on issues and pull requests - Search for, browse, and interact with users, repositories, and organizations - Receive a push notification when someone mentions your username -{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication{% endif %} +{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication +- Verify your sign in attempts on unrecognized devices{% endif %} For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)." +{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)." {% endif %} + ## Installing {% data variables.product.prodname_mobile %} To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% data variables.product.prodname_mobile %}](https://github.com/mobile). 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 fd482911ce..646bb7c088 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 @@ -20,7 +20,7 @@ versions: 在 {% data variables.product.prodname_dotcom %} 中输入 ? 可弹出一个对话框，列出可用于该页面的键盘快捷键。 您可以使用这些键盘快捷键对站点执行操作，而无需使用鼠标导航。 {% if keyboard-shortcut-accessibility-setting %} -您可以在辅助功能设置中禁用字符键快捷键，同时仍允许使用修饰键的快捷键。 更多信息请参阅“[管理辅助功能设置](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings)”。{% endif %} +您可以在辅助功能设置中禁用字符键快捷键，同时仍允许使用修饰键的快捷键。 更多信息请参阅“[管理辅助功能设置](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings)”。{% endif %} 下面是一些可用键盘快捷键的列表。 {% if command-palette %} @@ -28,11 +28,11 @@ versions: ## 站点快捷键 -| 键盘快捷键 | 描述 | -| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 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 | 转到您的通知。 更多信息请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications)”。 | +| Esc | 当聚焦于用户、议题或拉取请求悬停卡时，关闭悬停卡并重新聚焦于悬停卡所在的元素 | {% if command-palette %} @@ -106,7 +106,6 @@ versions: {% endif %} | R | 在您的回复中引用所选的文本。 更多信息请参阅“[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax#quoting-text)”。 | - ## 议题和拉取请求列表 | 键盘快捷键 | 描述 | @@ -135,16 +134,15 @@ versions: ## 拉取请求中的更改 -| 键盘快捷键 | 描述 | -| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| C | 在拉取请求中打开提交列表 | -| T | 在拉取请求中打开已更改文件列表 | -| J | 将所选内容在列表中向下移动 | -| K | 将所选内容在列表中向上移动 | -| Command+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)。” -{% endif %} +| 键盘快捷键 | 描述 | +| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| C | 在拉取请求中打开提交列表 | +| T | 在拉取请求中打开已更改文件列表 | +| J | 将所选内容在列表中向下移动 | +| K | 将所选内容在列表中向上移动 | +| Command+Shift+Enter | 添加一条有关拉取请求差异的评论 | +| Alt 并单击 | 通过按下 Alt 并单击 **Show outdated（显示已过期）**或 **Hide outdated（隐藏已过期）**，在折叠和展开拉取请求中所有过期的审查评论之间切换。 | +| 单击，然后按住 Shift 并单击 | 单击一个行号，按住 Shift，然后单击另一行号，便可对拉取请求的多行发表评论。 更多信息请参阅“[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)”。 | ## 项目板 @@ -200,7 +198,7 @@ versions: {% endif %} ## 通知 -{% ifversion fpt or ghes or ghae or ghec %} + | 键盘快捷键 | 描述 | | ----------------------------- | ----- | | E | 标记为完成 | @@ -208,13 +206,6 @@ versions: | Shift+I | 标记为已读 | | Shift+M | 取消订阅 | -{% else %} - -| 键盘快捷键 | 描述 | -| ------------------------------------------ | ----- | -| E 或 I 或 Y | 标记为已读 | -| Shift+M | 静音线程 | -{% endif %} ## 网络图 diff --git a/translations/zh-CN/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/zh-CN/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md index 00a5333f72..ce5486664c 100644 --- a/translations/zh-CN/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md +++ b/translations/zh-CN/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md @@ -60,7 +60,6 @@ Gist supports mapping GeoJSON files. These maps are displayed in embedded gists, Follow the steps below to create a gist. -{% ifversion fpt or ghes or ghae or ghec %} {% note %} You can also create a gist using the {% data variables.product.prodname_cli %}. For more information, see "[`gh gist create`](https://cli.github.com/manual/gh_gist_create)" in the {% data variables.product.prodname_cli %} documentation. @@ -68,7 +67,6 @@ You can also create a gist using the {% data variables.product.prodname_cli %}. Alternatively, you can drag and drop a text file from your desktop directly into the editor. {% endnote %} -{% endif %} 1. Sign in to {% data variables.product.product_name %}. 2. Navigate to your {% data variables.gists.gist_homepage %}. diff --git a/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index b649f2889b..ac8a170a32 100644 --- a/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -29,18 +29,19 @@ shortTitle: 基本格式语法 ![突出显示目录图标的屏幕截图](/assets/images/help/repository/headings_toc.png) - ## 样式文本 -您可以在评论字段和 `.md` 文件中以粗体、斜体或删除线的文字表示强调。 +You can indicate emphasis with bold, italic, strikethrough, subscript, or superscript text in comment fields and `.md` files. -| 样式 | 语法 | 键盘快捷键 | 示例 | 输出 | -| -------- | ------------------ | ------------------------------------------------------------------------------------ | ------------------ | ---------------- | -| 粗体 | `** **` 或 `__ __` | Command+B (Mac) 或 Ctrl+B (Windows/Linux) | `**这是粗体文本**` | **这是粗体文本** | -| 斜体 | `* *` 或 `_ _`      | Command+I (Mac) 或 Ctrl+I (Windows/Linux) | `*这是斜体文本*` | *这是斜体文本* | -| 删除线 | `~~ ~~` | | `~~这是错误文本~~` | ~~这是错误文本~~ | -| 粗体和嵌入的斜体 | `** **` 和 `_ _` | | `**此文本 _非常_ 重要**` | **此文本_非常_重要** | -| 全部粗体和斜体 | `*** ***` | | `***所有这些文本都很重要***` | ***所有这些文本都是斜体*** | +| 样式 | 语法 | 键盘快捷键 | 示例 | 输出 | +| ----------- | -------------------------- | ------------------------------------------------------------------------------------ | --------------------------------------------------- | ------------------------------------- | +| 粗体 | `** **` 或 `__ __` | Command+B (Mac) 或 Ctrl+B (Windows/Linux) | `**这是粗体文本**` | **这是粗体文本** | +| 斜体 | `* *` 或 `_ _`      | Command+I (Mac) 或 Ctrl+I (Windows/Linux) | `*这是斜体文本*` | *这是斜体文本* | +| 删除线 | `~~ ~~` | | `~~这是错误文本~~` | ~~这是错误文本~~ | +| 粗体和嵌入的斜体 | `** **` 和 `_ _` | | `**此文本 _非常_ 重要**` | **此文本_非常_重要** | +| 全部粗体和斜体 | `*** ***` | | `***所有这些文本都很重要***` | ***所有这些文本都是斜体*** | +| Subscript | ` ` | | `This is a subscript text` | This is a subscript text | +| Superscript | ` ` | | `This is a superscript text` | This is a superscript text | ## 引用文本 @@ -235,7 +236,7 @@ git commit ## 提及人员和团队 -您可以在 {% data variables.product.product_name %} 上提及人员或[团队](/articles/setting-up-teams/)，方法是键入 @ 加上其用户名或团队名称。 这将触发通知并提请他们注意对话。 如果您在编辑的评论中提及某人的用户名或团队名称，该用户也会收到通知。 有关通知的更多信息，请参阅{% 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 %}”。 +您可以在 {% data variables.product.product_name %} 上提及人员或[团队](/articles/setting-up-teams/)，方法是键入 @ 加上其用户名或团队名称。 这将触发通知并提请他们注意对话。 如果您在编辑的评论中提及某人的用户名或团队名称，该用户也会收到通知。 有关通知的详细信息，请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications)”。 {% note %} @@ -296,7 +297,7 @@ git commit 通过在文本行之间留一个空白行，可创建新段落。 -{% ifversion fpt or ghae-issue-5180 or ghes > 3.2 or ghec %} +{% ifversion fpt or ghae or ghes > 3.2 or ghec %} ## 脚注 您可以使用此括号语法为您的内容添加脚注： diff --git a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/index.md b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/index.md index 5ceac9e057..7dd29b38f2 100644 --- a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/index.md +++ b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/index.md @@ -14,6 +14,7 @@ children: - /organizing-information-with-collapsed-sections - /creating-and-highlighting-code-blocks - /creating-diagrams + - /writing-mathematical-expressions - /autolinked-references-and-urls - /attaching-files - /creating-a-permanent-link-to-a-code-snippet diff --git a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md index 54e06fa175..dd19fe4f50 100644 --- a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md +++ b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md @@ -15,7 +15,7 @@ topics: ## 将拉取请求链接到议题 -要将拉取请求链接到议题以{% ifversion fpt or ghes or ghae or ghec %} 显示正在进行的修复，并且{% endif %} 当有人合并拉取请求时自动关闭议题，请键入以下关键字之一，然后引用议题。 例如 `Closes #10` 或 `Fixes octo-org/octo-repo#100`。 +要将拉取请求链接到议题以 显示正在进行的修复，并且 当有人合并拉取请求时自动关闭议题，请键入以下关键字之一，然后引用议题。 例如 `Closes #10` 或 `Fixes octo-org/octo-repo#100`。 * close * closes diff --git a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md new file mode 100644 index 0000000000..99872a8016 --- /dev/null +++ b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md @@ -0,0 +1,59 @@ +--- +title: Writing mathematical expressions +intro: 'Use Markdown to display mathematical expressions on {% data variables.product.company_short %}.' +versions: + feature: math +shortTitle: Mathematical expressions +--- + +To enable clear communication of mathematical expressions, {% data variables.product.product_name %} supports LaTeX formatted math within Markdown. For more information, see [LaTeX/Mathematics](http://en.wikibooks.org/wiki/LaTeX/Mathematics) in Wikibooks. + +{% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide). + +## Writing inline expressions + +To include a math expression inline with your text, delimit the expression with a dollar symbol `$`. + +``` +This sentence uses `$` delimiters to show math inline: $\sqrt{3x-1}+(1+x)^2$ +``` + +![Inline math markdown rendering](/assets/images/help/writing/inline-math-markdown-rendering.png) + +## Writing expressions as blocks + +To add a math expression as a block, start a new line and delimit the expression with two dollar symbols `$$`. + +``` +**The Cauchy-Schwarz Inequality** + +$$\left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right)$$ +``` + +![Math expression as a block rendering](/assets/images/help/writing/math-expression-as-a-block-rendering.png) + +## Writing dollar signs in line with and within mathematical expressions + +To display a dollar sign as a character in the same line as a mathematical expression, you need to escape the non-delimiter `$` to ensure the line renders correctly. + + - Within a math expression, add a `\` symbol before the explicit `$`. + + ``` + This expression uses `\$` to display a dollar sign: $\sqrt{\$4}$ + ``` + + ![Dollar sign within math expression](/assets/images/help/writing/dollar-sign-within-math-expression.png) + + - Outside a math expression, but on the same line, use span tags around the explicit `$`. + + ``` + To split $100 in half, we calculate $100/2$ + ``` + + ![Dollar sign inline math expression](/assets/images/help/writing/dollar-sign-inline-math-expression.png) + +## 延伸阅读 + +* [The MathJax website](http://mathjax.org) +* [开始在 GitHub 上编写和格式化](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github) +* [GitHub Flavored Markdown Spec](https://github.github.com/gfm/) diff --git a/translations/zh-CN/content/github/copilot/about-github-copilot-telemetry.md b/translations/zh-CN/content/github/copilot/about-github-copilot-telemetry.md index b4592764f1..63d1ee158a 100644 --- a/translations/zh-CN/content/github/copilot/about-github-copilot-telemetry.md +++ b/translations/zh-CN/content/github/copilot/about-github-copilot-telemetry.md @@ -9,7 +9,7 @@ versions: ## 哪些数据会被收集？ -收集的数据在“[{% data variables.product.prodname_copilot %} 遥测术语](/github/copilot/github-copilot-telemetry-terms)”中进行了描述。 此外，{% data variables.product.prodname_copilot %} 扩展/插件从用户的集成开发环境 (IDE) 收集活动（绑定到时间戳）以及扩展/插件遥测包收集的元数据。 当与 Visual Studio Code、IntelliJ、NeoVIM 或其他 IDE 一起使用时，{% data variables.product.prodname_copilot %} 会收集这些 IDE 提供的标准元数据。 +收集的数据在“[{% data variables.product.prodname_copilot %} 遥测术语](/github/copilot/github-copilot-telemetry-terms)”中进行了描述。 此外，{% data variables.product.prodname_copilot %} 扩展/插件从用户的集成开发环境 (IDE) 收集活动（绑定到时间戳）以及扩展/插件遥测包收集的元数据。 When used with {% data variables.product.prodname_vscode %}, IntelliJ, NeoVIM, or other IDEs, {% data variables.product.prodname_copilot %} collects the standard metadata provided by those IDEs. ## {% data variables.product.company_short %} 如何使用数据 diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md index 1ee95562f5..99a00938fd 100644 --- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md +++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md @@ -30,8 +30,8 @@ shortTitle: 在板上筛选卡 - 使用 `status:pending`、`status:success` 或 `status:failure` 按检查状态过滤 - 使用 `type:issue`、`type:pr` 或 `type:note` 按类型过滤卡 - 使用 `is:open`、`is:closed` 或 `is:merged` 和 `is:issue`、`is:pr` 或 `is:note` 按状态和类型过滤卡 -- 使用 `linked:pr` 关闭引用，按链接到拉取请求的议题过滤卡{% ifversion fpt or ghes or ghae or ghec %} -- 使用 `repo:ORGANIZATION/REPOSITORY` 在组织范围的项目板中按仓库过滤卡{% endif %} +- 使用 `linked:pr`，按通过结束引用链接到拉取请求的问题筛选卡片 +- 使用 `repo:ORGANIZATION/REPOSITORY` 在组织范围的项目板中按仓库过滤卡 1. 导航到包含要过滤的卡的项目板。 2. 在项目卡列上方，单击“Filter cards（过滤卡）”搜索栏并键入搜索查询以过滤卡。 ![过滤卡搜索栏](/assets/images/help/projects/filter-card-search-bar.png) diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md index aee10389f1..7b9a23e3fd 100644 --- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/about-issues.md @@ -22,7 +22,7 @@ topics: 议题让您可以在进行开发的 {% data variables.product.company_short %} 上跟踪您的工作。 当您在议题中提到另一个议题或拉取请求时，该议题的时间表会反映交叉参考，以便你能够跟踪相关的工作。 要表示工作正在进行中，您可以将议题链接到拉取请求。 当拉取请求合并时，链接的议题会自动关闭。 -有关关键词的更多信息，请参阅“[将拉取请求链接到议题](issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)”。 +有关关键词的更多信息，请参阅“[将拉取请求链接到议题](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)”。 ## 快速创建议题 @@ -36,7 +36,7 @@ topics: ## 保持更新 -为保持更新议题中的最新评论，您可以订阅议题以接收关于最新评论的通知。 要快速查找指向您订阅的最新议题的链接，请访问仪表板。 更多信息请参阅 {% 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 %}”和“[关于个人仪表板](/articles/about-your-personal-dashboard)”。 +为保持更新议题中的最新评论，您可以订阅议题以接收关于最新评论的通知。 要快速查找指向您订阅的最新议题的链接，请访问仪表板。 更多信息请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications)”和“[关于个人仪表板](/articles/about-your-personal-dashboard)”。 ## 社区管理 diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md index a032720e8b..ebea410353 100644 --- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md @@ -19,7 +19,9 @@ shortTitle: 分配议题和 PR ## 关于议题和拉取请求受理人 -每个议题和拉取请求最多可分配给 10 个人，包括您自己、 任何评论了议题或拉取请求的人、任何对仓库有写入权限的人以及对仓库有读取权限的组织成员 。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/articles/access-permissions-on-github)”。 +每个议题和拉取请求可分配给多个人，包括您自己、 任何评论了议题或拉取请求的人、任何对仓库有写入权限的人以及对仓库有读取权限的组织成员 。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/articles/access-permissions-on-github)”。 + +公共仓库和付费帐户的私有仓库中的议题和拉取请求最多可以分配 10 个人。 免费计划中的私有仓库限制为每个议题或拉取请求一个人。 ## 分配单个议题或拉取请求 diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index ad62276d24..06a51f32d5 100644 --- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -173,11 +173,9 @@ gh pr list --search "team:octo-org/octo-team" {% endtip %} {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} 对于议题，您还可以使用搜索来： - 通过关闭引用过滤链接到拉取请求的议题：`linked:pr` -{% endif %} 对于拉取请求，您还可以使用搜索来： - 过滤[草稿](/articles/about-pull-requests#draft-pull-requests)拉取请求：`is:draft` @@ -188,8 +186,8 @@ gh pr list --search "team:octo-org/octo-team" - 按[审查者](/articles/about-pull-request-reviews/)过滤拉取请求：`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)的特定用户过滤拉取请求：`state:open type:pr review-requested:octocat`{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} - 过滤有人直接要求您审核的拉取请求：`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 %} -- 过滤链接到拉取请求可能关闭的议题的拉取请求：`linked:issue`{% endif %} +- 按请求审查的团队过滤拉取请求：`state:open type:pr team-review-requested:github/atom` +- 过滤链接到拉取请求可能关闭的议题的拉取请求：`linked:issue` ## 排序议题和拉取请求 @@ -211,7 +209,6 @@ gh pr list --search "team:octo-org/octo-team" 要清除您的排序选择，请单击 **Sort（排序）<**>**Newest（最新）**。 - ## 共享过滤器 当您过滤或排序议题和拉取请求时，浏览器的 URL 自动更新以匹配新视图。 diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md index bd0de520e2..6b6714dd60 100644 --- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md @@ -27,7 +27,7 @@ shortTitle: 将 PR 链接到议题 ## 关于链接的议题和拉取请求 -您可以{% ifversion fpt or ghes or ghae or ghec %}手动或{% endif %}使用拉取请求说明中支持的关键词将议题链接到拉取请求。 +您可以手动将议题链接到拉取请求，也可以使用拉取请求描述中的受支持关键字。 当您将拉取请求链接到拉取请求指向的议题，如果有人正在操作该议题，协作者可以看到。 @@ -57,11 +57,10 @@ shortTitle: 将 PR 链接到议题 | 不同仓库中的议题 | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100` | | 多个议题 | 对每个议题使用完整语法 | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` | -{% ifversion fpt or ghes or ghae or ghec %}只有手动链接的拉取请求才能手动取消链接。 要取消链接您使用关键词链接的议题，必须编辑拉取请求说明以删除该关键词。{% endif %} +只能手动取消链接手动链接的拉取请求。 要取消链接您使用关键词链接的议题，必须编辑拉取请求说明以删除该关键词。 您也可以在提交消息中使用关闭关键词。 议题将在提交合并到默认分支时关闭，但包含提交的拉取请求不会列为链接的拉取请求。 -{% ifversion fpt or ghes or ghae or ghec %} ## 手动将拉取请求链接到议题 对仓库有写入权限的任何人都可以手动将拉取请求链接到议题。 @@ -77,7 +76,6 @@ shortTitle: 将 PR 链接到议题 4. 在右侧边栏中，单击 **Linked issues（链接的议题）**。 ![右侧边栏中链接的议题](/assets/images/help/pull_requests/linked-issues.png) {% endif %} 5. 单击要链接到拉取请求的议题。 ![下拉以链接议题](/assets/images/help/pull_requests/link-issue-drop-down.png) -{% endif %} ## 延伸阅读 diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md index c678256c83..6db1d70b58 100644 --- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md @@ -25,4 +25,4 @@ type: how_to ## 延伸阅读 -- {% ifversion fpt or ghes or ghae or ghec %}”[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}”[列出您关注的仓库](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}" +- “[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching)” diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md index e1031f9737..591804ad85 100644 --- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md +++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md @@ -35,7 +35,7 @@ shortTitle: 组织仪表板 在消息馈送的“All activity（所有活动）”部分，您可以查看来自组织中其他团队和仓库的更新。 -“All activity（所有活动）”部分显示组织中所有最近的活动，包括您未订阅的仓库中以及您未关注的人员的活动。 更多信息请参阅{% 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/watching-and-unwatching-repositories){% endif %}”和“[关注人员](/articles/following-people)”。 +“All activity（所有活动）”部分显示组织中所有最近的活动，包括您未订阅的仓库中以及您未关注的人员的活动。 更多信息请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications)”和“[关注人员](/articles/following-people)”。 例如，当组织中有人执行以下操作时，组织消息馈送会显示更新： - 创建新分支。 diff --git a/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md index a639d9cfa2..1a25435c7c 100644 --- a/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md +++ b/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md @@ -32,7 +32,7 @@ topics: {% tip %} -**提示：**根据通知设置，您将通过电子邮件和/或 {% data variables.product.product_name %} 上的 web 通知页面收到更新。 更多信息请参阅{% ifversion fpt or ghae or ghes or ghec %}“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}“[关于电子邮件通知](/github/receiving-notifications-about-activity-on-github/about-email-notifications)”和“[关于 web 通知](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}”。 +**提示：**根据通知设置，您将通过电子邮件和/或 {% data variables.product.product_name %} 上的 web 通知页面收到更新。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)”。 {% endtip %} @@ -40,7 +40,7 @@ topics: 要关闭团队讨论的通知，您可以取消订阅特定的讨论帖子，或者更改通知设置，以取消关注或完全忽略特定团队的讨论。 即使您取消关注团队的讨论，也可订阅特定讨论帖子的通知。 -更多信息请参阅{% ifversion fpt or ghae or ghes or ghec %}“[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}“[订阅和退订通知](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}”和“[嵌套的团队](/articles/about-teams/#nested-teams)”。 +更多信息请参阅“[查看订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)”和“[嵌套团队](/articles/about-teams/#nested-teams)”。 {% ifversion fpt or ghec %} 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 index 8fd6ad0d77..31574c549c 100644 --- 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 @@ -162,5 +162,5 @@ You can manage access to {% data variables.product.prodname_GH_advanced_security - "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %} - "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %} -- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae-issue-4864 %} +- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae %} - "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)"{% endif %} 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 index 40c99ceccc..401665144c 100644 --- 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 @@ -41,7 +41,7 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." | [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing. | [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. | -| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %} | [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/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.{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %} | [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." @@ -61,8 +61,8 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | {% endif %} | [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion ghec %} | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %} -| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} +| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %} +| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization. | [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps. | [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %} | [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} @@ -75,7 +75,7 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae or ghec %} | [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% if secret-scanning-audit-log-custom-patterns %} | [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% if secret-scanning-audit-log-custom-patterns %} -| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %} | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %} | [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% if custom-repository-roles %} | [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %} @@ -236,7 +236,7 @@ An overview of some of the most common actions that are recorded as events in th | `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). {% endif %} -{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{% ifversion fpt or ghec or ghes > 3.2 or ghae %} ### `dependabot_alerts` category actions | Action | Description @@ -497,7 +497,6 @@ For more information, see "[Managing the publication of {% data variables.produc | `delete` | Triggered when a custom pattern is removed from secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)." {% endif %} -{% ifversion fpt or ghes or ghae or ghec %} ### `organization_label` category actions | Action | Description @@ -506,8 +505,6 @@ For more information, see "[Managing the publication of {% data variables.produc | `update` | Triggered when a default label is edited. | `destroy` | Triggered when a default label is deleted. -{% endif %} - ### `oauth_application` category actions | Action | Description @@ -572,11 +569,10 @@ For more information, see "[Managing the publication of {% data variables.produc | `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch. | `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed. | `rejected_ref_update ` | Triggered when a branch update attempt is rejected. -| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.{% ifversion fpt or ghes or ghae or ghec %} +| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator. | `update_allow_force_pushes_enforcement_level ` | Triggered when force pushes are enabled or disabled for a protected branch. | `update_allow_deletions_enforcement_level ` | Triggered when branch deletion is enabled or disabled for a protected branch. | `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch. -{% endif %} {% ifversion fpt or ghes > 3.1 or ghae or ghec %} @@ -707,7 +703,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." | `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a repository. -{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% endif %}{% ifversion fpt or ghes or ghae or ghec %} ### `repository_vulnerability_alert` category actions | Action | Description diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index ec169b0963..e0c81ef0fc 100644 --- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -158,25 +158,25 @@ shortTitle: 存储库角色 在本节中，您可以找到一些安全功能所需的访问权限，例如 {% data variables.product.prodname_advanced_security %} 功能。 -| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | -|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------------:|{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| 接收仓库中[易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) | | | | | **X** | -| [忽略 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %} +| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 | +|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------:|{% ifversion fpt or ghes or ghae or ghec %} +| 接收仓库中[易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) | | | | | **X** | +| [忽略 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | -| [指定其他人员或团队接收安全警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| 创建[安全通告](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [指定其他人员或团队接收安全警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} +| 创建[安全通告](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} | -| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”） | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} +| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”） | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} | -| 为私有仓库[启用依赖关系图](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 or ghec %} -| [查看依赖项审查](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** +| 为私有仓库[启用依赖关系图](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae or ghec %} +| [查看依赖项审查](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** {% endif %} -| [查看拉取请求上的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [列出、忽略和删除 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | -| [查看仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} +| [查看拉取请求上的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | +| [列出、忽略和删除 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | +| [查看仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} | -| [解决、撤销或重新打开 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %} -| [指定其他人员或团队接收仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** +| [解决、撤销或重新打开 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [指定其他人员或团队接收仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** {% endif %} [1] 仓库作者和维护者只能看到他们自己提交的警报信息。 diff --git a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md index bc90f157c3..83d6fd03f9 100644 --- a/translations/zh-CN/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md @@ -5,8 +5,6 @@ permissions: Organization owners can export member information for their organiz versions: fpt: '*' ghec: '*' - ghes: '>=3.3' - ghae: issue-5146 topics: - Organizations - Teams diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/zh-CN/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md index e548939557..14632f6214 100644 --- a/translations/zh-CN/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md +++ b/translations/zh-CN/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -26,8 +26,8 @@ shortTitle: 将组织转换为用户 2. [将用户的角色更改为所有者](/articles/changing-a-person-s-role-to-owner)。 3. {% data variables.product.signin_link %} 到新个人帐户。 4. [将每个组织仓库转让](/articles/how-to-transfer-a-repository)给新个人帐户。 -5. [重命名组织](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username)以使当前用户名可用。 -6. [将用户重命名](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username)为组织的名称。 +5. [重命名组织](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username)以使当前用户名可用。 +6. [将用户重命名](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username)为组织的名称。 7. [删除组织](/organizations/managing-organization-settings/deleting-an-organization-account)。 diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md index 0929dece62..3fce3a8cc6 100644 --- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md @@ -2,8 +2,6 @@ title: 管理组织中的安全管理员 intro: 通过将团队分配给安全管理员角色，您可以为安全团队提供他们对组织所需的最少访问权限。 versions: - fpt: '*' - ghes: '>=3.3' feature: security-managers topics: - Organizations @@ -30,7 +28,7 @@ permissions: Organization owners can assign the security manager role. 其他功能（包括组织的安全概述）在将 {% data variables.product.prodname_ghe_cloud %} 与 {% data variables.product.prodname_advanced_security %} 一起使用的组织中可用。 更多信息请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)。 {% endif %} -如果团队具有安全管理员角色，则对团队和特定存储库具有管理员访问权限的人员可以更改团队对该存储库的访问级别，但不能删除访问权限。 更多信息请参阅“[管理团队对组织存储库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion ghes %}”。{% else %} 和“[管理可以访问存储库的团队和人员](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)”。{% endif %} +如果团队具有安全管理员角色，则对团队和特定存储库具有管理员访问权限的人员可以更改团队对该存储库的访问级别，但不能删除访问权限。 更多信息请参阅“[管理团队对组织存储库的访问权限](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %}”和“[管理有权访问存储库的团队和人员](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)”。{% else %}”。{% endif %} ![使用安全管理器管理存储库访问 UI](/assets/images/help/organizations/repo-access-security-managers.png) diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md index 779f1e4e4d..77c7bbd6b6 100644 --- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md @@ -146,7 +146,7 @@ shortTitle: 组织中的角色 {% endif %} | 管理组织中的拉取请求审核（请参阅“[管理组织中的拉取请求审核](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)”） | **X** | | | | | -{% elsif ghes > 3.2 or ghae-issue-4999 %} +{% elsif ghes > 3.2 or ghae %} | 组织操作 | 所有者 | 成员 | 安全管理员 | diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md index 052dc5b6af..a48986bd53 100644 --- a/translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md @@ -37,7 +37,7 @@ You can also use LDAP Sync to synchronize {% data variables.product.product_loca {% data reusables.organizations.types-of-team-visibility %} -You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)." +You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)." ## Team pages diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md index 0c519a18d0..b6a396046a 100644 --- a/translations/zh-CN/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md +++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md @@ -31,11 +31,10 @@ permissions: Organization owners can promote team members to team maintainers. - [删除团队讨论](/articles/managing-disruptive-comments/#deleting-a-comment) - [添加组织成员到团队](/articles/adding-organization-members-to-a-team) - [从团队中删除组织成员](/articles/removing-organization-members-from-a-team) -- 删除团队对仓库的访问权限{% ifversion fpt or ghes or ghae or ghec %} -- [管理团队的代码审查任务](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% ifversion fpt or ghec %} +- 删除团队对仓库的访问权限 +- [管理团队的代码审查任务](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% ifversion fpt or ghec %} - [管理拉取请求的预定提醒](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %} - ## 将组织成员升级为团队维护员 在将组织成员提升为团队维护员之前，该人员必须已经是团队的成员。 diff --git a/translations/zh-CN/content/pages/index.md b/translations/zh-CN/content/pages/index.md index 763747d186..70438f474b 100644 --- a/translations/zh-CN/content/pages/index.md +++ b/translations/zh-CN/content/pages/index.md @@ -1,7 +1,34 @@ --- title: GitHub Pages 文档 shortTitle: GitHub Pages -intro: '您可以直接从 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 的仓库创建网站。' +intro: '了解如何直接从 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 的仓库创建网站。 探索像Jekyll这样的网站建设工具，并解决 {% data variables.product.prodname_pages %} 网站的问题。' +introLinks: + quickstart: /pages/quickstart + overview: /pages/getting-started-with-github-pages/about-github-pages +featuredLinks: + guides: + - /pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site + - /pages/getting-started-with-github-pages/creating-a-github-pages-site + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll{% endif %}' + - '{% ifversion ghec %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site{% endif %}' + - '{% ifversion fpt %}/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll{% endif %}' + popular: + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages{% endif %}' + - /pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll) + - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages{% endif %}' + - '{% ifversion fpt or ghec %}/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https{% endif %}' + - '{% ifversion ghes or ghae %}/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll{% endif %}' + - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll{% endif %}' + guideCards: + - /pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site + - /pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll + - /pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites +changelog: + label: pages +layout: product-landing redirect_from: - /categories/20/articles - /categories/95/articles diff --git a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md index 92c3653e6b..88f387e8f1 100644 --- a/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md +++ b/translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md @@ -49,7 +49,7 @@ shortTitle: 将主题添加到 Pages 站点 --- --- - @import "{{ site.theme }}"; + @import "{% raw %}{{ site.theme }}{% endraw %}"; ``` 3. 在 `@import` 行的后面直接添加您喜欢的任何自定义 CSS 或 Sass（包括导入）。 diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md index 98ff48b2a9..3a1844d9f6 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md @@ -24,13 +24,17 @@ topics: ### 合并压缩合并的消息 -在压缩与合并时，{% data variables.product.prodname_dotcom %} 生成提交消息，您可以根据需要更改该消息。 消息默认值取决于拉取请求是包含多个提交还是只包含一个。 在计算提交总数时，我们不包括合并提交。 +When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. The default message depends on the number of commits in the pull request, not including merge commits. | 提交数 | 摘要 | 描述 | | ---- | -------------------- | ------------------- | | 一个提交 | 单个提交的提交消息标题，后接拉取请求编号 | 单个提交的提交消息正文 | | 多个提交 | 拉取请求标题，后接拉取请求编号 | 按日期顺序列出所有被压缩提交的提交消息 | +{% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %} +People with admin access to a repository can configure the repository to use the title of the pull request as the default merge message for all squashed commits. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)". +{% endif %} + ### 压缩与合并长运行分支 如果计划在合并拉取请求后继续操作[头部分支](/github/getting-started-with-github/github-glossary#head-branch)，建议不要压缩与合并拉取请求。 diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md index 0b8bd5a96e..e761a84d41 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md @@ -1,6 +1,6 @@ --- title: 更改拉取请求的阶段 -intro: '您可以将拉取请求草稿标记为可供审查{% ifversion fpt or ghae or ghes or ghec %}或将拉取请求转换为草稿{% endif %}。' +intro: 您可以将草稿拉取请求标记为已准备好进行审查，或将拉取请求转换为草稿。 permissions: People with write permissions to a repository and pull request authors can change the stage of a pull request. product: '{% data reusables.gated-features.draft-prs %}' redirect_from: @@ -22,20 +22,16 @@ shortTitle: 更改状态 {% data reusables.pull_requests.mark-ready-review %} -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **提示**：您也可以使用 {% data variables.product.prodname_cli %} 将拉取请求标记为可供审查。 更多信息请参阅 {% data variables.product.prodname_cli %} 文档中的“[`gh pr 准备`](https://cli.github.com/manual/gh_pr_ready)”。 {% endtip %} -{% endif %} {% data reusables.repositories.sidebar-pr %} 2. 在“Pull Requests（拉取请求）”列表中，单击要标记为可供审查的拉取请求。 3. 在合并框中，单击 **Ready for review（可供审查）**。 ![可供审查按钮](/assets/images/help/pull_requests/ready-for-review-button.png) -{% ifversion fpt or ghae or ghes or ghec %} - ## 将拉取请求转换为草稿 您可以随时将拉取请求转换为草稿。 例如，如果您意外打开了拉取请求而不是草稿，或者收到了需要解决的关于拉取请求的反馈，则可将拉取请求转换为草稿，以表示需要进一步更改。 再次将拉取请求标记为可供审查之前，任何人都不能合并拉取请求。 将拉取请求转换为草稿时，已订阅拉取请求通知的用户将不会取消订阅。 @@ -45,8 +41,6 @@ shortTitle: 更改状态 3. 在右侧边栏中的“Reviewers（审查者）”下下单击 **Convert to draft（转换为草稿）**。 ![转换为草稿链接](/assets/images/help/pull_requests/convert-to-draft-link.png) 4. 单击 **Convert to draft（转换为草稿）**。 ![转换为草稿确认](/assets/images/help/pull_requests/convert-to-draft-dialog.png) -{% endif %} - ## 延伸阅读 - "[关于拉取请求](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)" diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md index d41af78d62..c49dcb8962 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md @@ -21,7 +21,7 @@ shortTitle: 请求 PR 审查 要将审阅者分配给拉取请求，您需要对存储库具有写入权限。 有关仓库访问权限的更多信息，请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 如果您具有写入权限，则可以将具有读取访问权限的任何人分配到存储库作为审阅者。 -具有写入权限的组织成员还可以将拉取请求审阅分配给对存储库具有读取访问权限的任何人员或团队。 被请求的审查者或团队将收到您请求他们审查拉取请求的通知。 {% ifversion fpt or ghae or ghes or ghec %}如果您请求团队审查，并且启用了代码审查分配，则会向特定成员发出申请，并且取消团队作为审查者。 更多信息请参阅“[管理团队的代码审查设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)”。{% endif %} +具有写入权限的组织成员还可以将拉取请求审阅分配给对存储库具有读取访问权限的任何人员或团队。 被请求的审查者或团队将收到您请求他们审查拉取请求的通知。 如果您请求团队审查，并且启用了代码审查分配，则会向特定成员发出申请，并且取消团队作为审查者。 更多信息请参阅“[管理团队的代码审查设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)”。 {% note %} diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md index 435df2b4a3..ce080a675e 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md @@ -22,7 +22,7 @@ shortTitle: 关于 PR 审查 {% if pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %} -仓库所有者和协作者可向具体的个人申请拉取请求审查。 组织成员也可向具有仓库读取权限的团队申请拉取请求审查。 更多信息请参阅“[申请拉取请求审查](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)”。 {% ifversion fpt or ghae or ghes or ghec %}您可以指定自动分配一部分团队成员，而不是分配整个团队。 更多信息请参阅“[管理团队的代码审查设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)”。{% endif %} +仓库所有者和协作者可向具体的个人申请拉取请求审查。 组织成员也可向具有仓库读取权限的团队申请拉取请求审查。 更多信息请参阅“[申请拉取请求审查](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)”。 您可以指定要在整个团队的位置自动分配的团队成员子集。 更多信息请参阅“[管理团队的代码审查设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)”。 审查允许讨论提议的更改，帮助确保更改符合仓库的参与指南及其他质量标准。 您可以在 CODEOWNERS 文件中定义哪些个人或团队拥有代码的特定类型或区域。 当拉取请求修改定义了所有者的代码时，该个人或团队将自动被申请为审查者。 更多信息请参阅“[关于代码所有者](/articles/about-code-owners/)”。 diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md index 0b5390b25d..333149afce 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md @@ -5,7 +5,7 @@ product: '{% data reusables.gated-features.dependency-review %}' versions: fpt: '*' ghes: '>= 3.2' - ghae: issue-4864 + ghae: '*' ghec: '*' type: how_to topics: diff --git a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md index 866e317285..9b9e130121 100644 --- a/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md +++ b/translations/zh-CN/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md @@ -31,9 +31,9 @@ versions: ## 比较标记 -比较发行版标记将显示自上次发布以来您对仓库的更改。 {% ifversion fpt or ghae or ghes or ghec %} 更多信息请参阅“[比较发行版](/github/administering-a-repository/comparing-releases)”。{% endif %} +比较发行版标记将显示自上次发布以来您对仓库的更改。 更多信息请参阅“[比较发行版](/github/administering-a-repository/comparing-releases)”。 -{% ifversion fpt or ghae or ghes or ghec %}要比较标记，可以从页面顶部的 `compare` 下拉菜单选择标记名称。{% else %} 不是键入分支名称，而是键入 `compare` 下拉菜单中的标记名称。{% endif %} +要比较标记，您可以从页面顶部的 `compare（比较）`下拉菜单中选择标记名称。 此处是[在两个标记之间进行比较](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3)的示例。 diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md index 49747d1b27..e2a506b530 100644 --- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md +++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md @@ -27,8 +27,7 @@ shortTitle: 关于合并方法 {% data reusables.pull_requests.default_merge_option %} -{% ifversion fpt or ghae or ghes or ghec %} -默认合并方法创建合并提交。 通过强制实施线性提交历史记录，可以防止任何人将合并提交推送到受保护分支。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-linear-history)”。{% endif %} +默认合并方法创建合并提交。 通过强制实施线性提交历史记录，可以防止任何人将合并提交推送到受保护分支。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-linear-history)”。 ## 压缩合并提交 diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md index 49ac86c24d..dada98ac8e 100644 --- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md +++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md @@ -63,9 +63,9 @@ shortTitle: 分支保护规则 - （可选）要在将代码修改提交推送到分支时忽略拉取请求批准审查，请选择 **Dismiss stale pull request approvals when new commits are pushed（推送新提交时忽略旧拉取请求批准）**。 ![在推送新提交时，关闭旧拉取请求批准的复选框](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) - （可选）要在拉取请求影响具有指定所有者的代码时要求代码所有者审查，请选择 **Require review from Code Owners（需要代码所有者审查）**。 更多信息请参阅“[关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners)”。 ![代码所有者的必需审查](/assets/images/help/repository/PR-review-required-code-owner.png) {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5611 %} - - （可选）若要允许特定人员或团队在需要时将代码推送到分支而不创建拉取请求，请选择 **Allow specific actors to bypass required pull requests（允许特定参与者绕过所需的拉取请求）**。 然后，搜索并选择应被允许跳过创建拉取请求的人员或团队。 ![允许特定执行者绕过拉取请求要求复选框](/assets/images/help/repository/PR-bypass-requirements.png) + - Optionally, to allow specific actors to push code to the branch without creating pull requests when they're required, select **Allow specified actors to bypass required pull requests**. Then, search for and select the actors who should be allowed to skip creating a pull request. ![Allow specific actors to bypass pull request requirements checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-bypass-requirements-with-apps.png){% else %}(/assets/images/help/repository/PR-bypass-requirements.png){% endif %} {% endif %} - - （可选）如果仓库属于组织，请选择 **Restrict who can dismiss pull request reviews（限制谁可以忽略拉取请求审查）**。 然后，搜索并选择有权忽略拉取请求审查的人员或团队。 更多信息请参阅“[忽略拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)”。 ![限制可以忽略拉取请求审查的人员复选框](/assets/images/help/repository/PR-review-required-dismissals.png) + - （可选）如果仓库属于组织，请选择 **Restrict who can dismiss pull request reviews（限制谁可以忽略拉取请求审查）**。 Then, search for and select the actors who are allowed to dismiss pull request reviews. 更多信息请参阅“[忽略拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)”。 ![Restrict who can dismiss pull request reviews checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-review-required-dismissals-with-apps.png){% else %}(/assets/images/help/repository/PR-review-required-dismissals.png){% endif %} 1. （可选）启用必需状态检查。 更多信息请参阅“[关于状态检查](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)”。 - 选中 **Require status checks to pass before merging（合并前必需状态检查通过）**。 ![必需状态检查选项](/assets/images/help/repository/required-status-checks.png) - （可选）要确保使用受保护分支上的最新代码测试拉取请求，请选择 **Require branches to be up to date before merging（要求分支在合并前保持最新）**。 ![宽松或严格的必需状态复选框](/assets/images/help/repository/protecting-branch-loose-status.png) @@ -95,7 +95,7 @@ shortTitle: 分支保护规则 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5624 %} 然后，选择谁可以强制推送到分支。 - 选择 **Everyone（每个人）**以允许至少具有存储库写入权限的每个人强制推送到分支，包括具有管理员权限的人员。 - - 选择 **Specify who can force push（指定谁可以强制推送）**，仅允许特定人员或团队强制推送到分支。 然后，搜索并选择这些人员或团队。 ![指定谁可以强制推送选项的屏幕截图](/assets/images/help/repository/allow-force-pushes-specify-who.png) + - Select **Specify who can force push** to allow only specific actors to force push to the branch. Then, search for and select those actors. ![Screenshot of the options to specify who can force push]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png){% else %}(/assets/images/help/repository/allow-force-pushes-specify-who.png){% endif %} {% endif %} 有关强制推送的详细信息，请参阅“[允许强制推送](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)”。 diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md index c4aadf7f4e..ff5e501eac 100644 --- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md +++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md @@ -37,14 +37,11 @@ remote: error: Required status check "ci-build" is failing {% endnote %} -{% ifversion fpt or ghae or ghes or ghec %} - ## 头部提交与测试合并提交之间的冲突 有时，测试合并提交与头部提交的状态检查结果存在冲突。 如果测试合并提交具有状态，则测试合并提交必须通过。 否则，必须传递头部提交的状态后才可合并该分支。 有关测试合并提交的更多信息，请参阅“[拉取](/rest/reference/pulls#get-a-pull-request)”。 ![具有冲突的合并提交的分支](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png) -{% endif %} ## 处理已跳过但需要检查 diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md index 4c7efb95b7..9b089273df 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md @@ -26,17 +26,15 @@ topics: {% endtip %} -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **提示**：您也可以使用 {% data variables.product.prodname_cli %} 创建仓库。 更多信息请参阅 {% data variables.product.prodname_cli %} 文档中的“[`gh 仓库创建`](https://cli.github.com/manual/gh_repo_create)”。 {% endtip %} -{% endif %} {% data reusables.repositories.create_new %} -2. （可选）要创建具有现有仓库的目录结构和文件的仓库，请使用 **Choose a template（选择模板）**下拉菜单并选择一个模板仓库。 您将看到由您和您所属组织拥有的模板仓库，或者您以前使用过的模板仓库。 更多信息请参阅“[从模板创建仓库](/articles/creating-a-repository-from-a-template)”。 ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png){% ifversion fpt or ghae or ghes or ghec %} -3. （可选）如果您选择使用模板，要包括模板中所有分支的目录结构和文件，而不仅仅是默认分支，请选择 **Include all branches（包括所有分支）**。 ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} +2. （可选）要创建具有现有仓库的目录结构和文件的仓库，请使用 **Choose a template（选择模板）**下拉菜单并选择一个模板仓库。 您将看到由您和您所属组织拥有的模板仓库，或者您以前使用过的模板仓库。 更多信息请参阅“[从模板创建仓库](/articles/creating-a-repository-from-a-template)”。 ![模板下拉菜单](/assets/images/help/repository/template-drop-down.png) +3. （可选）如果您选择使用模板，要包括模板中所有分支的目录结构和文件，而不仅仅是默认分支，请选择 **Include all branches（包括所有分支）**。 ![包括所有分支复选框](/assets/images/help/repository/include-all-branches.png) 3. 在“Owner（所有者）”下拉菜单中，选择要在其上创建仓库的帐户。 ![所有者下拉菜单](/assets/images/help/repository/create-repository-owner.png) {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %} diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md index 8dab5fd61c..8eb3f07a6e 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md @@ -19,17 +19,13 @@ shortTitle: 从模板创建 任何对模板仓库具有读取权限的人都可以从该模板创建仓库。 更多信息请参阅“[创建模板仓库](/articles/creating-a-template-repository)”。 -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **提示**：您也可以使用 {% data variables.product.prodname_cli %} 从模板创建仓库。 更多信息请参阅 {% data variables.product.prodname_cli %} 文档中的“[`gh 仓库创建`](https://cli.github.com/manual/gh_repo_create)”。 {% endtip %} -{% endif %} -{% ifversion fpt or ghae or ghes or ghec %} 您可以选择仅包括模板仓库的默认分支中的目录结构和文件，或者包括所有分支。 从模板创建的分支具有不相关的历史记录，这意味着您无法创建拉取请求或在分支之间合并。 -{% endif %} 从模板创建仓库类似于创建仓库的复刻，但存在一些重要差异： - 新的复刻包含父仓库的整个提交历史记录，而从模板创建的仓库从一个提交开始记录。 @@ -44,7 +40,7 @@ shortTitle: 从模板创建 2. 在文件列表上方，单击 **Use this template（使用此模板）**。 ![使用此模板按钮](/assets/images/help/repository/use-this-template-button.png) {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} -{% data reusables.repositories.choose-repo-visibility %}{% ifversion fpt or ghae or ghes or ghec %} -6. （可选）要包括模板中所有分支的目录结构和文件，而不仅仅是默认分支，请选择 **Include all branches（包括所有分支）**。 ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png){% endif %} +{% data reusables.repositories.choose-repo-visibility %} +6. （可选）要包括模板中所有分支的目录结构和文件，而不仅仅是默认分支，请选择 **Include all branches（包括所有分支）**。 ![包括所有分支复选框](/assets/images/help/repository/include-all-branches.png) {% data reusables.repositories.select-marketplace-apps %} 8. 单击 **Create repository from template（从模板创建仓库）**。 diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md index 3bc6209a8c..1986ddafb1 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md @@ -1,6 +1,6 @@ --- title: 创建模板仓库 -intro: '您可以将现有仓库设置为模板，以便您与其他人能够生成目录结构相同的新仓库{% ifversion fpt or ghae or ghes or ghec %}、分支{% endif %} 和文件。' +intro: 您可以将现有仓库设置为模板，以便您与其他人能够生成目录结构相同的新仓库、分支和文件。 permissions: Anyone with admin permissions to a repository can make the repository a template. redirect_from: - /articles/creating-a-template-repository @@ -24,7 +24,7 @@ shortTitle: 创建模板仓库 要创建模板仓库，必须先创建一个仓库，然后将该仓库设置为模板。 关于创建仓库的更多信息，请参阅“[创建新仓库](/articles/creating-a-new-repository)”。 -将仓库设置为模板后，有权访问仓库的任何人都可以生成与默认分支具有相同目录结构和文件的新仓库。{% ifversion fpt or ghae or ghes or ghec %} 他们还可以选择包含您的仓库中的所有其他分支。 从模板创建的分支具有不相关的历史记录，因此您无法创建拉取请求或在分支之间合并。{% endif %} 更多信息请参阅“[从模板创建仓库](/articles/creating-a-repository-from-a-template)”。 +将仓库设置为模板后，任何对该仓库有访问权限的人都可以生成与默认分支具有相同目录结构和文件的新仓库。 他们还可以选择在存储库中包含所有其他分支。 从模板创建的分支具有不相关的历史记录，这样您无法创建拉取请求或在分支之间合并。 更多信息请参阅“[从模板创建仓库](/articles/creating-a-repository-from-a-template)”。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md index 6169d3f79f..15e9b1da64 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md @@ -31,7 +31,7 @@ shortTitle: 用于推送的电子邮件通知 - 作为提交一部分所更改的文件 - 提交消息 -您可以过滤因推送到仓库而收到的电子邮件通知。 更多信息请参阅{% ifversion fpt or ghae or ghes or ghec %}“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}”[关于通知电子邮件](/github/receiving-notifications-about-activity-on-github/about-email-notifications)”。 您还可以对推送关闭电子邮件通知。 更多信息请参阅“[选择通知的递送方式](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}”。 +您可以过滤因推送到仓库而收到的电子邮件通知。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)”。 ## 对推送到仓库启用电子邮件通知 @@ -43,10 +43,5 @@ shortTitle: 用于推送的电子邮件通知 7. 单击 **Setup notifications（设置通知）**。 ![设置通知按钮](/assets/images/help/settings/setup_notifications_settings.png) ## 延伸阅读 -{% ifversion fpt or ghae or ghes or ghec %} - "[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" -{% else %} -- "[关于通知](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)" -- "[选择通知的递送方式](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)" -- "[关于电子邮件通知](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)" -- "[关于 web 通知](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)"{% endif %} + diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md index 4f0e7e8654..1c89e67c25 100644 --- a/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md +++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md @@ -32,7 +32,7 @@ topics: 发行版基于 [Git 标记](https://git-scm.com/book/en/Git-Basics-Tagging)，这些标记会标记仓库历史记录中的特定点。 标记日期可能与发行日期不同，因为它们可在不同的时间创建。 有关查看现有标记的更多信息，请参阅“[查看仓库的发行版和标记](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)”。 -当仓库中发布新发行版时您可以接收通知，但不会接受有关仓库其他更新的通知。 更多信息请参阅{% ifversion fpt or ghae or ghes or ghec %}“[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}”[关注和取消关注仓库的发行版](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-releases-for-a-repository){% endif %}”。 +当仓库中发布新发行版时您可以接收通知，但不会接受有关仓库其他更新的通知。 更多信息请参阅“[查看订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)”。 对仓库具有读取访问权限的任何人都可以查看和比较发行版，但只有对仓库具有写入权限的人员才能管理发行版。 更多信息请参阅“[管理仓库中的发行版](/github/administering-a-repository/managing-releases-in-a-repository)”。 @@ -40,6 +40,10 @@ topics: 您可以在管理版本时手动创建发行说明。 或者，您可以从默认模板自动生成发行说明，或自定义您自己的发行说明模板。 更多信息请参阅“[自动生成的发行说明](/repositories/releasing-projects-on-github/automatically-generated-release-notes)”。 {% endif %} +{% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7054 %} +When viewing the details for a release, the creation date for each release asset is shown next to the release asset. +{% endif %} + {% ifversion fpt or ghec %} 对仓库具有管理员权限的人可以选择是否将 {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) 对象包含在 {% data variables.product.product_name %} 为每个发行版创建的 ZIP 文件和 tarball 中。 更多信息请参阅“[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository)”。 @@ -48,7 +52,7 @@ topics: 您可以查看依赖项图的 **Dependents（依赖项）**选项卡，了解哪些仓库和包依赖于您仓库中的代码，并因此可能受到新发行版的影响。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 {% endif %} -您也可以使用发行版 API 来收集信息，例如人们下载发行版资产的次数。 更多信息请参阅“[发行版](/rest/reference/repos#releases)”。 +您也可以使用发行版 API 来收集信息，例如人们下载发行版资产的次数。 更多信息请参阅“[发行版](/rest/reference/releases)”。 {% ifversion fpt or ghec %} ## 存储和带宽配额 diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md index 7a6a9173a1..47746566e6 100644 --- a/translations/zh-CN/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md +++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md @@ -17,13 +17,11 @@ topics: shortTitle: 查看版本和标记 --- -{% ifversion fpt or ghae or ghes or ghec %} {% tip %} **提示**：您也可以使用 {% data variables.product.prodname_cli %} 查看发行版。 更多信息请参阅 {% data variables.product.prodname_cli %} 文档中的“[`gh 发行版视图`](https://cli.github.com/manual/gh_release_view)”。 {% endtip %} -{% endif %} ## 查看发行版 diff --git a/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md index 86db4cefb8..a1450f8cb1 100644 --- a/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md +++ b/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md @@ -64,7 +64,7 @@ shortTitle: 存储库之间的连接 {% data reusables.repositories.accessing-repository-graphs %} 3. 在左侧边栏中，单击 **Forks（复刻）**。 ![复刻选项卡](/assets/images/help/graphs/graphs-sidebar-forks-tab.png) -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} ## 查看仓库的依赖项 您可以使用依赖关系图来浏览仓库所依赖的代码。 diff --git a/translations/zh-CN/content/rest/enterprise-admin/audit-log.md b/translations/zh-CN/content/rest/enterprise-admin/audit-log.md index 20c66522df..4eb4702492 100644 --- a/translations/zh-CN/content/rest/enterprise-admin/audit-log.md +++ b/translations/zh-CN/content/rest/enterprise-admin/audit-log.md @@ -5,6 +5,7 @@ versions: fpt: '*' ghes: '>=3.3' ghec: '*' + ghae: '*' topics: - API miniTocMaxHeadingLevel: 3 diff --git a/translations/zh-CN/content/rest/guides/getting-started-with-the-checks-api.md b/translations/zh-CN/content/rest/guides/getting-started-with-the-checks-api.md index 11f50ee872..3ae85111e2 100644 --- a/translations/zh-CN/content/rest/guides/getting-started-with-the-checks-api.md +++ b/translations/zh-CN/content/rest/guides/getting-started-with-the-checks-api.md @@ -41,9 +41,7 @@ A check run is an individual test that is part of a check suite. Each run includ ![Check runs workflow](/assets/images/check_runs.png) -{% ifversion fpt or ghes or ghae or ghec %} If a check run is in a incomplete state for more than 14 days, then the check run's `conclusion` becomes `stale` and appears on {% data variables.product.prodname_dotcom %} as stale with {% octicon "issue-reopened" aria-label="The issue-reopened icon" %}. Only {% data variables.product.prodname_dotcom %} can mark check runs as `stale`. For more information about possible conclusions of a check run, see the [`conclusion` parameter](/rest/reference/checks#create-a-check-run--parameters). -{% endif %} As soon as you receive the [`check_suite`](/webhooks/event-payloads/#check_suite) webhook, you can create the check run, even if the check is not complete. You can update the `status` of the check run as it completes with the values `queued`, `in_progress`, or `completed`, and you can update the `output` as more details become available. A check run can contain timestamps, a link to more details on your external site, detailed annotations for specific lines of code, and information about the analysis performed. 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 4791afc212..726026840e 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 @@ -148,7 +148,7 @@ When authenticating, you should see your rate limit bumped to 5,000 requests an You can easily [create a **personal access token**][personal token] using your [Personal access tokens settings page][tokens settings]: -{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} {% warning %} To help keep your information secure, we highly recommend setting an expiration for your personal access tokens. @@ -164,7 +164,7 @@ To help keep your information secure, we highly recommend setting an expiration ![Personal Token selection](/assets/images/help/personal_token_ghae.png) {% endif %} -{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} API requests using an expiring personal access token will return that token's expiration date via the `GitHub-Authentication-Token-Expiration` header. You can use the header in your scripts to provide a warning message when the token is close to its expiration date. {% endif %} diff --git a/translations/zh-CN/content/rest/overview/libraries.md b/translations/zh-CN/content/rest/overview/libraries.md index fe8c8fe76f..96e2ed2dd2 100644 --- a/translations/zh-CN/content/rest/overview/libraries.md +++ b/translations/zh-CN/content/rest/overview/libraries.md @@ -141,9 +141,10 @@ topics: ### Rust -| 库名称 | 仓库 | -| ------------ | ------------------------------------------------------------- | -| **Octocrab** | [XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) | +| 库名称 | 仓库 | +| ------------ | ----------------------------------------------------------------- | +| **Octocrab** | [XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) | +| **Octocat** | [octocat-rs/octocat-rs](https://github.com/octocat-rs/octocat-rs) | ### Scala 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 1f7b2c54ac..7a2f660515 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 @@ -133,7 +133,7 @@ You will be unable to authenticate using your OAuth2 key and secret while in pri {% ifversion fpt or ghec %} -Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). +Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-apps). {% endif %} 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 3a3cf532c9..a235d91b87 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 @@ -87,7 +87,6 @@ shortTitle: 了解搜索语法 某些非字母数字符号（例如空格）会从引号内的代码搜索查询中删除，因此结果可能出乎意料。 -{% ifversion fpt or ghes or ghae or ghec %} ## 使用用户名的查询 如果搜索查询包含需要用户名的限定符，例如 `user`、`actor` 或 `assignee`，您可以使用任何 {% data variables.product.product_name %} 用户名指定特定人员，或使用 `@me` 指定当前用户。 @@ -98,4 +97,3 @@ shortTitle: 了解搜索语法 | `QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) 匹配已分配给结果查看者的议题 | `@me` 只能与限定符一起使用，而不能用作搜索词，例如 `@me main.workflow`。 -{% endif %} 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 dd13a0634d..6ddd17e18a 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 @@ -55,15 +55,12 @@ shortTitle: 搜索议题和 PR {% data reusables.pull_requests.large-search-workaround %} - | 限定符 | 示例 | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | user:USERNAME | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) 匹配含有 "ubuntu" 字样、来自 @defunkt 拥有的仓库的议题。 | | org:ORGNAME | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) 匹配 GitHub 组织拥有的仓库中的议题。 | | repo:USERNAME/REPOSITORY | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) 匹配来自 @mozilla 的 shumway 项目、在 2012 年 3 月之前创建的议题。 | - - ## 按开放或关闭状态搜索 您可以使用 `state` 或 `is` 限定符基于议题和拉取请求处于打开还是关闭状态进行过滤。 @@ -133,17 +130,15 @@ shortTitle: 搜索议题和 PR | involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** 匹配涉及 @defunkt 或 @jlord 的议题。 | | | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) 匹配涉及 @mdo 且正文中未包含 "bootstrap" 字样的议题。 | -{% ifversion fpt or ghes or ghae or ghec %} ## 搜索链接的议题和拉取请求 您可以将结果缩小到仅包括通过关闭引用链接到拉取请求的议题，或者链接到拉取请求可能关闭的议题的拉取请求。 -| 限定符 | 示例 | -| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) 匹配 `desktop/desktop` 仓库中通过关闭引用链接到拉取请求的开放议题。 | -| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) 匹配 `desktop/desktop` 仓库中链接到拉取请求可能已关闭的议题的已关闭拉取请求。 | -| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) 匹配 `desktop/desktop` 仓库中未通过关闭引用链接到拉取请求的开放议题。 | -| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) 匹配 `desktop/desktop` 仓库中未链接至拉取请求可能关闭的议题的开放拉取请求。 -{% endif %} +| 限定符 | 示例 | +| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) 匹配 `desktop/desktop` 仓库中通过关闭引用链接到拉取请求的开放议题。 | +| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) 匹配 `desktop/desktop` 仓库中链接到拉取请求可能已关闭的议题的已关闭拉取请求。 | +| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) 匹配 `desktop/desktop` 仓库中未通过关闭引用链接到拉取请求的开放议题。 | +| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) 匹配 `desktop/desktop` 仓库中未链接至拉取请求可能关闭的议题的开放拉取请求。 | ## 按标签搜索 @@ -240,7 +235,10 @@ shortTitle: 搜索议题和 PR ## 搜索草稿拉取请求 您可以过滤草稿拉取请求。 更多信息请参阅“[关于拉取请求](/articles/about-pull-requests#draft-pull-requests)”。 -| 限定符 | 示例 | ------------- | -------------{% ifversion fpt or ghes or ghae or ghec %} | `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) 匹配拉取请求草稿。 | `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) 匹配可供审查的拉取请求。{% else %} | `is:draft` | [**is:draft**](https://github.com/search?q=is%3Adraft) 匹配拉取请求草稿。{% endif %} +| 限定符 | 示例 | +| ------------- | ------------------------------------------------------------------------- | +| `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) 匹配草稿拉取请求。 | +| `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) 匹配可供审核的拉取请求。 | ## 按拉取请求审查状态和审查者搜索 diff --git a/translations/zh-CN/content/site-policy/github-terms/github-community-guidelines.md b/translations/zh-CN/content/site-policy/github-terms/github-community-guidelines.md index 9ce8b94661..00da5e6685 100644 --- a/translations/zh-CN/content/site-policy/github-terms/github-community-guidelines.md +++ b/translations/zh-CN/content/site-policy/github-terms/github-community-guidelines.md @@ -39,7 +39,7 @@ GitHub 社区的主要目的是协作处理软件项目。 我们致力于维持 * **传达期望** - 维护者可以设置社区特定的准则，以帮助用户了解如何与项目进行交互，例如，在存储库的自述文件中、[参与文件](/articles/setting-guidelines-for-repository-contributors/)或[专用行为准则](/articles/adding-a-code-of-conduct-to-your-project/)中。 您可以在[此处](/communities)找到有关建设社区的更多信息。 -* **主持评论** - 对仓库拥有[写入权限](/articles/repository-permission-levels-for-an-organization/)的用户可以[编辑、删除或隐藏](/communities/moderating-comments-and-conversations/managing-disruptive-comments)任何人对提交、拉取请求和议题的评论。 对仓库具有读取权限的任何人都可查看评论的编辑历史记录。 评论作者和对存储库具有写入权限的人员还可以从[评论的编辑历史记录](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)中删除敏感信息。 如果有很多活动，主持项目可能会感觉像是一项艰巨的任务，但您可以[添加协作者](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account)，以帮助您管理社区。 +* **主持评论** - 对仓库拥有[写入权限](/articles/repository-permission-levels-for-an-organization/)的用户可以[编辑、删除或隐藏](/communities/moderating-comments-and-conversations/managing-disruptive-comments)任何人对提交、拉取请求和议题的评论。 对仓库具有读取权限的任何人都可查看评论的编辑历史记录。 评论作者和对存储库具有写入权限的人员还可以从[评论的编辑历史记录](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)中删除敏感信息。 如果有很多活动，主持项目可能会感觉像是一项艰巨的任务，但您可以[添加协作者](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account)，以帮助您管理社区。 * **锁定对话** - 如果议题、拉取请求或提交的讨论失控、偏离主题或者违反项目的行为准则或 GitHub 政策，则所有者、协作者和其他具有写入权限的任何人都可以临时或永久[锁定](/articles/locking-conversations/)对话。 diff --git a/translations/zh-CN/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md b/translations/zh-CN/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md index 8aacff59ae..2716a91784 100644 --- a/translations/zh-CN/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md +++ b/translations/zh-CN/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md @@ -16,8 +16,8 @@ GitHub Codespaces 的使用受 [GitHub 隐私声明](/github/site-policy/github- github.dev 上的活动受 [GitHub 测试预览版条款](/github/site-policy/github-terms-of-service#j-beta-previews)的约束 -## 使用 Visual Studio Code +## 使用 {% data variables.product.prodname_vscode %} -GitHub Codespaces 和 github.dev 允许在 Web 浏览器中使用 Visual Studio Code。 在 Web 浏览器中使用 Visual Studio Code 时，默认情况下会启用某些遥测集合，[Visual Studio Code 网站上对此进行了详细解释](https://code.visualstudio.com/docs/getstarted/telemetry)。 用户可以通过转到左上角菜单下的 File > Preferences > Settings（文件首选项设置）来选择退出遥测。 +GitHub Codespaces and github.dev allow for use of {% data variables.product.prodname_vscode %} in the web browser. When using {% data variables.product.prodname_vscode_shortname %} in the web browser, some telemetry collection is enabled by default and is [explained in detail on the {% data variables.product.prodname_vscode_shortname %} website](https://code.visualstudio.com/docs/getstarted/telemetry). 用户可以通过转到左上角菜单下的 File > Preferences > Settings（文件首选项设置）来选择退出遥测。 -如果用户选择在代码空间内选择退出 Visual Studio Code 中的遥测捕获（如前所述），这将在 GitHub Codespaces 和 github.dev 中的所有未来 Web 会话中同步禁用遥测首选项。 +If a user chooses to opt out of telemetry capture in {% data variables.product.prodname_vscode_shortname %} while inside of a codespace as outlined, this will sync the disable telemetry preference across all future web sessions in GitHub Codespaces and github.dev. diff --git a/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md b/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md index 6924fa91a9..dfee84791c 100644 --- a/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md +++ b/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md @@ -65,7 +65,7 @@ topics: #### 支付信息 如果您注册我们的付费帐户、通过 GitHub 赞助计划汇款或在 GitHub Marketplace 上购买应用程序，我们将收集您的全名、地址和信用卡信息或 PayPal 信息。 请注意，GitHub 不会处理或存储您的信用卡信息或 PayPal 信息，但我们的第三方付款处理商会这样做。 -如果您在 [GitHub Marketplace](https://github.com/marketplace) 上列出并销售应用程序，我们需要您的银行信息。 如果您通过 [GitHub 赞助计划](https://github.com/sponsors)筹集资金，我们需要您在注册过程中提供一些[其他信息](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-bank-information)，以便您参与这些服务并通过这些服务获取资金以及满足合规要求。 +如果您在 [GitHub Marketplace](https://github.com/marketplace) 上列出并销售应用程序，我们需要您的银行信息。 If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes. #### 个人资料信息 您可以选择在帐户个人资料中向我们提供更多信息，例如您的全名、头像等，可包括照片、简历、地理位置、公司和第三方网站的 URL。 此类信息可能包括用户个人信息。 请注意，您的个人资料信息可能对我们服务的其他用户显示。 diff --git a/translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md index 4918a84824..1e44b4bbff 100644 --- a/translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md +++ b/translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md @@ -19,7 +19,7 @@ topics: {% data reusables.sponsors.no-fees %} For more information, see "[About billing for {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)." -{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)." +{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[About {% data variables.product.prodname_sponsors %} for open source contributors](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)" and "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)." {% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md index 0fb3ae74fb..e80ef26e64 100644 --- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md +++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md @@ -16,7 +16,7 @@ shortTitle: Open source contributors ## Joining {% data variables.product.prodname_sponsors %} -{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)." +{% data reusables.sponsors.you-can-be-a-sponsored-developer %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)." {% data reusables.sponsors.you-can-be-a-sponsored-organization %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." @@ -28,7 +28,7 @@ You can set a goal for your sponsorships. For more information, see "[Managing y ## Sponsorship tiers -{% data reusables.sponsors.tier-details %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)," "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization), and "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)." +{% data reusables.sponsors.tier-details %} For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)," "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization), and "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)." It's best to set up a range of different sponsorship options, including monthly and one-time tiers, to make it easy for anyone to support your work. In particular, one-time payments allow people to reward your efforts without worrying about whether their finances will support a regular payment schedule. diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md index 93282ec21b..b35f4f6765 100644 --- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md +++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md @@ -11,7 +11,7 @@ versions: ghec: '*' children: - /about-github-sponsors-for-open-source-contributors - - /setting-up-github-sponsors-for-your-user-account + - /setting-up-github-sponsors-for-your-personal-account - /setting-up-github-sponsors-for-your-organization - /editing-your-profile-details-for-github-sponsors - /managing-your-sponsorship-goal diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md index abdfe897f6..91483e1d14 100644 --- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -23,7 +23,7 @@ shortTitle: 为组织设置 收到邀请您的组织加入 {% data variables.product.prodname_sponsors %} 的邀请后，您可以完成以下步骤以成为被赞助的组织。 -要作为组织外部的个人贡献者加入 {% data variables.product.prodname_sponsors %}，请参阅“[为个人帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”。 +要作为组织外部的个人贡献者加入 {% data variables.product.prodname_sponsors %}，请参阅“[为个人帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)”。 {% data reusables.sponsors.navigate-to-github-sponsors %} {% data reusables.sponsors.view-eligible-accounts %} diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md similarity index 96% rename from translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md rename to translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md index 51bd1d836b..a7363a0331 100644 --- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md @@ -1,10 +1,11 @@ --- -title: 为您的用户帐户设置 GitHub Sponsors +title: Setting up GitHub Sponsors for your personal account intro: '要成为被赞助的开发者，请加入 {% data variables.product.prodname_sponsors %}、填写被赞助开发者个人资料、创建赞助等级、提交您的银行和税务信息并为您在 {% data variables.product.product_location %} 上的帐户启用双重身份验证。' redirect_from: - /articles/becoming-a-sponsored-developer - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account + - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account versions: fpt: '*' ghec: '*' diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md index e3433a14b1..113803cae8 100644 --- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md +++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md @@ -28,7 +28,7 @@ W-9 税表中的信息有助于 {% data variables.product.prodname_dotcom %} 使 W-8 BEN 和 W-8 BEN-E 税单有助于 {% data variables.product.prodname_dotcom %} 确定须扣缴金额的受益所有者。 -如果你是美国以外任何其他地区的纳税人， 必须提交 [W-8 BEN](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf) (个人) 或 [W-8 BEN-E](https://www.irs.gov/forms-pubs/about-form-w-8-ben-e) (公司) 表单才能发布您的 {% data variables.product.prodname_sponsors %} 个人资料。 更多信息请参阅“[为个人帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account#submitting-your-tax-information)”和“[为组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)”。 {% data variables.product.prodname_dotcom %} 将向您发送适当的表格，在到期时通知您，并给您合理的时间填写和发送表格。 +如果你是美国以外任何其他地区的纳税人， 必须提交 [W-8 BEN](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf) (个人) 或 [W-8 BEN-E](https://www.irs.gov/forms-pubs/about-form-w-8-ben-e) (公司) 表单才能发布您的 {% data variables.product.prodname_sponsors %} 个人资料。 For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-tax-information)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)." {% data variables.product.prodname_dotcom %} 将向您发送适当的表格，在到期时通知您，并给您合理的时间填写和发送表格。 如果您被分配了不正确的税单， [请联系 {% data variables.product.prodname_dotcom %} 客服](https://support.github.com/contact?form%5Bsubject%5D=GitHub%20Sponsors:%20tax%20form&tags=sponsors) 来为您的情况重新分配正确的税单。 diff --git a/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md index 0be8a855e2..096e87b9cd 100644 --- a/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md +++ b/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md @@ -43,7 +43,7 @@ shortTitle: 赞助贡献者 如果被赞助帐户撤销的等级，您将仍保留在该等级，直到您选择其他等级或取消订阅。 更多信息请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”。 -如果您要赞助的帐户在 {% data variables.product.prodname_sponsors %} 上还没有个人资料，您可以建议该帐户加入。 更多信息请参阅“[为个人帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account)”和“[为组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)”。 +如果您要赞助的帐户在 {% data variables.product.prodname_sponsors %} 上还没有个人资料，您可以建议该帐户加入。 更多信息请参阅“[为个人帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)”和“[为组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)”。 {% data reusables.sponsors.sponsorships-not-tax-deductible %} diff --git a/translations/zh-CN/data/features/integration-branch-protection-exceptions.yml b/translations/zh-CN/data/features/integration-branch-protection-exceptions.yml new file mode 100644 index 0000000000..3c6a729fb9 --- /dev/null +++ b/translations/zh-CN/data/features/integration-branch-protection-exceptions.yml @@ -0,0 +1,8 @@ +--- +#Reference: #6665 +#GitHub Apps are supported as actors in all types of exceptions to branch protections +versions: + fpt: '*' + ghec: '*' + ghes: '>= 3.6' + ghae: 'issue-6665' diff --git a/translations/zh-CN/data/features/math.yml b/translations/zh-CN/data/features/math.yml new file mode 100644 index 0000000000..b7b89eb201 --- /dev/null +++ b/translations/zh-CN/data/features/math.yml @@ -0,0 +1,8 @@ +--- +#Issues 6054 +#Math support using LaTeX syntax +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.6' + ghae: 'issue-6054' diff --git a/translations/zh-CN/data/features/security-managers.yml b/translations/zh-CN/data/features/security-managers.yml index 6e62d12897..77f12eb126 100644 --- a/translations/zh-CN/data/features/security-managers.yml +++ b/translations/zh-CN/data/features/security-managers.yml @@ -4,5 +4,5 @@ versions: fpt: '*' ghes: '>=3.3' - ghae: 'issue-4999' + ghae: '*' ghec: '*' diff --git a/translations/zh-CN/data/features/security-overview-feature-specific-alert-page.yml b/translations/zh-CN/data/features/security-overview-feature-specific-alert-page.yml new file mode 100644 index 0000000000..1aebf50245 --- /dev/null +++ b/translations/zh-CN/data/features/security-overview-feature-specific-alert-page.yml @@ -0,0 +1,8 @@ +--- +#Reference: #7028. +#Documentation for feature-specific page for security overview at enterprise-level. +versions: + fpt: '*' + ghec: '*' + ghes: '>3.5' + ghae: 'issue-7028' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/19.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/19.yml index 88e870d0c9..a5b796aa23 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/19.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/19.yml @@ -1,9 +1,8 @@ ---- date: '2021-11-09' sections: security_fixes: - A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870. - - 包已更新到最新的安全版本。 + - Packages have been updated to the latest security versions. bugs: - Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration. - Unicorn worker counts might have been set incorrectly in clustering mode. @@ -15,10 +14,10 @@ sections: - Hookshot Go sent distribution type metrics that Collectd could not handle, which caused a ballooning of parsing errors. - Public repositories displayed unexpected results from {% data variables.product.prodname_secret_scanning %} with a type of `Unknown Token`. 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 %} 可用性。 - - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。 + - 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. + - When a replica node is offline in a high availability configuration, {% data variables.product.product_name %} may still route {% data variables.product.prodname_pages %} requests to the offline node, reducing the availability of {% data variables.product.prodname_pages %} for users. + - 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-0/20.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/20.yml index 24a0bac6d1..93ce32a049 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/20.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/20.yml @@ -4,13 +4,13 @@ sections: security_fixes: - 包已更新到最新的安全版本。 bugs: - - Pre-receive hooks would fail due to undefined `PATH`. - - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' - - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. - - Some critical services may not have been available on backend nodes in GHES Cluster. + - 预接收挂钩会由于未定义的 `PATH` 而失败。 + - '如果实例之前已配置为副本运行 `ghe-repl-setup` 将返回错误：“cannot create directory /data/user/elasticsearch: File exists（无法创建目录/data/user/elasticsearch：文件存在）”。' + - 在大型群集环境中，身份验证后端在前端节点子集上可能不可用。 + - 某些关键服务可能在 GHES 群集中的后端节点上不可用。 changes: - - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. - - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. + - 现在，默认情况下，在创建具有 `ghe-cluster-suport-bundle` 的集群支持包时，`gzip` 压缩的附加外层处于关闭状态。这种外部压缩可以选择使用 `ghe-cluster-suport-bundle -c` 命令行选项来应用。 + - 我们在管理控制台中添加了额外的文本，以提醒用户移动应用程序收集数据来改善体验。 - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09] known_issues: - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-0/25.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-0/25.yml index c563f88795..5744c6ed3f 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-0/25.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-0/25.yml @@ -4,7 +4,7 @@ sections: security_fixes: - 包已更新到最新的安全版本。 known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/21.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/21.yml new file mode 100644 index 0000000000..b6e1956267 --- /dev/null +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/21.yml @@ -0,0 +1,24 @@ +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - Packages have been updated to the latest security versions. + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not supported. + - Support bundles now include the row count of tables stored in MySQL. + 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 %} instance 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 {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} 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/zh-CN/data/release-notes/enterprise-server/3-2/10.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/10.yml index d56cb0b1cb..b3fb1c5f24 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/10.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/10.yml @@ -7,7 +7,7 @@ sections: - Upgrades could sometimes fail if a high-availability replica's clock was out of sync with the primary. - 'OAuth Applications created after September 1st, 2020 were not able to use the [Check an Authorization](https://docs.github.com/en/enterprise-server@3.2/rest/reference/apps#check-an-authorization) API endpoint.' known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml index 3d01f6405c..bb92336a91 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml @@ -35,7 +35,7 @@ sections: - The “Triage” and “Maintain” team roles are preserved during repository migrations. - Performance has been improved for web requests made by enterprise owners. known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/12.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/12.yml index 30a305d231..227905027b 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/12.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/12.yml @@ -15,7 +15,7 @@ sections: - The {% data variables.product.prodname_codeql %} starter workflow no longer errors even if the default token permissions for {% data variables.product.prodname_actions %} are not used. - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions. known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/13.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/13.yml new file mode 100644 index 0000000000..85332bd370 --- /dev/null +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/13.yml @@ -0,0 +1,27 @@ +--- +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - 包已更新到最新的安全版本。 + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - Videos uploaded to issue comments would not be rendered properly. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. + - Support bundles now include the row count of tables stored in MySQL. + - Dependency Graph can now be enabled without vulnerability data, allowing you to see what dependencies are in use and at what versions. Enabling Dependency Graph without enabling {% data variables.product.prodname_github_connect %} will **not** provide vulnerability information. + known_issues: + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 + - 自定义防火墙规则在升级过程中被删除。 + - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 + - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 + - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。' + - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml index 3d82006740..5c1b3f7a32 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml @@ -1,9 +1,8 @@ ---- date: '2021-11-09' sections: security_fixes: - A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870. - - 包已更新到最新的安全版本。 + - Packages have been updated to the latest security versions. bugs: - Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration. - Unicorn worker counts might have been set incorrectly in clustering mode. @@ -12,7 +11,7 @@ sections: - Upgrading from {% data variables.product.prodname_ghe_server %} 2.x to 3.x failed when there were UTF8 characters in an LDAP configuration. - Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations. - The documentation link for Server Statistics was broken. - - 'When a new tag was created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload did not display a correct `head_commit` object. Now, when a new tag is created, the push webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload''s `after` commit.' + - When a new tag was created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload did not display a correct `head_commit` object. Now, when a new tag is created, the push webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload's `after` commit. - The enterprise audit log page would not display audit events for {% data variables.product.prodname_secret_scanning %}. - There was an insufficient job timeout for replica repairs. - A repository's releases page would return a 500 error when viewing releases. @@ -22,10 +21,10 @@ sections: changes: - Kafka configuration improvements have been added. When deleting repositories, package files are now immediately deleted from storage account to free up space. `DestroyDeletedPackageVersionsJob` now deletes package files from storage account for stale packages along with metadata records. 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 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。' - - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。 + - 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. + - 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. + - 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/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/4.yml index a0fb2d5239..ff07cef22b 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/4.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/4.yml @@ -5,20 +5,20 @@ sections: security_fixes: - 包已更新到最新的安全版本。 bugs: - - Running `ghe-repl-start` or `ghe-repl-status` would sometimes return errors connecting to the database when GitHub Actions was enabled. - - Pre-receive hooks would fail due to undefined `PATH`. - - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' - - 'Running `ghe-support-bundle` returned an error: `integer expression expected`.' - - 'After setting up a high availability replica, `ghe-repl-status` included an error in the output: `unexpected unclosed action in command`.' - - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. - - Some critical services may not have been available on backend nodes in GHES Cluster. - - The repository permissions to the user returned by the `/repos` API would not return the full list. - - The `childTeams` connection on the `Team` object in the GraphQL schema produced incorrect results under some circumstances. - - In a high availability configuration, repository maintenance always showed up as failed in stafftools, even when it succeeded. - - User defined patterns would not detect secrets in files like `package.json` or `yarn.lock`. + - 在启用 GitHub Actions 时，运行 `ghe-repl-start` 或 `ghe-repl-status` 有时会返回连接到数据库的错误。 + - 预接收挂钩会由于未定义的 `PATH` 而失败。 + - '如果实例之前已配置为副本运行 `ghe-repl-setup` 将返回错误：“cannot create directory /data/user/elasticsearch: File exists（无法创建目录/data/user/elasticsearch：文件存在）”。' + - '运行 `ghe-support-bundle` 返回错误：“integer expression expected（预期为整数表达式）”。' + - '设置高可用性副本后，`ghe-repl-status` 在输出中包含错误：“unexpected unclosed action in command（命令中意外的未关闭操作）”。' + - 在大型群集环境中，身份验证后端在前端节点子集上可能不可用。 + - 某些关键服务可能在 GHES 群集中的后端节点上不可用。 + - '`/repos` API 返回的用户的存储库权限不会返回完整列表。' + - 在某些情况下，GraphQL 模式中 `Team` 对象上的 `childTeams` 连接产生不正确的结果。 + - 在高可用性配置中，存储库维护在 stafftools 中始终显示为失败，即使它成功了也是如此。 + - 用户定义的模式不会检测 `package.json` 或 `yarn.lock`等文件中的机密。 changes: - - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. - - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. + - 现在，默认情况下，在创建具有 `ghe-cluster-suport-bundle` 的集群支持包时，`gzip` 压缩的附加外层处于关闭状态。这种外部压缩可以选择使用 `ghe-cluster-suport-bundle -c` 命令行选项来应用。 + - 我们在管理控制台中添加了额外的文本，以提醒用户移动应用程序收集数据来改善体验。 - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09] known_issues: - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 上，攻击者可以创建第一个管理员用户。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/9.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/9.yml index 0db4e78e56..e75e728993 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-2/9.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/9.yml @@ -11,7 +11,7 @@ sections: changes: - Secret scanning will skip scanning ZIP and other archive files for secrets. known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml index dd43b99fc8..eaa5046942 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml @@ -1,4 +1,3 @@ ---- date: '2021-11-09' release_candidate: true deprecated: true @@ -12,9 +11,9 @@ intro: | For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." sections: features: - - - heading: Security Manager role + - heading: Security Manager role notes: + # https://github.com/github/releases/issues/1610 - | Organization owners can now grant teams the access to manage security alerts and settings on their repositories. The "security manager" role can be applied to any team and grants the team's members the following access: @@ -25,9 +24,10 @@ sections: - Write access on security settings at the repository level. For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." - - - heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling' + + - heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling' notes: + # https://github.com/github/releases/issues/1378 - | {% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. @@ -36,47 +36,71 @@ sections: You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)." - - - heading: 'Dark high contrast theme' + + - heading: 'Dark high contrast theme' notes: + # https://github.com/github/releases/issues/1539 - | A dark high contrast theme, with greater contrast between foreground and background elements, is now available on {% data variables.product.prodname_ghe_server %} 3.3. This release also includes improvements to the color system across all {% data variables.product.company_short %} themes. ![Animated image of switching between dark default theme and dark high contrast on the appearance settings page](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif) For more information about changing your theme, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + changes: - - - heading: 管理更改 + - heading: Administration Changes notes: + # https://github.com/github/releases/issues/1666 - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the maintenance of repositories, especially for repositories that contain many unreachable objects. Note that the first maintenance cycle after upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may take longer than usual to complete.' + + # https://github.com/github/releases/issues/1533 - '{% data variables.product.prodname_ghe_server %} 3.3 includes the public beta of a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."' + + # https://github.com/github/releases/issues/1616 - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the user impersonation process. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise administrator. For more information, see "[Impersonating a user](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."' + + # https://github.com/github/releases/issues/1609 - A new stream processing service has been added to facilitate the growing set of events that are published to the audit log, including events associated with Git and {% data variables.product.prodname_actions %} activity. - - - heading: 令牌更改 + + - heading: Token Changes notes: + # https://github.com/github/releases/issues/1390 - | An expiration date can now be set for new and existing personal access tokens. Setting an expiration date on personal access tokens is highly recommended to prevent older tokens from leaking and compromising security. Token owners will receive an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving users a duplicate token with the same properties as the original. When using a personal access token with the {% data variables.product.company_short %} API, a new `GitHub-Authentication-Token-Expiration` header is included in the response, which indicates the token's expiration date. For more information, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - - - heading: 'Notifications changes' + + - heading: 'Notifications changes' notes: + # https://github.com/github/releases/issues/1625 - 'Notification emails from discussions now include `(Discussion #xx)` in the subject, so you can recognize and filter emails that reference discussions.' - - - heading: '存储库更改' + + - heading: 'Repositories changes' notes: + # https://github.com/github/releases/issues/1735 - Public repositories now have a `Public` label next to their names like private and internal repositories. This change makes it easier to identify public repositories and avoid accidentally committing private code. + + # https://github.com/github/releases/issues/1733 - If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list. + + # https://github.com/github/releases/issues/1673 - When viewing a branch that has a corresponding open pull request, {% data variables.product.prodname_ghe_server %} now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request. + + # https://github.com/github/releases/issues/1670 - You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click {% octicon "copy" aria-label="The copy icon" %} in the toolbar. Note that this feature is currently only available in some browsers. + + # https://github.com/github/releases/issues/1571 - When creating a new release, you can now select or create the tag using a dropdown selector, rather than specifying the tag in a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)." + + # https://github.com/github/releases/issues/1752 - A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/). + + # https://github.com/github/releases/issues/1416 - You can now use `CITATION.cff` files to let others know how you would like them to cite your work. `CITATION.cff` files are plain text files with human- and machine-readable citation information. {% data variables.product.prodname_ghe_server %} parses this information into common citation formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX). For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." - - - heading: 'Markdown 更改' + + - heading: 'Markdown changes' notes: + # https://github.com/github/releases/issues/1645 - | You can use new keyboard shortcuts for quotes and lists in Markdown files, issues, pull requests, and comments. @@ -85,15 +109,28 @@ sections: * To add an unordered list, use cmd shift 8 on Mac, or ctrl shift 8 on Windows and Linux. See "[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)" for a full list of available shortcuts. - - 'You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)."' + + # https://github.com/github/releases/issues/1684 + - You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)." + + # https://github.com/github/releases/issues/1647 - When viewing Markdown files, you can now click {% octicon "code" aria-label="The code icon" %} in the toolbar to view the source of a Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file. + + # https://github.com/github/releases/issues/1600 - You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + + # https://github.com/github/releases/issues/1523 - '{% data variables.product.prodname_ghe_server %} now automatically generates a table of contents for Wikis, based on headings.' + + # https://github.com/github/releases/issues/1626 - When dragging and dropping files into a Markdown editor, such as images and videos, {% data variables.product.prodname_ghe_server %} now uses the mouse pointer location instead of the cursor location when placing the file. - - - heading: '议题和拉取请求更改' + + - heading: 'Issues and pull requests changes' notes: - - 'You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)."' + # https://github.com/github/releases/issues/1504 + - You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)." + + # https://github.com/github/releases/issues/1685 - | Improvements have been made to help teams manage code review assignments. You can now: @@ -105,12 +142,18 @@ sections: For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/). - You can now filter pull request searches to only include pull requests you are directly requested to review. + # https://github.com/github/releases/issues/1683 - Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)." - - - heading: 'GitHub Actions 更改' + + - heading: 'GitHub Actions changes' notes: + # https://github.com/github/releases/issues/1593 - You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)." - - 'Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise''s self-hosted runners.' + + # https://github.com/github/releases/issues/1694 + - Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise's self-hosted runners. + + # https://github.com/github/releases/issues/1157 - | The audit log now includes additional events for {% data variables.product.prodname_actions %}. Audit log entries are now recorded for the following events: @@ -121,75 +164,112 @@ sections: * A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#auditing-github-actions-events)." + + # https://github.com/github/releases/issues/1588 - Performance improvements have been made to {% data variables.product.prodname_actions %}, which may result in higher maximum job concurrency. - - - heading: 'GitHub Packages 更改' + + - heading: 'GitHub Packages changes' notes: + # https://github.com/github/docs-content/issues/5554 - When a repository is deleted, any associated package files are now immediately deleted from your {% data variables.product.prodname_registry %} external storage. - - - heading: 'Dependabot 和依赖关系图更改' + + - heading: 'Dependabot and Dependency graph changes' notes: + # https://github.com/github/releases/issues/1141 - Dependency review is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." + + # https://github.com/github/releases/issues/1630 - '{% data variables.product.prodname_dependabot %} is now available as a private beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} to be enabled. To learn more and sign up for the beta, contact the GitHub Sales team.' - - - heading: '代码扫描和秘密扫描更改' + + - heading: 'Code scanning and secret scanning changes' notes: + # https://github.com/github/releases/issues/1724 - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models. [JavaScript](https://github.com/github/codeql/tree/main/javascript) analysis now supports most common templating languages, and [Java](https://github.com/github/codeql/tree/main/java) now covers more than three times the endpoints of previous {% data variables.product.prodname_codeql %} versions. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts. + + # https://github.com/github/releases/issues/1639 - '{% data variables.product.prodname_codeql %} now supports scanning standard language features in Java 16, such as records and pattern matching. {% data variables.product.prodname_codeql %} is able to analyze code written in Java version 7 through 16. For more information about supported languages and frameworks, see the [{% data variables.product.prodname_codeql %} documentation](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).' + + # https://github.com/github/releases/issues/1655 - | Improvements have been made to the {% data variables.product.prodname_code_scanning %} `on:push` trigger when code is pushed to a pull request. If an `on:push` scan returns results that are associated with a pull request, {% data variables.product.prodname_code_scanning %} will now show these alerts on the pull request. Some other CI/CD systems can be exclusively configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, {% data variables.product.prodname_code_scanning %} will also try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-27-showing-code-scanning-alerts-on-pull-requests/). + + # https://github.com/github/releases/issues/1546 - You can now use the new pull request filter on the {% data variables.product.prodname_code_scanning %} alerts page to find all the {% data variables.product.prodname_code_scanning %} alerts associated with a pull request. A new "View all branch alerts" link on the pull request "Checks" tab allows you to directly view {% data variables.product.prodname_code_scanning %} alerts with the specific pull request filter already applied. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-08-23-pull-request-filter-for-code-scanning-alerts/). + + # https://github.com/github/releases/issues/1562 - User defined patterns for {% data variables.product.prodname_secret_scanning %} is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Also new in this release is the ability to edit custom patterns defined at the repository, organization, and enterprise levels. After editing and saving a pattern, {% data variables.product.prodname_secret_scanning %} searches for matches both in a repository's entire Git history and in any new commits. Editing a pattern will close alerts previously associated with the pattern if they no longer match the updated version. Other improvements, such as dry-runs, are planned in future releases. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." - - - heading: API and webhook changes + + - heading: API and webhook changes notes: + # https://github.com/github/releases/issues/1744 - Most REST API previews have graduated and are now an official part of the API. Preview headers are no longer required for most REST API endpoints, but will still function as expected if you specify a graduated preview in the `Accept` header of a request. For previews that still require specifying the preview in the `Accept` header of a request, see "[API previews](/rest/overview/api-previews)." - - 'You can now use the REST API to configure custom autolinks to external resources. The REST API now provides beta `GET`/`POST`/`DELETE` endpoints which you can use to view, add, or delete custom autolinks associated with a repository. For more information, see "[Autolinks](/rest/reference/repos#autolinks)."' - - 'You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Branches](/rest/reference/branches#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation.' - - 'Enterprise administrators on GitHub Enterprise Server can now use the REST API to enable or disable Git LFS for a repository. For more information, see "[Repositories](/rest/reference/repos#git-lfs)."' - - 'You can now use the REST API to query the audit log for an enterprise. While audit log forwarding provides the ability to retain and analyze data with your own toolkit and determine patterns over time, the new endpoint can help you perform limited analysis on recent events. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the REST API documentation.' + + # https://github.com/github/releases/issues/1513 + - You can now use the REST API to configure custom autolinks to external resources. The REST API now provides beta `GET`/`POST`/`DELETE` endpoints which you can use to view, add, or delete custom autolinks associated with a repository. For more information, see "[Autolinks](/rest/reference/repos#autolinks)." + + # https://github.com/github/releases/issues/1578 + - You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Branches](/rest/reference/branches#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation. + + # https://github.com/github/releases/issues/1527 + - Enterprise administrators on GitHub Enterprise Server can now use the REST API to enable or disable Git LFS for a repository. For more information, see "[Repositories](/rest/reference/repos#git-lfs)." + + # https://github.com/github/releases/issues/1476 + - You can now use the REST API to query the audit log for an enterprise. While audit log forwarding provides the ability to retain and analyze data with your own toolkit and determine patterns over time, the new endpoint can help you perform limited analysis on recent events. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the REST API documentation. + + # https://github.com/github/releases/issues/1485 - GitHub App user-to-server API requests can now read public resources using the REST API. This includes, for example, the ability to list a public repository's issues and pull requests, and to access a public repository's comments and content. - - 'When creating or updating a repository, you can now configure whether forking is allowed using the REST and GraphQL APIs. Previously, APIs for creating and updating repositories didn''t include the fields `allow_forking` (REST) or `forkingAllowed` (GraphQL). For more information, see "[Repositories](/rest/reference/repos)" in the REST API documentation and "[Repositories](/graphql/reference/objects#repository)" in the GraphQL API documentation.' + + # https://github.com/github/releases/issues/1734 + - When creating or updating a repository, you can now configure whether forking is allowed using the REST and GraphQL APIs. Previously, APIs for creating and updating repositories didn't include the fields `allow_forking` (REST) or `forkingAllowed` (GraphQL). For more information, see "[Repositories](/rest/reference/repos)" in the REST API documentation and "[Repositories](/graphql/reference/objects#repository)" in the GraphQL API documentation. + + # https://github.com/github/releases/issues/1637 - | A new GraphQL mutation [`createCommitOnBranch`](/graphql/reference/mutations#createcommitonbranch) makes it easier to add, update, and delete files in a branch of a repository. Compared to the REST API, you do not need to manually create blobs and trees before creating the commit. This allows you to add, update, or delete multiple files in a single API call. Commits authored using the new API are automatically GPG signed and are [marked as verified](/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification) in the {% data variables.product.prodname_ghe_server %} UI. GitHub Apps can use the mutation to author commits directly or [on behalf of users](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests). - - 'When a new tag is created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload''s `after` commit.' - - - heading: 'Performance Changes' + + # https://github.com/github/releases/issues/1665 + - When a new tag is created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload's `after` commit. + + - heading: 'Performance Changes' notes: + # https://github.com/github/releases/issues/1823 - Page loads and jobs are now significantly faster for repositories with many Git refs. - #No security/bug fixes for the RC release - #security_fixes: - #- PLACEHOLDER - #bugs: - #- PLACEHOLDER + + # No security/bug fixes for the RC release + # security_fixes: + # - PLACEHOLDER + + # bugs: + # - PLACEHOLDER + known_issues: - 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 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。' - - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。 + - 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. + - 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. + - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + deprecations: - - - heading: 弃用 GitHub Enterprise Server 2.22 + - heading: Deprecation of GitHub Enterprise Server 2.22 notes: - '**{% data variables.product.prodname_ghe_server %} 2.22 was discontinued on September 23, 2021**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - - heading: Deprecation of GitHub Enterprise Server 3.0 + - heading: Deprecation of GitHub Enterprise Server 3.0 notes: - '**{% data variables.product.prodname_ghe_server %} 3.0 will be discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - - heading: XenServer Hypervisor 支持终止 + + - heading: Deprecation of XenServer Hypervisor support notes: + # https://github.com/github/docs-content/issues/4439 - Starting with {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer is deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns. - - - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters + + - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters notes: + # https://github.com/github/releases/issues/1316 - | To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API authentication using query parameters. View the following posts to see the proposed replacements: @@ -197,13 +277,15 @@ sections: * [Replacement authentication using headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) These endpoints and authentication route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. - - - heading: Deprecation of the CodeQL runner + + - heading: Deprecation of the CodeQL runner notes: + # https://github.com/github/releases/issues/1632 - The {% data variables.product.prodname_codeql %} runner is being deprecated. {% data variables.product.prodname_ghe_server %} 3.3 will be the final release series that supports the {% data variables.product.prodname_codeql %} runner. Starting with {% data variables.product.prodname_ghe_server %} 3.4, the {% data variables.product.prodname_codeql %} runner will be removed and no longer supported. The {% data variables.product.prodname_codeql %} CLI version 2.6.2 or greater is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). - - - heading: Deprecation of custom bit-cache extensions + + - heading: Deprecation of custom bit-cache extensions notes: + # https://github.com/github/releases/issues/1415 - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3. @@ -212,5 +294,6 @@ sections: Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. To start a repository maintenance task manually, browse to `https:///stafftools/repositories///network` for each affected repository and click the **Schedule** button. + backups: - '{% data variables.product.prodname_ghe_server %} 3.3 requires at least [GitHub Enterprise Backup Utilities 3.3.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml index f816ec2c95..1ca3d1f503 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml @@ -1,11 +1,10 @@ ---- date: '2021-12-07' intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."

**Note:** We are aware of an issue where {% data variables.product.prodname_actions %} may fail to start automatically following the upgrade to {% data variables.product.prodname_ghe_server %} 3.3. To resolve, connect to the appliance via SSH and run the `ghe-actions-start` command. sections: features: - - - heading: Security Manager role + - heading: Security Manager role notes: + # https://github.com/github/releases/issues/1610 - | Organization owners can now grant teams the access to manage security alerts and settings on their repositories. The "security manager" role can be applied to any team and grants the team's members the following access: @@ -16,9 +15,10 @@ sections: - Write access on security settings at the repository level. For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." - - - heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling' + + - heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling' notes: + # https://github.com/github/releases/issues/1378 - | {% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. @@ -27,48 +27,74 @@ sections: You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)." - - - heading: 'Dark high contrast theme' + + - heading: 'Dark high contrast theme' notes: + # https://github.com/github/releases/issues/1539 - | A dark high contrast theme, with greater contrast between foreground and background elements, is now available on {% data variables.product.prodname_ghe_server %} 3.3. This release also includes improvements to the color system across all {% data variables.product.company_short %} themes. ![Animated image of switching between dark default theme and dark high contrast on the appearance settings page](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif) For more information about changing your theme, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + changes: - - - heading: 管理更改 + - heading: Administration Changes notes: + # https://github.com/github/releases/issues/1666 - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the maintenance of repositories, especially for repositories that contain many unreachable objects. Note that the first maintenance cycle after upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may take longer than usual to complete.' + + # https://github.com/github/releases/issues/1533 - '{% data variables.product.prodname_ghe_server %} 3.3 includes the public beta of a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."' + + # https://github.com/github/releases/issues/1616 - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the user impersonation process. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise administrator. For more information, see "[Impersonating a user](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."' + + # https://github.com/github/releases/issues/1609 - A new stream processing service has been added to facilitate the growing set of events that are published to the audit log, including events associated with Git and {% data variables.product.prodname_actions %} activity. + + # https://github.com/github/docs-content/issues/5801 - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09] - - - heading: 令牌更改 + + - heading: Token Changes notes: + # https://github.com/github/releases/issues/1390 - | An expiration date can now be set for new and existing personal access tokens. Setting an expiration date on personal access tokens is highly recommended to prevent older tokens from leaking and compromising security. Token owners will receive an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving users a duplicate token with the same properties as the original. When using a personal access token with the {% data variables.product.company_short %} API, a new `GitHub-Authentication-Token-Expiration` header is included in the response, which indicates the token's expiration date. For more information, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)." - - - heading: 'Notifications changes' + + - heading: 'Notifications changes' notes: + # https://github.com/github/releases/issues/1625 - 'Notification emails from discussions now include `(Discussion #xx)` in the subject, so you can recognize and filter emails that reference discussions.' - - - heading: '存储库更改' + + - heading: 'Repositories changes' notes: + # https://github.com/github/releases/issues/1735 - Public repositories now have a `Public` label next to their names like private and internal repositories. This change makes it easier to identify public repositories and avoid accidentally committing private code. + + # https://github.com/github/releases/issues/1733 - If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list. + + # https://github.com/github/releases/issues/1673 - When viewing a branch that has a corresponding open pull request, {% data variables.product.prodname_ghe_server %} now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request. + + # https://github.com/github/releases/issues/1670 - You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click {% octicon "copy" aria-label="The copy icon" %} in the toolbar. Note that this feature is currently only available in some browsers. + + # https://github.com/github/releases/issues/1571 - When creating a new release, you can now select or create the tag using a dropdown selector, rather than specifying the tag in a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)." + + # https://github.com/github/releases/issues/1752 - A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/). + + # https://github.com/github/releases/issues/1416 - You can now use `CITATION.cff` files to let others know how you would like them to cite your work. `CITATION.cff` files are plain text files with human- and machine-readable citation information. {% data variables.product.prodname_ghe_server %} parses this information into common citation formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX). For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." - - - heading: 'Markdown 更改' + + - heading: 'Markdown changes' notes: + # https://github.com/github/releases/issues/1645 - | You can use new keyboard shortcuts for quotes and lists in Markdown files, issues, pull requests, and comments. @@ -77,15 +103,28 @@ sections: * To add an unordered list, use cmd shift 8 on Mac, or ctrl shift 8 on Windows and Linux. See "[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)" for a full list of available shortcuts. - - 'You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)."' + + # https://github.com/github/releases/issues/1684 + - You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)." + + # https://github.com/github/releases/issues/1647 - When viewing Markdown files, you can now click {% octicon "code" aria-label="The code icon" %} in the toolbar to view the source of a Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file. + + # https://github.com/github/releases/issues/1600 - You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + + # https://github.com/github/releases/issues/1523 - '{% data variables.product.prodname_ghe_server %} now automatically generates a table of contents for Wikis, based on headings.' + + # https://github.com/github/releases/issues/1626 - When dragging and dropping files into a Markdown editor, such as images and videos, {% data variables.product.prodname_ghe_server %} now uses the mouse pointer location instead of the cursor location when placing the file. - - - heading: '议题和拉取请求更改' + + - heading: 'Issues and pull requests changes' notes: - - 'You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)."' + # https://github.com/github/releases/issues/1504 + - You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)." + + # https://github.com/github/releases/issues/1685 - | Improvements have been made to help teams manage code review assignments. You can now: @@ -97,12 +136,18 @@ sections: For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/). - You can now filter pull request searches to only include pull requests you are directly requested to review. + # https://github.com/github/releases/issues/1683 - Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)." - - - heading: 'GitHub Actions 更改' + + - heading: 'GitHub Actions changes' notes: + # https://github.com/github/releases/issues/1593 - You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)." - - 'Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise''s self-hosted runners.' + + # https://github.com/github/releases/issues/1694 + - Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise's self-hosted runners. + + # https://github.com/github/releases/issues/1157 - | The audit log now includes additional events for {% data variables.product.prodname_actions %}. Audit log entries are now recorded for the following events: @@ -113,79 +158,118 @@ sections: * A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#auditing-github-actions-events)." + + # https://github.com/github/releases/issues/1588 - '{% data variables.product.prodname_ghe_server %} 3.3 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information about the new performance targets for a range of CPU and memory configurations, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."' + + # https://github.com/github/releases/issues/1556 - To mitigate insider man in the middle attacks when using actions resolved through {% data variables.product.prodname_github_connect %} to {% data variables.product.prodname_dotcom_the_website %} from {% data variables.product.prodname_ghe_server %}, the actions namespace (`owner/name`) is retired on use. Retiring the namespace prevents that namespace from being created on your {% data variables.product.prodname_ghe_server %} instance, and ensures all workflows referencing the action will download it from {% data variables.product.prodname_dotcom_the_website %}. - - - heading: 'GitHub Packages 更改' + + - heading: 'GitHub Packages changes' notes: + # https://github.com/github/docs-content/issues/5554 - When a repository is deleted, any associated package files are now immediately deleted from your {% data variables.product.prodname_registry %} external storage. - - - heading: 'Dependabot 和依赖关系图更改' + + - heading: 'Dependabot and Dependency graph changes' notes: + # https://github.com/github/releases/issues/1141 - Dependency review is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." + + # https://github.com/github/releases/issues/1630 - '{% data variables.product.prodname_dependabot %} is now available as a private beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} to be enabled. To learn more and sign up for the beta, contact the GitHub Sales team.' - - - heading: '代码扫描和秘密扫描更改' + + - heading: 'Code scanning and secret scanning changes' notes: + # https://github.com/github/releases/issues/1724 - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models. [JavaScript](https://github.com/github/codeql/tree/main/javascript) analysis now supports most common templating languages, and [Java](https://github.com/github/codeql/tree/main/java) now covers more than three times the endpoints of previous {% data variables.product.prodname_codeql %} versions. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts. + + # https://github.com/github/releases/issues/1639 - '{% data variables.product.prodname_codeql %} now supports scanning standard language features in Java 16, such as records and pattern matching. {% data variables.product.prodname_codeql %} is able to analyze code written in Java version 7 through 16. For more information about supported languages and frameworks, see the [{% data variables.product.prodname_codeql %} documentation](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).' + + # https://github.com/github/releases/issues/1655 - | Improvements have been made to the {% data variables.product.prodname_code_scanning %} `on:push` trigger when code is pushed to a pull request. If an `on:push` scan returns results that are associated with a pull request, {% data variables.product.prodname_code_scanning %} will now show these alerts on the pull request. Some other CI/CD systems can be exclusively configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, {% data variables.product.prodname_code_scanning %} will also try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-27-showing-code-scanning-alerts-on-pull-requests/). + + # https://github.com/github/releases/issues/1546 - You can now use the new pull request filter on the {% data variables.product.prodname_code_scanning %} alerts page to find all the {% data variables.product.prodname_code_scanning %} alerts associated with a pull request. A new "View all branch alerts" link on the pull request "Checks" tab allows you to directly view {% data variables.product.prodname_code_scanning %} alerts with the specific pull request filter already applied. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-08-23-pull-request-filter-for-code-scanning-alerts/). + + # https://github.com/github/releases/issues/1562 - User defined patterns for {% data variables.product.prodname_secret_scanning %} is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Also new in this release is the ability to edit custom patterns defined at the repository, organization, and enterprise levels. After editing and saving a pattern, {% data variables.product.prodname_secret_scanning %} searches for matches both in a repository's entire Git history and in any new commits. Editing a pattern will close alerts previously associated with the pattern if they no longer match the updated version. Other improvements, such as dry-runs, are planned in future releases. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." - - - heading: API and webhook changes + + - heading: API and webhook changes notes: + # https://github.com/github/releases/issues/1744 - Most REST API previews have graduated and are now an official part of the API. Preview headers are no longer required for most REST API endpoints, but will still function as expected if you specify a graduated preview in the `Accept` header of a request. For previews that still require specifying the preview in the `Accept` header of a request, see "[API previews](/rest/overview/api-previews)." - - 'You can now use the REST API to configure custom autolinks to external resources. The REST API now provides beta `GET`/`POST`/`DELETE` endpoints which you can use to view, add, or delete custom autolinks associated with a repository. For more information, see "[Autolinks](/rest/reference/repos#autolinks)."' - - 'You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Branches](/rest/reference/branches#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation.' - - 'Enterprise administrators on GitHub Enterprise Server can now use the REST API to enable or disable Git LFS for a repository. For more information, see "[Repositories](/rest/reference/repos#git-lfs)."' - - 'You can now use the REST API to query the audit log for an enterprise. While audit log forwarding provides the ability to retain and analyze data with your own toolkit and determine patterns over time, the new endpoint can help you perform limited analysis on recent events. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the REST API documentation.' + + # https://github.com/github/releases/issues/1513 + - You can now use the REST API to configure custom autolinks to external resources. The REST API now provides beta `GET`/`POST`/`DELETE` endpoints which you can use to view, add, or delete custom autolinks associated with a repository. For more information, see "[Autolinks](/rest/reference/repos#autolinks)." + + # https://github.com/github/releases/issues/1578 + - You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Branches](/rest/reference/branches#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation. + + # https://github.com/github/releases/issues/1527 + - Enterprise administrators on GitHub Enterprise Server can now use the REST API to enable or disable Git LFS for a repository. For more information, see "[Repositories](/rest/reference/repos#git-lfs)." + + # https://github.com/github/releases/issues/1476 + - You can now use the REST API to query the audit log for an enterprise. While audit log forwarding provides the ability to retain and analyze data with your own toolkit and determine patterns over time, the new endpoint can help you perform limited analysis on recent events. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the REST API documentation. + + # https://github.com/github/releases/issues/1485 - GitHub App user-to-server API requests can now read public resources using the REST API. This includes, for example, the ability to list a public repository's issues and pull requests, and to access a public repository's comments and content. - - 'When creating or updating a repository, you can now configure whether forking is allowed using the REST and GraphQL APIs. Previously, APIs for creating and updating repositories didn''t include the fields `allow_forking` (REST) or `forkingAllowed` (GraphQL). For more information, see "[Repositories](/rest/reference/repos)" in the REST API documentation and "[Repositories](/graphql/reference/objects#repository)" in the GraphQL API documentation.' + + # https://github.com/github/releases/issues/1734 + - When creating or updating a repository, you can now configure whether forking is allowed using the REST and GraphQL APIs. Previously, APIs for creating and updating repositories didn't include the fields `allow_forking` (REST) or `forkingAllowed` (GraphQL). For more information, see "[Repositories](/rest/reference/repos)" in the REST API documentation and "[Repositories](/graphql/reference/objects#repository)" in the GraphQL API documentation. + + # https://github.com/github/releases/issues/1637 - | A new GraphQL mutation [`createCommitOnBranch`](/graphql/reference/mutations#createcommitonbranch) makes it easier to add, update, and delete files in a branch of a repository. Compared to the REST API, you do not need to manually create blobs and trees before creating the commit. This allows you to add, update, or delete multiple files in a single API call. Commits authored using the new API are automatically GPG signed and are [marked as verified](/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification) in the {% data variables.product.prodname_ghe_server %} UI. GitHub Apps can use the mutation to author commits directly or [on behalf of users](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests). - - 'When a new tag is created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload''s `after` commit.' - - - heading: 'Performance Changes' + + # https://github.com/github/releases/issues/1665 + - When a new tag is created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload's `after` commit. + + - heading: 'Performance Changes' notes: + # https://github.com/github/releases/issues/1823 - Page loads and jobs are now significantly faster for repositories with many Git refs. - #No security/bug fixes for the RC release - #security_fixes: - #- PLACEHOLDER - #bugs: - #- PLACEHOLDER + + # No security/bug fixes for the RC release + # security_fixes: + # - PLACEHOLDER + + # bugs: + # - PLACEHOLDER + 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 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。' - - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。 + - 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. + - 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. + - 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.' - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' + deprecations: - - - heading: 弃用 GitHub Enterprise Server 2.22 + - heading: Deprecation of GitHub Enterprise Server 2.22 notes: - '**{% data variables.product.prodname_ghe_server %} 2.22 was discontinued on September 23, 2021**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - - heading: Deprecation of GitHub Enterprise Server 3.0 + - heading: Deprecation of GitHub Enterprise Server 3.0 notes: - '**{% data variables.product.prodname_ghe_server %} 3.0 will be discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - - - heading: XenServer Hypervisor 支持终止 + + - heading: Deprecation of XenServer Hypervisor support notes: + # https://github.com/github/docs-content/issues/4439 - Starting with {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer is deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns. - - - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters + + - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters notes: + # https://github.com/github/releases/issues/1316 - | To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API authentication using query parameters. View the following posts to see the proposed replacements: @@ -193,13 +277,15 @@ sections: * [Replacement authentication using headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make) These endpoints and authentication route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4. - - - heading: Deprecation of the CodeQL runner + + - heading: Deprecation of the CodeQL runner notes: + # https://github.com/github/releases/issues/1632 - The {% data variables.product.prodname_codeql %} runner is being deprecated. {% data variables.product.prodname_ghe_server %} 3.3 will be the final release series that supports the {% data variables.product.prodname_codeql %} runner. Starting with {% data variables.product.prodname_ghe_server %} 3.4, the {% data variables.product.prodname_codeql %} runner will be removed and no longer supported. The {% data variables.product.prodname_codeql %} CLI version 2.6.2 or greater is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). - - - heading: Deprecation of custom bit-cache extensions + + - heading: Deprecation of custom bit-cache extensions notes: + # https://github.com/github/releases/issues/1415 - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3. @@ -208,5 +294,6 @@ sections: Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. To start a repository maintenance task manually, browse to `https:///stafftools/repositories///network` for each affected repository and click the **Schedule** button. + backups: - '{% data variables.product.prodname_ghe_server %} 3.3 requires at least [GitHub Enterprise Backup Utilities 3.3.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).' 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 53db1d26df..8196aaccab 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 @@ -6,7 +6,7 @@ sections: - '**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. - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/2.yml index 5b4d360329..dd3a4d31e7 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/2.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/2.yml @@ -21,7 +21,7 @@ sections: - Several documentation links resulted in a 404 Not Found error. 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. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 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 index 46254f4419..27dd158e20 100644 --- 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 @@ -19,7 +19,7 @@ sections: - 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. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/4.yml index 236c75aceb..183c9c9120 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/4.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/4.yml @@ -14,7 +14,7 @@ sections: - Secret scanning will skip scanning ZIP and other archive files for secrets. 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. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/5.yml index 3d43c11824..6b29835d02 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/5.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/5.yml @@ -8,7 +8,7 @@ sections: - 'OAuth Applications created after September 1st, 2020 were not able to use the [Check an Authorization](https://docs.github.com/en/enterprise-server@3.3/rest/reference/apps#check-an-authorization) API endpoint.' 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. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/6.yml index 12e11d2847..c5054f2c68 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/6.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/6.yml @@ -39,7 +39,7 @@ sections: - Performance has been improved for web requests made by enterprise owners. 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. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/7.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/7.yml index da95356d96..7f1b2f5c23 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/7.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/7.yml @@ -21,7 +21,7 @@ sections: - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions. 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. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/8.yml new file mode 100644 index 0000000000..96950f12a4 --- /dev/null +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/8.yml @@ -0,0 +1,34 @@ +--- +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - 包已更新到最新的安全版本。 + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + - Videos uploaded to issue comments would not be rendered properly. + - When using the file finder on a repository page, typing the backspace key within the search field would result in search results being listed multiple times and cause rendering problems. + - When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events. + - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. + - Support bundles now include the row count of tables stored in MySQL. + - When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects. + - The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload. + 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. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 + - 自定义防火墙规则在升级过程中被删除。 + - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 + - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 + - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。' + - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。 + - '{% 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.' + - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml index f62d7467c6..6c586a5ba0 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml @@ -43,7 +43,7 @@ sections: - Users can now choose the number of spaces a tab is equal to, by setting their preferred tab size in the "Appearance" settings of their user account. All code with a tab indent will render using the preferred tab size. - The {% data variables.product.prodname_github_connect %} data connection record now includes a count of the number of active and dormant users and the configured dormancy period. - - heading: Performance Changes + heading: 性能更改 notes: - WireGuard, used to secure communication between {% data variables.product.prodname_ghe_server %} instances in a High Availability configuration, has been migrated to the Kernel implementation. - @@ -141,7 +141,7 @@ sections: #bugs: #- PLACEHOLDER known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 @@ -151,7 +151,7 @@ sections: - Actions services needs to be restarted after restoring appliance from backup taken on a different host. deprecations: - - heading: Deprecation of GitHub Enterprise Server 3.0 + heading: 弃用 GitHub Enterprise Server 3.0 notes: - '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - @@ -171,16 +171,16 @@ sections: notes: - 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-06-deprecation-notice-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.' - - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters + heading: OAuth 应用程序 API 端点的弃用和通过查询参数的 API 身份验证 notes: - | Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make). - - heading: Deprecation of the CodeQL runner + heading: 废弃 CodeQL 运行器 notes: - The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). - - heading: Deprecation of custom bit-cache extensions + heading: 废弃自定义位缓存扩展 notes: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml index b13d8dddbf..cde3bd02ac 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml @@ -42,7 +42,7 @@ sections: - The {% data variables.product.prodname_github_connect %} data connection record now includes a count of the number of active and dormant users and the configured dormancy period. - You can now give users access to enterprise-specific links by adding custom footers to {% data variables.product.prodname_ghe_server %}. For more information, see "[Configuring custom footers](/admin/configuration/configuring-your-enterprise/configuring-custom-footers)." - - heading: Performance Changes + heading: 性能更改 notes: - WireGuard, used to secure communication between {% data variables.product.prodname_ghe_server %} instances in a High Availability configuration, has been migrated to the Kernel implementation. - @@ -144,7 +144,7 @@ sections: #bugs: #- PLACEHOLDER known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 @@ -160,7 +160,7 @@ sections: - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL. deprecations: - - heading: Deprecation of GitHub Enterprise Server 3.0 + heading: 弃用 GitHub Enterprise Server 3.0 notes: - '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - @@ -180,16 +180,16 @@ sections: notes: - 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-06-deprecation-notice-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.' - - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters + heading: OAuth 应用程序 API 端点的弃用和通过查询参数的 API 身份验证 notes: - | Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make). - - heading: Deprecation of the CodeQL runner + heading: 废弃 CodeQL 运行器 notes: - The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). - - heading: Deprecation of custom bit-cache extensions + heading: 废弃自定义位缓存扩展 notes: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml index cc3cea8307..6cf210773e 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml @@ -40,7 +40,7 @@ sections: - Using ghe-migrator or exporting from GitHub.com, an export would not include Pull Request attachments. - Performance has been improved for web requests made by enterprise owners. known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 @@ -55,7 +55,7 @@ sections: - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL. deprecations: - - heading: Deprecation of GitHub Enterprise Server 3.0 + heading: 弃用 GitHub Enterprise Server 3.0 notes: - '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - @@ -75,16 +75,16 @@ sections: notes: - 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-06-deprecation-notice-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.' - - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters + heading: OAuth 应用程序 API 端点的弃用和通过查询参数的 API 身份验证 notes: - | Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make). - - heading: Deprecation of the CodeQL runner + heading: 废弃 CodeQL 运行器 notes: - The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). - - heading: Deprecation of custom bit-cache extensions + heading: 废弃自定义位缓存扩展 notes: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml index 7021324b1a..0eef2fdc0c 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml @@ -19,7 +19,7 @@ sections: - Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log. - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions. known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 @@ -34,7 +34,7 @@ sections: - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL. deprecations: - - heading: Deprecation of GitHub Enterprise Server 3.0 + heading: 弃用 GitHub Enterprise Server 3.0 notes: - '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' - @@ -54,16 +54,16 @@ sections: notes: - 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-06-deprecation-notice-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.' - - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters + heading: OAuth 应用程序 API 端点的弃用和通过查询参数的 API 身份验证 notes: - | Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make). - - heading: Deprecation of the CodeQL runner + heading: 废弃 CodeQL 运行器 notes: - The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). - - heading: Deprecation of custom bit-cache extensions + heading: 废弃自定义位缓存扩展 notes: - | Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. @@ -73,5 +73,10 @@ sections: Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. To start a repository maintenance task manually, browse to `https:///stafftools/repositories///network` for each affected repository and click the Schedule button. + - + heading: Theme picker for GitHub Pages has been removed + notes: + - | + The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)." backups: - '{% data variables.product.prodname_ghe_server %} 3.4 requires at least [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/3.yml new file mode 100644 index 0000000000..e70e23b617 --- /dev/null +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/3.yml @@ -0,0 +1,41 @@ +--- +date: '2022-05-17' +sections: + security_fixes: + - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).' + - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/). + - 包已更新到最新的安全版本。 + bugs: + - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`. + - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog. + - When adding custom patterns and providing non-UTF8 test strings, match highlighting was incorrect. + - LDAP users with an underscore character (`_`) in their user names can now login successfully. + - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out. + - After enabling SAML encrypted assertions with Azure as identity provider, the sign in page would fail with a `500` error. + - Character key shortcut preferences weren't respected. + - Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`. + - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified. + - Videos uploaded to issue comments would not be rendered properly. + - When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events. + - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests. + changes: + - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status. + - The Nomad allocation timeout for Dependency Graph has been increased to ensure post-upgrade migrations can complete. + - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported. + - Support bundles now include the row count of tables stored in MySQL. + - When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects. + - The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload. + known_issues: + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 + - 自定义防火墙规则在升级过程中被删除。 + - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 + - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 + - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。' + - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。 + - | + When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11] + + To work around this problem, you can take one of the two following actions. + - Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute. + - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL. diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml index aff612c647..fc62736af0 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -5,11 +5,11 @@ deprecated: false intro: | {% note %} - **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. + **注意：** 如果 {% data variables.product.product_location %} 正在运行候选发行版，则无法使用热补丁进行升级。我们建议仅在测试环境中运行候选版本。 {% endnote %} - For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." + 有关升级说明，请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)”。 sections: features: - @@ -333,8 +333,13 @@ sections: notes: - | The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, 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)." + - + heading: Theme picker for GitHub Pages has been removed + notes: + - | + The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)." known_issues: - - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - 在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。 - 自定义防火墙规则在升级过程中被删除。 - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。 - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。 diff --git a/translations/zh-CN/data/release-notes/github-ae/2021-06/2021-12-06.yml b/translations/zh-CN/data/release-notes/github-ae/2021-06/2021-12-06.yml index af5fa71e1e..f6c4263b39 100644 --- a/translations/zh-CN/data/release-notes/github-ae/2021-06/2021-12-06.yml +++ b/translations/zh-CN/data/release-notes/github-ae/2021-06/2021-12-06.yml @@ -2,7 +2,7 @@ date: '2021-12-06' friendlyDate: 'December 6, 2021' title: 'December 6, 2021' -currentWeek: true +currentWeek: false sections: features: - diff --git a/translations/zh-CN/data/release-notes/github-ae/2022-05/2022-05-17.yml b/translations/zh-CN/data/release-notes/github-ae/2022-05/2022-05-17.yml new file mode 100644 index 0000000000..a2bb879cb8 --- /dev/null +++ b/translations/zh-CN/data/release-notes/github-ae/2022-05/2022-05-17.yml @@ -0,0 +1,190 @@ +--- +date: '2022-05-17' +friendlyDate: 'May 17, 2022' +title: 'May 17, 2022' +currentWeek: true +sections: + features: + - + heading: 'GitHub Advanced Security features are generally available' + notes: + - | + Code scanning and secret scanning are now generally available for GitHub AE. For more information, see "[About code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)." + - | + Custom patterns for secret scanning is now generally available. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + - + heading: 'View all code scanning alerts for a pull request' + notes: + - | + You can now find all code scanning alerts associated with your pull request with the new pull request filter on the code scanning alerts page. The pull request checks page shows the alerts introduced in a pull request, but not existing alerts on the pull request branch. The new "View all branch alerts" link on the Checks page takes you to the code scanning alerts page with the specific pull request filter already applied, so you can see all the alerts associated with your pull request. This can be useful to manage lots of alerts, and to see more detailed information for individual alerts. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)." + - + heading: 'Security overview for organizations' + notes: + - | + GitHub Advanced Security now offers an organization-level view of the application security risks detected by code scanning, Dependabot, and secret scanning. The security overview shows the enablement status of security features on each repository, as well as the number of alerts detected. + + In addition, the security overview lists all secret scanning alerts at the organization level. Similar views for Dependabot and code scanning alerts are coming in future releases. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + + ![Screenshot of security overview](/assets/images/enterprise/3.2/release-notes/security-overview-UI.png) + - + heading: '依赖关系图' + notes: + - | + Dependency graph is now available on GitHub AE. The dependency graph helps you understand the open source software that you depend on by parsing the dependency manifests checked into repositories. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." + - + heading: 'Dependabot 警报' + notes: + - | + Dependabot alerts can now notify you of vulnerabilities in your dependencies on GitHub AE. You can enable Dependabot alerts by enabling the dependency graph, enabling GitHub Connect, and syncing vulnerabilities from the GitHub Advisory Database. This feature is in beta and subject to change. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)." + + After you enable Dependabot alerts, members of your organization will receive notifications any time a new vulnerability that affects their dependencies is added to the GitHub Advisory Database or a vulnerable dependency is added to their manifest. Members can customize notification settings. For more information, see "[Configuring notifications for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies)." + - + heading: 'Security manager role for organizations' + notes: + - | + Organizations can now grant teams permission to manage security alerts and settings on all their repositories. The "security manager" role can be applied to any team and grants the team's members the following permissions. + + - Read access on all repositories in the organization + - Write access on all security alerts in the organization + - Access to the organization-level security tab + - Write access on security settings at the organization level + - Write access on security settings at the repository level + + For more information, see "[Managing security managers in your organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." + - + heading: 'Ephemeral runners and autoscaling webhooks for GitHub Actions' + notes: + - | + GitHub AE now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier. + + Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, GitHub AE automatically unregisteres ephemeral runners, allowing you to perform any post-job management. + + You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to job requests from GitHub Actions. + + For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)." + - + heading: 'Composite actions for GitHub Actions' + notes: + - | + You can reduce duplication in your workflows by using composition to reference other actions. Previously, actions written in YAML could only use scripts. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)." + - + heading: 'New token scope for management of self-hosted runners' + notes: + - | + Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the `new manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to many REST API endpoints to manage your enterprise's self-hosted runners. + - + heading: 'Audit log accessible via REST API' + notes: + - | + You can now use the REST API to programmatically interface with the audit log. While audit log forwarding provides you with the ability to retain and analyze data with your own toolkit and determine patterns over time, the new REST API will help you perform limited analysis on events of note that have happened in recent history. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-rest-api)." + - + heading: 'Expiration dates for personal access tokens' + notes: + - | + You can now set an expiration date on new and existing personal access tokens. GitHub AE will send you an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving you a duplicate token with the same properties as the original. When using a token with the GitHub AE API, you'll see a new header, `GitHub-Authentication-Token-Expiration`, indicating the token's expiration date. You can use this in scripts, for example to log a warning message as the expiration date approaches. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" and "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#using-personal-access-tokens)." + - + heading: 'Export a list of people with access to a repository' + notes: + - | + Organization owners can now export a list of the people with access to a repository in CSV format. For more information, see "[Viewing people with access to your repository](/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository#exporting-a-list-of-people-with-access-to-your-repository)." + - + heading: 'Improved management of code review assignments' + notes: + - | + New settings to manage code review assignment code review assignment help distribute a team's pull request review across the team members so reviews aren't the responsibility of just one or two team members. + + - Child team members: Limit assignment to only direct members of the team. Previously, team review requests could be assigned to direct members of the team or members of child teams. + - Count existing requests: Continue with automatic assignment even if one or more members of the team are already requested. Previously, a team member who was already requested would be counted as one of the team's automatic review requests. + - Team review request: Keep a team assigned to review even if one or more members is newly assigned. + + For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)." + - + heading: 'New themes' + notes: + - | + Two new themes are available for the GitHub AE web UI. + + - A dark high contrast theme, with greater contrast between foreground and background elements + - Light and dark colorblind, which swap colors such as red and green for orange and blue + + For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + - + heading: 'Markdown improvements' + notes: + - | + You can now use footnote syntax in any Markdown field to reference relevant information without disrupting the flow of your prose. Footnotes are displayed as superscript links. Click a footnote to jump to the reference, displayed in a new section at the bottom of the document. 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#footnotes)." + - | + You can now toggle between the source view and rendered Markdown view through the web UI by clicking the {% octicon "code" aria-label="The Code icon" %} button to "Display the source diff" at the top of any Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file. + - | + You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](/github/writing-on-github/working-with-advanced-formatting/attaching-files)." + - | + GitHub AE now automatically generates a table of contents for Wikis, based on headings. + changes: + - + heading: '性能' + notes: + - | + 现在，对于具有许多 Git 引用的存储库，页面加载和作业的速度要快得多。 + - + heading: '管理' + notes: + - | + The user impersonation process is improved. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise owner. For more information, see "[Impersonating a user](/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)." + - + heading: 'GitHub Actions' + notes: + - | + To mitigate insider man-in-the-middle attacks when using actions resolved through GitHub Connect to GitHub.com from GitHub AE, GitHub AE retires the actions namespace (`OWNER/NAME`) on use. Retiring the namespace prevents that namespace from being created in your enterprise, and ensures all workflows referencing the action will download it from GitHub.com. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." + - | + The audit log now includes additional events for GitHub Actions. GitHub AE now records audit log entries for the following events. + + - A self-hosted runner is registered or removed. + - A self-hosted runner is added to a runner group, or removed from a runner group. + - A runner group is created or removed. + - A workflow run is created or completed. + - A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner. + + For more information, see "[Security hardening for GitHub Actions](/actions/security-guides/security-hardening-for-github-actions)." + - + heading: 'GitHub Advanced Security' + notes: + - | + Code scanning will now map alerts identified in `on:push` workflows to show up on pull requests, when possible. The alerts shown on the pull request are those identified by comparing the existing analysis of the head of the branch to the analysis for the target branch that you are merging against. Note that if the pull request's merge commit is not used, alerts can be less accurate when compared to the approach that uses `on:pull_request` triggers. For more information, see "[About code scanning with CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." + + Some other CI/CD systems can exclusively be configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, code scanning will try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see "[Uploading a SARIF file to GitHub](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)." + - | + GitHub AE now detects secrets from additional providers. For more information, see "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets)." + - + heading: '拉取请求' + notes: + - | + The timeline and Reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members because that team uses code review assignment. + + ![Screenshot of indicator for automatic assignment of code review](https://user-images.githubusercontent.com/2503052/134931920-409dea07-7a70-4557-b208-963357db7a0d.png) + - | + You can now filter pull request searches to only include pull requests you are directly requested to review by choosing **Awaiting review from you**. For more information, see "[Searching issues and pull requests](https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests)." + - | + 如果在使用分支选择器菜单时指定分支的确切名称，则结果现在将显示在匹配分支列表的顶部。以前，确切的分支名称匹配项可能会显示在列表的底部。 + - | + When viewing a branch that has a corresponding open pull request, GitHub AE now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request. + - | + You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click in the toolbar. Note that this feature is currently only available in some browsers. + - | + A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [GitHub Changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/). + - + heading: '仓库' + notes: + - | + GitHub AE now includes enhanced support for _CITATION.cff_ files. _CITATION.cff_ files are plain text files with human- and machine-readable citation information. GitHub AE parses this information into convenient formats such as [APA](​​https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX) that can be copied by others. For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)." + - | + You can now add, delete, or view autolinks through the Repositories API's Autolinks endpoint. For more information, see "[Autolinked references and URLs](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)" and "[Repositories](/rest/reference/repos#autolinks)" in the REST API documentation. + - + heading: '版本发布' + notes: + - | + The tag selection component for GitHub releases is now a drop-down menu rather than a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)." + - + heading: 'Markdown' + notes: + - | + When dragging and dropping files such as images and videos into a Markdown editor, GitHub AE now uses the mouse pointer location instead of the cursor location when placing the file. diff --git a/translations/zh-CN/data/reusables/actions/about-actions.md b/translations/zh-CN/data/reusables/actions/about-actions.md index 995119f59d..78425ec818 100644 --- a/translations/zh-CN/data/reusables/actions/about-actions.md +++ b/translations/zh-CN/data/reusables/actions/about-actions.md @@ -1 +1 @@ -{% data variables.product.prodname_actions %} is a continuous integration and continuous delivery (CI/CD) platform that allows you to automate your build, test, and deployment pipeline. +{% data variables.product.prodname_actions %} 是一个持续集成和持续交付 (CI/CD) 平台，可用于自动执行构建、测试和部署管道。 diff --git a/translations/zh-CN/data/reusables/actions/allow-specific-actions-intro.md b/translations/zh-CN/data/reusables/actions/allow-specific-actions-intro.md index 50662d81b5..e9986bccbb 100644 --- a/translations/zh-CN/data/reusables/actions/allow-specific-actions-intro.md +++ b/translations/zh-CN/data/reusables/actions/allow-specific-actions-intro.md @@ -5,8 +5,8 @@ 选择 {% data reusables.actions.policy-label-for-select-actions-workflows %} 时，允许本地操作{% if actions-workflow-policy %} 和可重用工作流程{% endif %} ，并且还有其他选项可用于允许其他特定操作{% if actions-workflow-policy %} 和可重用工作流程{% endif %}： -- **允许 {% data variables.product.prodname_dotcom %} 创建的操作：** 您可以允许 {% data variables.product.prodname_dotcom %} 创建的所有操作用于工作流程。 {% data variables.product.prodname_dotcom %} 创建的操作位于 `actions` 和 `github` 组织中。 更多信息请参阅 [`actions`](https://github.com/actions) 和 [`github`](https://github.com/github) 组织。{% ifversion fpt or ghes or ghae-issue-5094 or ghec %} -- **允许已验证的创建者执行市场操作：** {% ifversion ghes or ghae-issue-5094 %}此选项在您启用 {% data variables.product.prodname_github_connect %} 并配置了 {% data variables.product.prodname_actions %} 时可用。 更多信息请参阅“[使用 GitHub Connect 启用对 GitHub.com 操作的自动访问](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。{% endif %} 您可以允许工作流程使用由经过验证的创建者创建的所有 {% data variables.product.prodname_marketplace %} 操作。 如果 GitHub 验证该操作的创建者为合作伙伴组织，{% octicon "verified" aria-label="The verified badge" %} 徽章将显示在 {% data variables.product.prodname_marketplace %} 中的操作旁边。{% endif %} +- **允许 {% data variables.product.prodname_dotcom %} 创建的操作：** 您可以允许 {% data variables.product.prodname_dotcom %} 创建的所有操作用于工作流程。 {% data variables.product.prodname_dotcom %} 创建的操作位于 `actions` 和 `github` 组织中。 更多信息请参阅 [`actions`](https://github.com/actions) 和 [`github`](https://github.com/github) 组织。{% ifversion fpt or ghes or ghae or ghec %} +- **允许已验证的创建者执行市场操作：** {% ifversion ghes or ghae %}此选项在您启用 {% data variables.product.prodname_github_connect %} 并配置了 {% data variables.product.prodname_actions %} 时可用。 更多信息请参阅“[使用 GitHub Connect 启用对 GitHub.com 操作的自动访问](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)”。{% endif %} 您可以允许工作流程使用由经过验证的创建者创建的所有 {% data variables.product.prodname_marketplace %} 操作。 如果 GitHub 验证该操作的创建者为合作伙伴组织，{% octicon "verified" aria-label="The verified badge" %} 徽章将显示在 {% data variables.product.prodname_marketplace %} 中的操作旁边。{% endif %} - **允许指定的操作{% if actions-workflow-policy %} 和可重用工作流程{% endif %}：** 可以将工作流程限制为使用特定组织和存储库中的操作{% if actions-workflow-policy %} 和可重用工作流程{% endif %}。 要限制对特定标记的访问或者操作{% if actions-workflow-policy %} 或可重用工作流程{% endif %} 的提交 SHA，请使用工作流中使用的相同语法来选择操作{% if actions-workflow-policy %} 或可重用工作流程{% endif %}。 diff --git a/translations/zh-CN/data/reusables/actions/introducing-enterprise.md b/translations/zh-CN/data/reusables/actions/introducing-enterprise.md index 60cb001dfd..7f50bb7255 100644 --- a/translations/zh-CN/data/reusables/actions/introducing-enterprise.md +++ b/translations/zh-CN/data/reusables/actions/introducing-enterprise.md @@ -1 +1 @@ -Before you get started, you should make a plan for how you'll introduce {% data variables.product.prodname_actions %} to your enterprise. For more information, see "[Introducing {% data variables.product.prodname_actions %} to your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise)." +在开始之前，您应该制定一个计划，说明如何将 {% data variables.product.prodname_actions %} 引入企业。 更多信息请参阅“[为企业引入 {% data variables.product.prodname_actions %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise)”。 diff --git a/translations/zh-CN/data/reusables/actions/jobs/using-matrix-strategy.md b/translations/zh-CN/data/reusables/actions/jobs/using-matrix-strategy.md index 7b5a237d79..f2e7a52ba5 100644 --- a/translations/zh-CN/data/reusables/actions/jobs/using-matrix-strategy.md +++ b/translations/zh-CN/data/reusables/actions/jobs/using-matrix-strategy.md @@ -1,4 +1,4 @@ -Use `jobs..strategy.matrix` to define a matrix of different job configurations. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a veriable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`: +Use `jobs..strategy.matrix` to define a matrix of different job configurations. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a variable called `version` with the value `[10, 12, 14]` and a variable called `os` with the value `[ubuntu-latest, windows-latest]`: ```yaml jobs: diff --git a/translations/zh-CN/data/reusables/actions/message-parameters.md b/translations/zh-CN/data/reusables/actions/message-parameters.md index 9e5eee6dd1..146c2f14bb 100644 --- a/translations/zh-CN/data/reusables/actions/message-parameters.md +++ b/translations/zh-CN/data/reusables/actions/message-parameters.md @@ -1 +1 @@ -| 参数 | 值 | | :- | :- |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `title` | 自定义标题 |{% endif %} | `file` | 文件名 | | `col` | 列号，从 1 开始 |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `endColumn` | 结束列号 |{% endif %} | `line` | 行号，从 1 开始 |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} | `endLine` | 结束行号 |{% endif %} +| 参数 | 值 | | :- | :- |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `title` | 自定义标题 |{% endif %} | `file` | 文件名 | | `col` | 列号，从 1 开始 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endColumn` | 结束列号 |{% endif %} | `line` | 行号，从 1 开始 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endLine` | 结束行号 |{% endif %} diff --git a/translations/zh-CN/data/reusables/actions/ref_name-description.md b/translations/zh-CN/data/reusables/actions/ref_name-description.md index 4a39dc1922..dd3066b59c 100644 --- a/translations/zh-CN/data/reusables/actions/ref_name-description.md +++ b/translations/zh-CN/data/reusables/actions/ref_name-description.md @@ -1 +1 @@ -The branch or tag name that triggered the workflow run. +触发工作流程的分支或标记名称。 diff --git a/translations/zh-CN/data/reusables/actions/ref_protected-description.md b/translations/zh-CN/data/reusables/actions/ref_protected-description.md index 9975dc406a..c0fd06d410 100644 --- a/translations/zh-CN/data/reusables/actions/ref_protected-description.md +++ b/translations/zh-CN/data/reusables/actions/ref_protected-description.md @@ -1 +1 @@ -`true` if branch protections are configured for the ref that triggered the workflow run. +如果为触发工作流运行的 ref 配置了分支保护，则为 `true`。 diff --git a/translations/zh-CN/data/reusables/actions/ref_type-description.md b/translations/zh-CN/data/reusables/actions/ref_type-description.md index 74888dee73..4a695cd93c 100644 --- a/translations/zh-CN/data/reusables/actions/ref_type-description.md +++ b/translations/zh-CN/data/reusables/actions/ref_type-description.md @@ -1 +1 @@ -The type of ref that triggered the workflow run. Valid values are `branch` or `tag`. +触发工作流程运行的引用类型。 有效值为 `branch` 或 `tag`。 diff --git a/translations/zh-CN/data/reusables/actions/self-hosted-runner-ports-protocols.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-ports-protocols.md index a24c445d1b..a905a163f9 100644 --- a/translations/zh-CN/data/reusables/actions/self-hosted-runner-ports-protocols.md +++ b/translations/zh-CN/data/reusables/actions/self-hosted-runner-ports-protocols.md @@ -1,3 +1,3 @@ {% ifversion ghes or ghae %} -The connection between self-hosted runners and {% data variables.product.product_name %} is over {% ifversion ghes %}HTTP (port 80) or {% endif %}HTTPS (port 443). {% ifversion ghes %}To ensure connectivity over HTTPS, configure TLS for {% data variables.product.product_location %}. For more information, see "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)."{% endif %} +自托管运行器与 {% data variables.product.product_name %} 之间的连接通过{% ifversion ghes %}HTTP（端口 80）或 {% endif %}HTTPS（端口 443）。 {% ifversion ghes %}要确保通过 HTTPS 的连接，请为 {% data variables.product.product_location %} 配置 TLS。 更多信息请参阅“[配置 TLS](/admin/configuration/configuring-network-settings/configuring-tls)”。{% endif %} {% endif %} diff --git a/translations/zh-CN/data/reusables/advanced-security/check-for-ghas-license.md b/translations/zh-CN/data/reusables/advanced-security/check-for-ghas-license.md index 9fcc39ac76..8e041aa334 100644 --- a/translations/zh-CN/data/reusables/advanced-security/check-for-ghas-license.md +++ b/translations/zh-CN/data/reusables/advanced-security/check-for-ghas-license.md @@ -1 +1 @@ -You can identify if your enterprise has a {% data variables.product.prodname_GH_advanced_security %} license by reviewing your enterprise settings. For more information, see "[Enabling GitHub Advanced Security for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise#checking-whether-your-license-includes-github-advanced-security)." +您可以通过查看企业设置来确定您的企业是否具有 {% data variables.product.prodname_GH_advanced_security %} 许可证。 更多信息请参阅“[为企业启用 GitHub Advanced Security](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise#checking-whether-your-license-includes-github-advanced-security)”。 diff --git a/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md index 80a1833994..1c83fc9695 100644 --- a/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md +++ b/translations/zh-CN/data/reusables/apps/deprecating_auth_with_query_parameters.md @@ -1,4 +1,3 @@ -{% ifversion fpt or ghes or ghae or ghec %} {% warning %} **Deprecation Notice:** {% data variables.product.prodname_dotcom %} will discontinue authentication to the API using query parameters. Authenticating to the API should be done with [HTTP basic authentication](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens).{% ifversion fpt or ghec %} Using query parameters to authenticate to the API will no longer work on May 5, 2021. {% endif %} For more information, including scheduled brownouts, see the [blog post](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/). @@ -6,4 +5,3 @@ {% ifversion ghes or ghae %} Authentication to the API using query parameters while available is no longer supported due to security concerns. Instead we recommend integrators move their access token, `client_id`, or `client_secret` in the header. {% data variables.product.prodname_dotcom %} will announce the removal of authentication by query parameters with advanced notice. {% endif %} {% endwarning %} -{% endif %} diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md b/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md index 640b27704e..b4c6fa7e40 100644 --- a/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md +++ b/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md @@ -28,13 +28,13 @@ {%- ifversion ghes %} | `config_entry` | Contains activities related to configuration settings. 这些事件仅在站点管理员审核日志中可见。 {%- endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | `dependabot_alerts` | 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` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. | `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access. {%- endif %} {%- ifversion fpt or ghec or ghes > 3.2 %} | `dependabot_security_updates` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. 更多信息请参阅“[配置 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)。” | `dependabot_security_updates_new_repos` | 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 or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} | `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 | `dependency_graph_new_repos` | Contains organization-level configuration activities for new repositories created in the organization. {%- endif %} {%- ifversion fpt or ghec %} @@ -116,7 +116,7 @@ {%- ifversion fpt or ghec %} | `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization. {%- endif %} -{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %} +{%- ifversion fpt or ghec or ghes or ghae %} | `repository_vulnerability_alert` | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies). {%- endif %} {%- ifversion fpt or ghec %} diff --git a/translations/zh-CN/data/reusables/cli/filter-issues-and-pull-requests-tip.md b/translations/zh-CN/data/reusables/cli/filter-issues-and-pull-requests-tip.md index bd54057f7e..a574398f81 100644 --- a/translations/zh-CN/data/reusables/cli/filter-issues-and-pull-requests-tip.md +++ b/translations/zh-CN/data/reusables/cli/filter-issues-and-pull-requests-tip.md @@ -1,7 +1,5 @@ -{% ifversion fpt or ghes or ghae or ghec %} {% tip %} **提示**：您也可以使用 {% data variables.product.prodname_cli %} 过滤议题或拉取请求。 更多信息请参阅 {% data variables.product.prodname_cli %} 文档中的 "[`gh issue list`](https://cli.github.com/manual/gh_issue_list)" 或 "[`gh pr list`](https://cli.github.com/manual/gh_pr_list)"。 {% endtip %} -{% endif %} diff --git a/translations/zh-CN/data/reusables/code-scanning/alert-tracking-link.md b/translations/zh-CN/data/reusables/code-scanning/alert-tracking-link.md index 25b7b94f3b..b8d7a4ae28 100644 --- a/translations/zh-CN/data/reusables/code-scanning/alert-tracking-link.md +++ b/translations/zh-CN/data/reusables/code-scanning/alert-tracking-link.md @@ -1,2 +1,2 @@ -For more information about creating issues to track {% data variables.product.prodname_code_scanning %} alerts, see "[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)." +有关创建议题以跟踪 {% data variables.product.prodname_code_scanning %} 警报的详细信息，请参阅“[使用任务列表跟踪议题中的 {% 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)”。 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 a3d0bf5c2a..ccf377e20c 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 @@ -2,9 +2,9 @@ {% note %} -**Note:** The tracking of {% data variables.product.prodname_code_scanning %} alerts in issues is in beta and subject to change. +**注意：** 议题中 {% data variables.product.prodname_code_scanning %} 警报的跟踪处于测试阶段，可能会发生更改。 -This feature supports running analysis natively using {% data variables.product.prodname_actions %} or externally using existing CI/CD infrastructure, as well as third-party {% data variables.product.prodname_code_scanning %} tools, but _not_ third-party tracking tools. +此功能支持使用 {% data variables.product.prodname_actions %} 在本地运行分析，或使用现有 CI/CD 基础结构以及第三方 {% data variables.product.prodname_code_scanning %} 工具在外部运行分析，但_不_使用第三方跟踪工具。 {% endnote %} {% endif %} diff --git a/translations/zh-CN/data/reusables/code-scanning/beta.md b/translations/zh-CN/data/reusables/code-scanning/beta.md index 42bf4638be..bf3f2b88e5 100644 --- a/translations/zh-CN/data/reusables/code-scanning/beta.md +++ b/translations/zh-CN/data/reusables/code-scanning/beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-5752 %} +{% ifversion ghae %} diff --git a/translations/zh-CN/data/reusables/code-scanning/github-issues-integration.md b/translations/zh-CN/data/reusables/code-scanning/github-issues-integration.md index e382a70813..7d8b33308b 100644 --- a/translations/zh-CN/data/reusables/code-scanning/github-issues-integration.md +++ b/translations/zh-CN/data/reusables/code-scanning/github-issues-integration.md @@ -1,3 +1,3 @@ -{% data variables.product.prodname_code_scanning_capc %} alerts integrate with task lists in {% data variables.product.prodname_github_issues %} to make it easy for you to prioritize and track alerts with all your development work. 有关议题的更多信息，请参阅“[关于议题](/issues/tracking-your-work-with-issues/about-issues)”。 +{% data variables.product.prodname_code_scanning_capc %} 警报与 {% data variables.product.prodname_github_issues %} 中的任务列表集成，可让您轻松地在所有开发工作中确定警报的优先级并进行跟踪。 有关议题的更多信息，请参阅“[关于议题](/issues/tracking-your-work-with-issues/about-issues)”。 -To track a code scanning alert in an issue, add the URL for the alert as a task list item in the issue. For more information about task lists, see "[About tasks lists](/issues/tracking-your-work-with-issues/about-task-lists)." +要跟踪议题中的代码扫描警报，请将警报的 URL 添加为议题中的任务列表项。 有关任务列表的更多信息，请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/about-task-lists)”。 diff --git a/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md index 157489ba84..0eae7a1f6f 100644 --- a/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md +++ b/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md @@ -1 +1 @@ -1. 在 {% data variables.product.prodname_vscode %} 中，从左侧边栏单击 Remote Explorer 图标。 ![{% data variables.product.prodname_vscode %} 中的 Remote Explorer 图标](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) +1. 在 {% data variables.product.prodname_vscode_shortname %} 中，从左侧边栏单击 Remote Explorer 图标。 ![{% data variables.product.prodname_vscode %} 中的 Remote Explorer 图标](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png) diff --git a/translations/zh-CN/data/reusables/codespaces/committing-link-to-procedure.md b/translations/zh-CN/data/reusables/codespaces/committing-link-to-procedure.md index 89b6a8e543..b5a8fa1551 100644 --- a/translations/zh-CN/data/reusables/codespaces/committing-link-to-procedure.md +++ b/translations/zh-CN/data/reusables/codespaces/committing-link-to-procedure.md @@ -1,3 +1,3 @@ -在对代码空间进行更改（无论是添加新代码还是更改配置）之后，您需要提交更改。 将更改提交到仓库可确保从此仓库创建代码空间的其他任何人都具有相同的配置。 这也意味着您所做的任何自定义，例如添加 {% data variables.product.prodname_vscode %} 扩展，都会显示给所有用户。 +在对代码空间进行更改（无论是添加新代码还是更改配置）之后，您需要提交更改。 将更改提交到仓库可确保从此仓库创建代码空间的其他任何人都具有相同的配置。 这也意味着您所做的任何自定义，例如添加 {% data variables.product.prodname_vscode_shortname %} 扩展，都会显示给所有用户。 有关信息，请参阅“[在代码空间中使用源控制](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)”。 diff --git a/translations/zh-CN/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/zh-CN/data/reusables/codespaces/connect-to-codespace-from-vscode.md index 795ded63dd..86ed616975 100644 --- a/translations/zh-CN/data/reusables/codespaces/connect-to-codespace-from-vscode.md +++ b/translations/zh-CN/data/reusables/codespaces/connect-to-codespace-from-vscode.md @@ -1 +1 @@ -您可以直接从 {% data variables.product.prodname_vscode %} 连接至您的代码空间。 更多信息请参阅“[在 {% data variables.product.prodname_vscode %} 中使用代码空间](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)”。 +您可以直接从 {% data variables.product.prodname_vscode_shortname %} 连接至您的代码空间。 更多信息请参阅“[在 {% data variables.product.prodname_vscode_shortname %} 中使用代码空间](/github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code)”。 diff --git a/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md index 45dcfb353e..ee1fbbee0b 100644 --- a/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md +++ b/translations/zh-CN/data/reusables/codespaces/creating-a-codespace-in-vscode.md @@ -1,8 +1,8 @@ -将 {% data variables.product.product_location %} 上的帐户连接到 {% data variables.product.prodname_github_codespaces %} 扩展后，可以创建新的代码空间。 有关 {% data variables.product.prodname_github_codespaces %} 扩展的详细信息，请参阅 [{% data variables.product.prodname_vscode %} Marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces)。 +将 {% data variables.product.product_location %} 上的帐户连接到 {% data variables.product.prodname_github_codespaces %} 扩展后，可以创建新的代码空间。 有关 {% data variables.product.prodname_github_codespaces %} 扩展的详细信息，请参阅 [{% data variables.product.prodname_vs_marketplace_shortname %} Marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces)。 {% note %} -**注意**：目前， {% data variables.product.prodname_vscode %} 不允许在创建代码空间时选择开发容器配置。 如果要选择特定的开发容器配置，请使用 {% data variables.product.prodname_dotcom %} Web 界面创建代码空间。 有关详细信息，请单击此页顶部的 **Web browser（Web 浏览器）**选项卡。 +**注意**：目前，{% data variables.product.prodname_vscode_shortname %} 不允许在创建代码空间时选择开发容器配置。 如果要选择特定的开发容器配置，请使用 {% data variables.product.prodname_dotcom %} Web 界面创建代码空间。 有关详细信息，请单击此页顶部的 **Web browser（Web 浏览器）**选项卡。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/codespaces/deleting-a-codespace-in-vscode.md b/translations/zh-CN/data/reusables/codespaces/deleting-a-codespace-in-vscode.md index 9c663d0a65..6c27ec39d6 100644 --- a/translations/zh-CN/data/reusables/codespaces/deleting-a-codespace-in-vscode.md +++ b/translations/zh-CN/data/reusables/codespaces/deleting-a-codespace-in-vscode.md @@ -1,4 +1,4 @@ -当前不在代码空间中工作时，可以从 {% data variables.product.prodname_vscode %} 中删除代码空间。 +当前不在代码空间中工作时，可以从 {% data variables.product.prodname_vscode_shortname %} 中删除代码空间。 {% data reusables.codespaces.click-remote-explorer-icon-vscode %} 1. 在“GITHUB CODESPACES”下，右键单击要删除的代码空间。 diff --git a/translations/zh-CN/data/reusables/codespaces/links-to-get-started.md b/translations/zh-CN/data/reusables/codespaces/links-to-get-started.md index 5448b6204f..a446c97a1b 100644 --- a/translations/zh-CN/data/reusables/codespaces/links-to-get-started.md +++ b/translations/zh-CN/data/reusables/codespaces/links-to-get-started.md @@ -1 +1 @@ -To get started with {% data variables.product.prodname_codespaces %}, see "[Quickstart for {% data variables.product.prodname_codespaces %}](/codespaces/getting-started/quickstart)." To learn more about how {% data variables.product.prodname_codespaces %} works, see "[Deep dive into Codespaces](/codespaces/getting-started/deep-dive)." +要开始使用 {% data variables.product.prodname_codespaces %}，请参阅“[{% data variables.product.prodname_codespaces %}](/codespaces/getting-started/quickstart)快速入门”。 要了解有关 {% data variables.product.prodname_codespaces %} 工作原理的更多信息，请参阅“[深入了解代码空间](/codespaces/getting-started/deep-dive)”。 diff --git a/translations/zh-CN/data/reusables/codespaces/more-info-devcontainer.md b/translations/zh-CN/data/reusables/codespaces/more-info-devcontainer.md index 430a9f1156..f0fd5c863b 100644 --- a/translations/zh-CN/data/reusables/codespaces/more-info-devcontainer.md +++ b/translations/zh-CN/data/reusables/codespaces/more-info-devcontainer.md @@ -1 +1 @@ -For information about the settings and properties that you can set in a `devcontainer.json` file, see "[devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json)" in the {% data variables.product.prodname_vscode %} documentation. \ No newline at end of file +For information about the settings and properties that you can set in a `devcontainer.json` file, see "[devcontainer.json reference](https://aka.ms/vscode-remote/devcontainer.json)" in the {% data variables.product.prodname_vscode_shortname %} documentation. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/use-visual-studio-features.md b/translations/zh-CN/data/reusables/codespaces/use-visual-studio-features.md index dc30c73437..33fd92d4e9 100644 --- a/translations/zh-CN/data/reusables/codespaces/use-visual-studio-features.md +++ b/translations/zh-CN/data/reusables/codespaces/use-visual-studio-features.md @@ -1 +1 @@ -使用 {% data variables.product.prodname_vscode %} 在代码空间中开发时，您可以编辑代码、调试和使用 Git 命令。 更多信息请参阅 [{% data variables.product.prodname_vscode %} 文档](https://code.visualstudio.com/docs)。 +使用 {% data variables.product.prodname_vscode_shortname %} 在代码空间中开发时，您可以编辑代码、调试和使用 Git 命令。 更多信息请参阅 [{% data variables.product.prodname_vscode_shortname %} 文档](https://code.visualstudio.com/docs)。 diff --git a/translations/zh-CN/data/reusables/codespaces/vscode-settings-order.md b/translations/zh-CN/data/reusables/codespaces/vscode-settings-order.md index 28c82030d8..0de9ab5609 100644 --- a/translations/zh-CN/data/reusables/codespaces/vscode-settings-order.md +++ b/translations/zh-CN/data/reusables/codespaces/vscode-settings-order.md @@ -1 +1 @@ -配置 {% data variables.product.prodname_vscode %} 的编辑器设置时，有三个可用的作用域：_工作区_、_远程 [Codespaces]_和_用户_。 如果在多个作用域中定义了设置，_工作区_设置优先级最高，_远程 [Codespaces]_ 次之，最后是_用户_。 +配置 {% data variables.product.prodname_vscode_shortname %} 的编辑器设置时，有三个可用的作用域：_工作区_、_远程 [Codespaces]_和_用户_。 如果在多个作用域中定义了设置，_工作区_设置优先级最高，_远程 [Codespaces]_ 次之，最后是_用户_。 diff --git a/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md b/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md index f50ef78f03..a71f8d2aa1 100644 --- a/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md +++ b/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md @@ -2,7 +2,7 @@ {% note %} -**Note:** Dependabot security updates and version updates are currently available for {% data variables.product.prodname_ghe_cloud %} and in beta for {% data variables.product.prodname_ghe_server %} 3.3. Please [contact your account management team](https://enterprise.github.com/contact) for instructions on enabling Dependabot updates. +**注意：** Dependabot 安全更新和版本更新目前可用于 {% data variables.product.prodname_ghe_cloud %} 以及 {% data variables.product.prodname_ghe_server %} 3.3 的测试版。 请[联系您的客户管理团队](https://enterprise.github.com/contact)，以获取有关启用 Dependabot 更新的说明。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates.md b/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates.md index 948349fcb4..4b95df8409 100644 --- a/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates.md +++ b/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates.md @@ -2,9 +2,9 @@ {% note %} {% ifversion ghes = 3.4 %} -**Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in public beta and subject to change. +**注意：** {% data variables.product.prodname_dependabot %} 安全和版本更新目前处于公开测试阶段，可能会发生更改。 {% else %} -**Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in private beta and subject to change. Please [contact your account management team](https://enterprise.github.com/contact) for instructions on enabling Dependabot updates. +**注意：** {% data variables.product.prodname_dependabot %} 安全和版本更新目前处于私密测试阶段，可能会发生更改。 请[联系您的客户管理团队](https://enterprise.github.com/contact)，以获取有关启用 Dependabot 更新的说明。 {% endif %} {% endnote %} @@ -15,7 +15,7 @@ {% note %} -**Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in public beta and subject to change. +**注意：** {% data variables.product.prodname_dependabot %} 安全和版本更新目前处于公开测试阶段，可能会发生更改。 {% endnote %} {% endif %} diff --git a/translations/zh-CN/data/reusables/dependabot/dependabot-alerts-beta.md b/translations/zh-CN/data/reusables/dependabot/dependabot-alerts-beta.md index 4b2b4947b8..10551d51b8 100644 --- a/translations/zh-CN/data/reusables/dependabot/dependabot-alerts-beta.md +++ b/translations/zh-CN/data/reusables/dependabot/dependabot-alerts-beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-4864 %} +{% ifversion ghae %} {% note %} **注意：**{% data variables.product.prodname_dependabot_alerts %} 目前处于测试阶段，可能会更改。 diff --git a/translations/zh-CN/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md b/translations/zh-CN/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md index d5ae9b8415..930c6ac941 100644 --- a/translations/zh-CN/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md +++ b/translations/zh-CN/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md @@ -1,3 +1,3 @@ -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} Enterprise owners can configure {% ifversion ghes %}the dependency graph and {% endif %}{% data variables.product.prodname_dependabot_alerts %} for an enterprise. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} diff --git a/translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md b/translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md index 5371719aaa..1df0abf905 100644 --- a/translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md +++ b/translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md @@ -2,7 +2,7 @@ {% note %} -**Note:** Your site administrator must set up {% data variables.product.prodname_dependabot_updates %} for {% data variables.product.product_location %} before you can use this feature. 更多信息请参阅“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。 +**Note:** Your site administrator must set up {% data variables.product.prodname_dependabot_updates %} for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endnote %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md b/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md index 534d9c25e0..6ce601a146 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md @@ -1 +1 @@ -{% ifversion not ghec%}By default, a{% else %}A{% endif %} user account is considered to be dormant if it has not been active for 90 days. {% ifversion not ghec %}You can configure the length of time a user must be inactive to be considered dormant{% ifversion ghes%} and choose to suspend dormant users to release user licenses{% endif %}.{% endif %} +{% ifversion not ghec%}默认情况下，如果{% else %}{% endif %} 用户帐户在 90 天内未处于活动状态，则该用户帐户被视为处于休眠状态。 {% ifversion not ghec %}您可以配置用户必须处于非活动状态才能被视为休眠{% ifversion ghes%} 的时间长度，并选择挂起休眠用户以释放用户许可证{% endif %}。{% endif %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md b/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md index b200d8f417..9d3540b679 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md @@ -3,4 +3,4 @@ - 评论问题和拉取请求。 - 创建、删除、关注仓库和加星标。 - 推送提交。 -- Accessing resources by using a personal access token or SSH key. +- 使用个人访问令牌或 SSH 密钥访问资源。 diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-release-phase.md b/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-release-phase.md index 3ac13f7607..28b6184842 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-release-phase.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-release-phase.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The Dormant Users report is currently in beta and subject to change. During the beta, ongoing improvements to the report download feature may limit its availability. +**注意：** “休眠用户”报告目前处于测试阶段，可能会有所变化。 在测试期间，对报告下载功能的持续改进可能会限制其可用性。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-accounts-compliance-tab.md b/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-accounts-compliance-tab.md index a16d7459ab..bfa09a0727 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-accounts-compliance-tab.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/enterprise-accounts-compliance-tab.md @@ -1 +1 @@ -1. In the enterprise account sidebar, click {% octicon "checklist" aria-label="The Compliance icon" %} **Compliance**. ![Compliance tab in the enterprise account sidebar](/assets/images/help/business-accounts/enterprise-accounts-compliance-tab.png) +1. 在企业帐户侧边栏中，单击 {% octicon "checklist" aria-label="The Compliance icon" %} **Compliance（合规性）**。 ![企业帐户边栏中的 Compliance（合规性）选项卡](/assets/images/help/business-accounts/enterprise-accounts-compliance-tab.png) diff --git a/translations/zh-CN/data/reusables/enterprise/create-an-enterprise-account.md b/translations/zh-CN/data/reusables/enterprise/create-an-enterprise-account.md index 031039863b..97c8410a24 100644 --- a/translations/zh-CN/data/reusables/enterprise/create-an-enterprise-account.md +++ b/translations/zh-CN/data/reusables/enterprise/create-an-enterprise-account.md @@ -1 +1 @@ -If you currently use {% data variables.product.prodname_ghe_cloud %} with a single organization, we encourage you to create an enterprise account. +如果您目前在单个组织中使用 {% data variables.product.prodname_ghe_cloud %} ，我们建议您创建一个企业帐户。 diff --git a/translations/zh-CN/data/reusables/enterprise/repository-caching-config-summary.md b/translations/zh-CN/data/reusables/enterprise/repository-caching-config-summary.md index 73fde0a21b..1dadf049f6 100644 --- a/translations/zh-CN/data/reusables/enterprise/repository-caching-config-summary.md +++ b/translations/zh-CN/data/reusables/enterprise/repository-caching-config-summary.md @@ -1 +1 @@ -You can configure repository caching by creating a special type of replica called a repository cache. +您可以通过创建一种称为存储库缓存的特殊类型的副本来配置存储库缓存。 diff --git a/translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md b/translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md index a6035dfd4f..7287ae406d 100644 --- a/translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md +++ b/translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md @@ -1,5 +1,5 @@ {% note %} -**Note:** Repository caching is currently in beta and subject to change. +**注意：** 存储库缓存目前处于测试阶段，可能会发生更改。 {% endnote %} diff --git a/translations/zh-CN/data/reusables/gated-features/dependency-review.md b/translations/zh-CN/data/reusables/gated-features/dependency-review.md index 9fc21444cb..63777f00ca 100644 --- a/translations/zh-CN/data/reusables/gated-features/dependency-review.md +++ b/translations/zh-CN/data/reusables/gated-features/dependency-review.md @@ -7,7 +7,7 @@ {%- elsif ghes > 3.1 %} 依赖项审查适用于 {% data variables.product.product_name %} 中的组织拥有的存储库。 此功能需要 {% data variables.product.prodname_GH_advanced_security %} 的许可证。 -{%- elsif ghae-issue-4864 %} +{%- elsif ghae %} 依赖项审查适用于 {% data variables.product.product_name %} 中的组织拥有的存储库。 这是一项 {% data variables.product.prodname_GH_advanced_security %} 功能（在测试版期间免费）。 -{%- endif %} {% data reusables.advanced-security.more-info-ghas %} \ No newline at end of file +{%- endif %} {% data reusables.advanced-security.more-info-ghas %} diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-confirm-scim.md b/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-confirm-scim.md index 2cadcc5846..1b35caaa6f 100644 --- a/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-confirm-scim.md +++ b/translations/zh-CN/data/reusables/identity-and-permissions/team-sync-confirm-scim.md @@ -1 +1 @@ -1. We recommend you confirm that your users have SAML enabled and have a linked SCIM identity to avoid potential provisioning errors. For help auditing your users, see "[Auditing users for missing SCIM metadata](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management#auditing-users-for-missing-scim-metadata)." For help resolving unlinked SCIM identities, see "[Troubleshooting identity and access management](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management)." +1. 建议确认您的用户已启用 SAML 并具有链接的 SCIM 标识，以避免潜在的预配错误。 For help auditing your users, see "[Auditing users for missing SCIM metadata](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management#auditing-users-for-missing-scim-metadata)." For help resolving unlinked SCIM identities, see "[Troubleshooting identity and access management](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management)." diff --git a/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md index c59d32ea72..cb54ff0e81 100644 --- a/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md +++ b/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes or ghae or ghec %} 您可以选择 您关注或已订阅安全警报通知的仓库中 {% data variables.product.prodname_dependabot_alerts %} 通知的递送方式和频率。 {% endif %} diff --git a/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md b/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md index 8d2b81380d..96569a17c1 100644 --- a/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md +++ b/translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md @@ -1,5 +1,5 @@ -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} -{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes > 3.1 or ghae %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %} - by email, an email is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**Email each time a vulnerability is found** option). - in the user interface, a warning is shown in your repository's file and code views if there are any vulnerable dependencies (**UI alerts** option). diff --git a/translations/zh-CN/data/reusables/organizations/security-overview-feature-specific-page.md b/translations/zh-CN/data/reusables/organizations/security-overview-feature-specific-page.md new file mode 100644 index 0000000000..e9e1e1efd0 --- /dev/null +++ b/translations/zh-CN/data/reusables/organizations/security-overview-feature-specific-page.md @@ -0,0 +1 @@ +1. 或者，也可以使用左侧边栏按安全功能筛选信息。 On each page, you can use filters that are specific to that feature to fine-tune your search. diff --git a/translations/zh-CN/data/reusables/organizations/team_maintainers_can.md b/translations/zh-CN/data/reusables/organizations/team_maintainers_can.md index f40ccc6000..d2b271143c 100644 --- a/translations/zh-CN/data/reusables/organizations/team_maintainers_can.md +++ b/translations/zh-CN/data/reusables/organizations/team_maintainers_can.md @@ -10,6 +10,6 @@ - [添加组织成员到团队](/articles/adding-organization-members-to-a-team) - [从团队中删除组织成员](/articles/removing-organization-members-from-a-team) - [将组织成员升级为团队维护员](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member) -- 删除团队对仓库的访问权限{% ifversion fpt or ghes or ghae or ghec %} -- [管理团队的代码审查设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% endif %}{% ifversion fpt or ghec %} +- 删除团队对仓库的访问权限 +- [管理团队的代码审查设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% ifversion fpt or ghec %} - [管理拉取请求的预定提醒](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %} diff --git a/translations/zh-CN/data/reusables/pull_requests/close-issues-using-keywords.md b/translations/zh-CN/data/reusables/pull_requests/close-issues-using-keywords.md index 470dc8e298..638579a0d6 100644 --- a/translations/zh-CN/data/reusables/pull_requests/close-issues-using-keywords.md +++ b/translations/zh-CN/data/reusables/pull_requests/close-issues-using-keywords.md @@ -1 +1 @@ -您可以将拉取请求链接到议题，以便{% ifversion fpt or ghes or ghae or ghec %}显示正在进行修复并{% endif %}在有人合并拉取请求时自动关闭议题。 更多信息请参阅“[将拉取请求链接到议题](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)”。 +您可以将拉取请求链接到议题，以显示正在进行修复，并在有人合并拉取请求时自动关闭议题。 更多信息请参阅“[将拉取请求链接到议题](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)”。 diff --git a/translations/zh-CN/data/reusables/repositories/copy-clone-url.md b/translations/zh-CN/data/reusables/repositories/copy-clone-url.md index 1fe13d407a..2c3ab6fcf6 100644 --- a/translations/zh-CN/data/reusables/repositories/copy-clone-url.md +++ b/translations/zh-CN/data/reusables/repositories/copy-clone-url.md @@ -1,6 +1,6 @@ 1. 在文件列表上方，单击 {% octicon "download" aria-label="The download icon" %} ****Code（代码）。 !["代码"按钮](/assets/images/help/repository/code-button.png) -1. 要使用 HTTPS 克隆仓库，请在“Clone with HTTPS（使用 HTTPS 克隆）”下单击 -{% octicon "clippy" aria-label="The clipboard icon" %}. 要使用 SSH 密钥克隆仓库，包括组织的 SSH 认证中心颁发的证书，单击 **Use SSH（使用 SSH）**，然后单击 {% octicon "clippy" aria-label="The clipboard icon" %}。 要使用 {% data variables.product.prodname_cli %} 克隆存储库，请单击 **使用 {% data variables.product.prodname_cli %}**，然后单击 {% octicon "clippy" aria-label="The clipboard icon" %}。 - ![用于复制 URL 以克隆仓库的剪贴板图标](/assets/images/help/repository/https-url-clone.png) - {% ifversion fpt or ghes or ghae or ghec %} - ![用于复制 URL 以使用 GitHub CLI 克隆仓库的剪贴板图标](/assets/images/help/repository/https-url-clone-cli.png){% endif %} +1. 复制存储库的 URL。 + + - 要使用 HTTPS 克隆仓库，在“HTTPS”下单击 {% octicon "clippy" aria-label="The clipboard icon" %}。 + - 要使用 SSH 密钥克隆仓库，包括组织的 SSH 认证中心颁发的证书，单击 **SSH**，然后单击 {% octicon "clippy" aria-label="The clipboard icon" %}。 + - 要使用 {% data variables.product.prodname_cli %} 克隆存储库，请单击 **{% data variables.product.prodname_cli %}**，然后单击 {% octicon "clippy" aria-label="The clipboard icon" %}。 ![用于复制 URL 以使用 GitHub CLI 克隆仓库的剪贴板图标](/assets/images/help/repository/https-url-clone-cli.png) diff --git a/translations/zh-CN/data/reusables/repositories/default-issue-templates.md b/translations/zh-CN/data/reusables/repositories/default-issue-templates.md index c4852ecff5..5f5b8cec0a 100644 --- a/translations/zh-CN/data/reusables/repositories/default-issue-templates.md +++ b/translations/zh-CN/data/reusables/repositories/default-issue-templates.md @@ -1,2 +1 @@ -您可以创建默认的议题模板{% ifversion fpt or ghes or ghae or ghec %} 和议题模板的默认配置文件{% endif %}，适用于您的组织{% ifversion fpt or ghes or ghae or ghec %} 或个人帐户{% endif %}。 更多信息请参阅“[创建默认社区健康文件](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)”。 - +您可以为组织或个人帐户的议题模板创建默认议题模板和默认配置文件。 更多信息请参阅“[创建默认社区健康文件](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)”。 diff --git a/translations/zh-CN/data/reusables/repositories/dependency-review.md b/translations/zh-CN/data/reusables/repositories/dependency-review.md index 8f1c0afb82..5f0086b3e9 100644 --- a/translations/zh-CN/data/reusables/repositories/dependency-review.md +++ b/translations/zh-CN/data/reusables/repositories/dependency-review.md @@ -1,4 +1,4 @@ -{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} +{% ifversion fpt or ghes > 3.1 or ghae or ghec %} 此外， {% data variables.product.prodname_dotcom %} 可以查看在针对仓库默认分支的拉取请求中添加、更新或删除的任何依赖项，并标记任何将漏洞引入项目的变化。 这允许您在易受攻击的依赖项到达您的代码库之前发现并处理它们，而不是事后处理。 更多信息请参阅“[审查拉取请求中的依赖项更改](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request)”。 {% endif %} diff --git a/translations/zh-CN/data/reusables/repositories/enable-security-alerts.md b/translations/zh-CN/data/reusables/repositories/enable-security-alerts.md index 61a3c1b50d..375d5d5c4c 100644 --- a/translations/zh-CN/data/reusables/repositories/enable-security-alerts.md +++ b/translations/zh-CN/data/reusables/repositories/enable-security-alerts.md @@ -1,3 +1,3 @@ -{% ifversion ghes or ghae-issue-4864 %} +{% ifversion ghes or ghae %} Enterprise owners must enable {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} diff --git a/translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md b/translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md index dae9b1f388..330171023c 100644 --- a/translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md +++ b/translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md @@ -1 +1 @@ -{% ifversion fpt or ghes or ghae or ghec %}如果你的仓库中有需要线性提交历史记录的受保护分支规则，必须允许压缩合并和/或变基合并。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)”。{% endif %} +如果你的仓库中有需要线性提交历史记录的受保护分支规则，必须允许压缩合并和/或变基合并。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)”。 diff --git a/translations/zh-CN/data/reusables/repositories/start-line-comment.md b/translations/zh-CN/data/reusables/repositories/start-line-comment.md index 97f47b1a23..5e2b477878 100644 --- a/translations/zh-CN/data/reusables/repositories/start-line-comment.md +++ b/translations/zh-CN/data/reusables/repositories/start-line-comment.md @@ -1 +1 @@ -1. 将鼠标悬停在您要添加评论的代码行上，然后单击蓝色评论图标。{% ifversion fpt or ghes or ghae or ghec %} 要在多行上添加评论，请单击并拖动以选择行范围，然后单击蓝色评论图标。{% endif %} ![蓝色评论图标](/assets/images/help/commits/hover-comment-icon.gif) +1. 将鼠标悬停在要添加评论的代码行上，然后单击蓝色评论图标。 要在多行上添加评论，请单击并拖动以选择行的范围，然后单击蓝色评论图标。 ![蓝色评论图标](/assets/images/help/commits/hover-comment-icon.gif) diff --git a/translations/zh-CN/data/reusables/repositories/suggest-changes.md b/translations/zh-CN/data/reusables/repositories/suggest-changes.md index cf063cc9f2..97f0591347 100644 --- a/translations/zh-CN/data/reusables/repositories/suggest-changes.md +++ b/translations/zh-CN/data/reusables/repositories/suggest-changes.md @@ -1 +1 @@ -1. （可选）要建议对一行{% ifversion fpt or ghes or ghae or ghec %}或多行{% endif %}进行特定更改，请单击 {% octicon "diff" aria-label="The diff symbol" %}，然后在建议块内编辑文本。 ![建议块](/assets/images/help/pull_requests/suggestion-block.png) +1. （可选）要建议对行进行特定的更改，请单击 {% octicon "diff" aria-label="The diff symbol" %}，然后在建议块内编辑文本。 ![建议块](/assets/images/help/pull_requests/suggestion-block.png) diff --git a/translations/zh-CN/data/reusables/saml/authorized-creds-info.md b/translations/zh-CN/data/reusables/saml/authorized-creds-info.md index 20edaeb3fa..6140c36f47 100644 --- a/translations/zh-CN/data/reusables/saml/authorized-creds-info.md +++ b/translations/zh-CN/data/reusables/saml/authorized-creds-info.md @@ -1,7 +1,7 @@ -Before you can authorize a personal access token or SSH key, you must have a linked SAML identity. If you're a member of an organization where SAML SSO is enabled, you can create a linked identity by authenticating to your organization with your IdP at least once. 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)”。 +在授权个人访问令牌或 SSH 密钥之前，您必须具有链接的 SAML 标识。 如果您是启用了 SAML SSO 的组织的成员，则可以通过至少一次使用 IdP 向组织验证来创建链接身份。 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)”。 -After you authorize a personal access token or SSH key. The token or key will stay authorized until revoked in one of these ways. -- An organization or enterprise owner revokes the authorization. -- You are removed from the organization. -- The scopes in a personal access token are edited, or the token is regenerated. -- The personal access token expired as defined during creation. +授权个人访问令牌或 SSH 密钥后。 令牌或密钥将保持授权状态，直到以下面方式之一吊销。 +- 组织或企业所有者撤销授权。 +- 您已从组织中删除。 +- 编辑个人访问令牌中的范围，或重新生成令牌。 +- 个人访问令牌已过期，如创建期间所定义的那样。 diff --git a/translations/zh-CN/data/reusables/secret-scanning/beta.md b/translations/zh-CN/data/reusables/secret-scanning/beta.md index 4676aecb28..89e515f50f 100644 --- a/translations/zh-CN/data/reusables/secret-scanning/beta.md +++ b/translations/zh-CN/data/reusables/secret-scanning/beta.md @@ -1,4 +1,4 @@ -{% ifversion ghae-issue-5752 %} +{% ifversion ghae %} 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 2d0294ba20..c1875346d3 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 @@ -13,9 +13,9 @@ Adobe | Adobe JSON Web Token | adobe_jwt{% endif %} Alibaba Cloud | Alibaba Clou Amazon | Amazon OAuth 客户端 ID | amazon_oauth_client_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Amazon | Amazon OAuth 客户端机密 | amazon_oauth_client_secret{% endif %} Amazon Web Services (AWS) | Amazon AWS 访问密钥 ID | aws_access_key_id Amazon Web Services (AWS) | Amazon AWS 机密访问密钥 | aws_secret_access_key -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Amazon Web Services (AWS) | Amazon AWS Session Token | aws_session_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID | aws_temporary_access_key_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Asana | Asana 个人访问令牌 | asana_personal_access_token{% endif %} Atlassian | Atlassian API 令牌 | atlassian_api_token Atlassian | Atlassian JSON Web 令牌 | atlassian_jwt @@ -27,7 +27,7 @@ Azure | Azure Active Directory 应用程序密钥 | azure_active_directory_appli Azure | Azure Cache for Redis 访问密钥 | azure_cache_for_redis_access_key{% endif %} Azure | Azure DevOps 个人访问令牌 | azure_devops_personal_access_token Azure | Azure SAS 令牌 | azure_sas_token Azure | Azure 服务管理凭证 | azure_management_certificate {%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %} Azure | Azure SQL 连接字符串 | azure_sql_connection_string{% endif %} Azure | Azure 存储帐户密钥 | azure_storage_account_key -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Beamer | Beamer API Key | beamer_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key{% endif %} @@ -35,7 +35,7 @@ Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_k Checkout.com | Checkout.com 测试密钥 | checkout_test_secret_key{% endif %} Clojars | Clojars 部署令牌 | clojars_deploy_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Contentful | Contentful 个人访问令牌 | contentful_personal_access_token{% endif %} Databricks | Databricks 访问令牌 | databricks_access_token {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} DigitalOcean | DigitalOcean 个人访问令牌 | digitalocean_personal_access_token DigitalOcean | DigitalOcean OAuth 令牌 | digitalocean_oauth_token DigitalOcean | DigitalOcean 更新令牌 | digitalocean_refresh_token DigitalOcean | DigitalOcean 系统令牌 | digitalocean_system_token{% endif %} Discord | Discord Bot 令牌 | discord_bot_token Doppler | Doppler 个人令牌 | doppler_personal_token Doppler | Doppler 服务令牌 | doppler_service_token Doppler | Doppler CLI 令牌 | doppler_cli_token Doppler | Doppler SCIM 令牌 | doppler_scim_token @@ -55,7 +55,7 @@ Fastly | Fastly API 令牌 | fastly_api_token{% endif %} Finicity | Finicity App Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Flutterwave | Flutterwave 测试 API 密钥 | flutterwave_test_api_secret_key{% endif %} Frame.io | Frame.io JSON Web 令牌 | frameio_jwt Frame.io| Frame.io Developer 令牌 | frameio_developer_token -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} FullStory | FullStory API Key | fullstory_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} GitHub | GitHub Personal Access Token | github_personal_access_token{% endif %} @@ -67,13 +67,13 @@ GitHub | GitHub Refresh Token | github_refresh_token{% endif %} GitHub | GitHub App 安装访问令牌 | github_app_installation_access_token{% endif %} GitHub | GitHub SSH 私钥 | github_ssh_private_key {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} GitLab | GitLab 访问令牌 | gitlab_access_token{% endif %} GoCardless | GoCardless Live 访问令牌 | gocardless_live_access_token GoCardless | GoCardless Sandbox 访问令牌 | gocardless_sandbox_access_token -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Firebase Cloud Messaging Server 密钥 | firebase_cloud_messaging_server_key{% endif %} Google | Google API 密钥 | google_api_key Google | Google Cloud 私钥 ID | google_cloud_private_key_id -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage Access Key Secret | google_cloud_storage_access_key_secret{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Google | Google Cloud Storage User Access Key ID | google_cloud_storage_user_access_key_id{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Google | Google OAuth 访问令牌 | google_oauth_access_token{% endif %} @@ -93,9 +93,9 @@ Ionic | Ionic Personal Access Token | ionic_personal_access_token{% endif %} Ionic | Ionic Refresh Token | ionic_refresh_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6944 %} JD Cloud | JD Cloud 访问密钥 | jd_cloud_access_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Linear | Linear API Key | linear_api_key{% endif %} @@ -115,13 +115,13 @@ Meta | Facebook 访问令牌 | facebook_access_token{% endif %} Midtrans | Midtrans Production Server 密钥 | midtrans_production_server_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Midtrans | Midtrans Sandbox Server 密钥 | midtrans_sandbox_server_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} New Relic | New Relic License Key | new_relic_license_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5845 %} Notion | Notion 集成令牌 | notion_integration_token{% endif %} @@ -135,15 +135,15 @@ Onfido | Onfido Live API Token | onfido_live_api_token{% endif %} Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} OpenAI | OpenAI API 密钥 | openai_api_key{% endif %} Palantir | Palantir JSON Web 令牌 | palantir_jwt -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Plivo | Plivo Auth ID | plivo_auth_id{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Plivo | Plivo 验证令牌 | plivo_auth_token{% endif %} Postman | Postman API 密钥 | postman_api_key Proctorio | Proctorio 消费者密钥 | proctorio_consumer_key Proctorio | Proctorio 链接密钥 | proctorio_linkage_key Proctorio | Proctorio 注册密钥 | proctorio_registration_key Proctorio | Proctorio 密钥 | proctorio_secret_key Pulumi | Pulumi 访问令牌 | pulumi_access_token {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} PyPI | PyPI API Token | pypi_api_token{% endif %} @@ -153,9 +153,9 @@ RubyGems | RubyGems API 密钥 | rubygems_api_key{% endif %} Samsara | Samsara A Segment | Segment 公共 API 令牌 | 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 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %} -{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-5844 %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %} {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Shippo | Shippo Live API Token | shippo_live_api_token{% endif %} diff --git a/translations/zh-CN/data/reusables/security-center/permissions.md b/translations/zh-CN/data/reusables/security-center/permissions.md new file mode 100644 index 0000000000..99dfdbb565 --- /dev/null +++ b/translations/zh-CN/data/reusables/security-center/permissions.md @@ -0,0 +1 @@ +Organization owners and security managers can access the security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %} and view their organization's repositories via the enterprise-level security overview. Enterprise owners can use the enterprise-level security overview to view all repositories in their enterprise's organizations{% endif %}. 团队成员可以看到团队具有管理权限的仓库的安全概述。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/security/compliance-report-list.md b/translations/zh-CN/data/reusables/security/compliance-report-list.md index 731afc0ca0..cb121885f2 100644 --- a/translations/zh-CN/data/reusables/security/compliance-report-list.md +++ b/translations/zh-CN/data/reusables/security/compliance-report-list.md @@ -1,4 +1,5 @@ - SOC 1, Type 2 - SOC 2, Type 2 - Cloud Security Alliance CAIQ self-assessment (CSA CAIQ) +- ISO/IEC 27001:2013 certification - {% data variables.product.prodname_dotcom_the_website %} Services Continuity and Incident Management Plan diff --git a/translations/zh-CN/data/reusables/ssh/key-type-support.md b/translations/zh-CN/data/reusables/ssh/key-type-support.md index bbaa91bb4d..47ea1037cb 100644 --- a/translations/zh-CN/data/reusables/ssh/key-type-support.md +++ b/translations/zh-CN/data/reusables/ssh/key-type-support.md @@ -1,3 +1,4 @@ +{% ifversion fpt or ghec %} {% note %} **注意：** {% data variables.product.company_short %} 在 2022 年 3 月 15 日通过删除较旧的不安全密钥类型提高了安全性。 @@ -7,3 +8,4 @@ 在 2021 年 11 月 2 日之前 `valid_after` 的 RSA 密钥 (`ssh-rsa`) 可以继续使用任何签名算法。 在该日期之后生成的 RSA 密钥必须使用 SHA-2 签名算法。 某些较旧的客户端可能需要升级才能使用 SHA-2 签名。 {% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/support/submit-a-ticket.md b/translations/zh-CN/data/reusables/support/submit-a-ticket.md index a997773064..e2e68d70ae 100644 --- a/translations/zh-CN/data/reusables/support/submit-a-ticket.md +++ b/translations/zh-CN/data/reusables/support/submit-a-ticket.md @@ -20,14 +20,14 @@ - 选择 **{% data variables.product.support_ticket_priority_low %}** 以提出一般问题和提交有关新功能、购买、培训或状态检查的请求。 {%- endif %} {%- ifversion ghes or ghec %} -1. Optionally, if your account includes {% data variables.contact.premium_support %} and your ticket is {% ifversion ghes %}urgent or high{% elsif ghec %}high{% endif %} priority, you can request a callback in English. Select **Request a callback from GitHub Support**, select the country code dropdown menu to choose your country, and enter your phone number. !["请求回叫"复选框、 "国家/地区代码"下拉菜单和"电话号码"文本框的屏幕截图。](/assets/images/help/support/request-callback.png) +1. （可选）如果您的帐户包含 {% data variables.contact.premium_support %} 并且您的事件单为 {% ifversion ghes %}紧急或高{% elsif ghec %}高{% endif %} 优先级，则可以请求英语回电。 选择 **Request a callback from GitHub Support（请求 GitHub 支持回电）**，选择国家/地区代码下拉菜单以选择您所在的国家/地区，然后输入您的电话号码。 !["请求回叫"复选框、 "国家/地区代码"下拉菜单和"电话号码"文本框的屏幕截图。](/assets/images/help/support/request-callback.png) {%- endif %} -1. 在“Subject（主题）”下，为您遇到的问题输入描述性标题。 ![Screenshot of the "Subject" text box.](/assets/images/help/support/subject-field.png) -1. 在“How can we help（我们如何提供帮助）”下，提供将帮助支持团队对问题进行故障排除的任何其他信息。 You can use markdown to format your message. ![Screenshot of the "How can we help" text area.](/assets/images/help/support/how-can-we-help-field.png) Helpful information may include: +1. 在“Subject（主题）”下，为您遇到的问题输入描述性标题。 !["主题"文本框的屏幕截图。](/assets/images/help/support/subject-field.png) +1. 在“How can we help（我们如何提供帮助）”下，提供将帮助支持团队对问题进行故障排除的任何其他信息。 您可以使用 Markdown 格式化消息。 ![Screenshot of the "How can we help" text area.](/assets/images/help/support/how-can-we-help-field.png) 有用的信息可能包括： - 重现问题的步骤 - 与发现问题相关的任何特殊情况（例如，首次发生或特定活动后发生、发生频率、问题的业务影响以及建议的紧迫程度） - 错误消息的准确表述 {%- ifversion ghes %} -1. Optionally, attach diagnostics files and other files by dragging and dropping, uploading, or pasting from the clipboard. +1. （可选）通过拖放、上传或从剪贴板粘贴来附加诊断文件及其他文件。 {%- endif %} -1. 单击 **Send request（发送请求）**。 ![Screenshot of the "Send request" button.](/assets/images/help/support/send-request-button.png) +1. 单击 **Send request（发送请求）**。 !["发送请求"按钮的屏幕截图。](/assets/images/help/support/send-request-button.png) diff --git a/translations/zh-CN/data/reusables/user-settings/removes-personal-access-tokens.md b/translations/zh-CN/data/reusables/user-settings/removes-personal-access-tokens.md index 6d7ce81c20..512dccc29c 100644 --- a/translations/zh-CN/data/reusables/user-settings/removes-personal-access-tokens.md +++ b/translations/zh-CN/data/reusables/user-settings/removes-personal-access-tokens.md @@ -1 +1 @@ -作为安全防范措施，{% data variables.product.company_short %} 会自动删除一年内未使用的个人访问令牌。{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 or ghec %} 为了提供额外的安全性，我们强烈建议在您的个人访问令牌中添加到期日。{% endif %} +作为安全防范措施，{% data variables.product.company_short %} 会自动删除一年内未使用的个人访问令牌。{% ifversion fpt or ghes > 3.1 or ghae or ghec %} 为了提供额外的安全性，我们强烈建议在您的个人访问令牌中添加到期日。{% endif %} diff --git a/translations/zh-CN/data/reusables/webhooks/check_run_properties.md b/translations/zh-CN/data/reusables/webhooks/check_run_properties.md index c584b4f509..f804c07f7e 100644 --- a/translations/zh-CN/data/reusables/webhooks/check_run_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/check_run_properties.md @@ -1,12 +1,12 @@ -| 键 | 类型 | 描述 | -| --------------------------------------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是以下选项之一：
  • `created` - 创建了新的检查运行。
  • `completed` - 检查运行的“状态”为“已完成”。
  • `rerequested` - 有人请求从拉取请求 UI 重新运行检查。 有关 GitHub UI 的更多信息，请参阅“关于状态检查](/articles/about-status-checks#checks)”。 收到 `rerequested` 操作时，您需要[创建新的检查运行](/rest/reference/checks#create-a-check-run)。 仅当有人请求重新运行检查时，{% data variables.product.prodname_github_app %} 才会收到 `rerequested` 有效负载。
  • `requested_action` - 有人请求执行应用程序提供的操作。 仅当有人请求执行操作时，{% data variables.product.prodname_github_app %} 才会收到 `requested_action` 有效负载。 有关检查运行和请求操作的更多信息，请参阅“[检查运行和请求操作](/rest/reference/checks#check-runs-and-requested-actions)”。
| -| `check_run` | `对象` | [check_run](/rest/reference/checks#get-a-check-run)。 | -| `check_run[status]` | `字符串` | 检查运行的当前状态。 可以是 `queued`、`in_progress` 或 `completed`。 | -| `check_run[conclusion]` | `字符串` | 已完成检查运行的结果。 可以是以下项之一：`success`、`failure`、`neutral`、`cancelled`、`timed_out`、{% ifversion fpt or ghes or ghae or ghec %}`action_required` 或 `stale`{% else %}或 `action_required`{% endif %}。 此值将为 `null`，直到检查运行 `completed`。 | -| `check_run[name]` | `字符串` | 检查运行的名称。 | -| `check_run[check_suite][id]` | `整数` | 此检查运行所属检查套件的 ID。 | -| `check_run[check_suite][pull_requests]` | `数组` | 匹配此检查套件的拉取请求数组。 如果拉取请求具有相同的 `head_branch`，则它们与检查套件匹配。

**注意：**
  • 如果随后推送到 PR 中，则检查套件的“head_sha”可能与拉取请求的“sha”不同。
  • 当检查套件的“head_branch”位于复刻的存储库中时，它将为“null”，而“pull_requests”数组将为空。
| -| `check_run[check_suite][deployment]` | `对象` | 部署到仓库环境。 这仅当检查运行是由引用环境的 {% data variables.product.prodname_actions %} 工作流程作业创建时才会填充。 | -| `requested_action` | `对象` | 用户请求的操作。 | -| `requested_action[identifier]` | `字符串` | 用户请求的操作的集成器引用。 | +| 键 | 类型 | 描述 | +| --------------------------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `字符串` | 执行的操作。 可以是以下选项之一：
  • `created` - 创建了新的检查运行。
  • `completed` - 检查运行的“状态”为“已完成”。
  • `rerequested` - 有人请求从拉取请求 UI 重新运行检查。 有关 GitHub UI 的更多信息，请参阅“关于状态检查](/articles/about-status-checks#checks)”。 收到 `rerequested` 操作时，您需要[创建新的检查运行](/rest/reference/checks#create-a-check-run)。 仅当有人请求重新运行检查时，{% data variables.product.prodname_github_app %} 才会收到 `rerequested` 有效负载。
  • `requested_action` - 有人请求执行应用程序提供的操作。 仅当有人请求执行操作时，{% data variables.product.prodname_github_app %} 才会收到 `requested_action` 有效负载。 有关检查运行和请求操作的更多信息，请参阅“[检查运行和请求操作](/rest/reference/checks#check-runs-and-requested-actions)”。
| +| `check_run` | `对象` | [check_run](/rest/reference/checks#get-a-check-run)。 | +| `check_run[status]` | `字符串` | 检查运行的当前状态。 可以是 `queued`、`in_progress` 或 `completed`。 | +| `check_run[conclusion]` | `字符串` | 已完成检查运行的结果。 可以是 `success`、`failure`、`neutral`、`cancelled`、`timed_out`、`action_required` 或 `stale` 之一。 此值将为 `null`，直到检查运行 `completed`。 | +| `check_run[name]` | `字符串` | 检查运行的名称。 | +| `check_run[check_suite][id]` | `整数` | 此检查运行所属检查套件的 ID。 | +| `check_run[check_suite][pull_requests]` | `数组` | 匹配此检查套件的拉取请求数组。 如果拉取请求具有相同的 `head_branch`，则它们与检查套件匹配。

**注意：**
  • 如果随后推送到 PR 中，则检查套件的“head_sha”可能与拉取请求的“sha”不同。
  • 当检查套件的“head_branch”位于复刻的存储库中时，它将为“null”，而“pull_requests”数组将为空。
| +| `check_run[check_suite][deployment]` | `对象` | 部署到仓库环境。 这仅当检查运行是由引用环境的 {% data variables.product.prodname_actions %} 工作流程作业创建时才会填充。 | +| `requested_action` | `对象` | 用户请求的操作。 | +| `requested_action[identifier]` | `字符串` | 用户请求的操作的集成器引用。 | diff --git a/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md b/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md index 9ba9f165b8..957984c3e9 100644 --- a/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/check_suite_properties.md @@ -1,10 +1,10 @@ -| 键 | 类型 | 描述 | -| ---------------------------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `action` | `字符串` | 执行的操作。 可以是：
  • `completed` - 检查套件中的所有检查运行已完成。
  • `requested` - 新代码被推送到应用程序的仓库时发生。 收到 `requested` 操作事件时，您需要[创建新的检查运行](/rest/reference/checks#create-a-check-run)。
  • `rerequested` - 有人请求从拉取请求 UI 重新运行整个检查套件时发生。 收到 `rerequested` 操作事件时，您需要[创建新的检查运行](/rest/reference/checks#create-a-check-run)。 有关 GitHub UI 的更多信息，请参阅“关于状态检查](/articles/about-status-checks#checks)”。
| -| `check_suite` | `对象` | [check_suite](/rest/reference/checks#suites)。 | -| `check_suite[head_branch]` | `字符串` | 更改所在的头部分支的名称。 | -| `check_suite[head_sha]` | `字符串` | 此检查套件的最新提交的 SHA。 | -| `check_suite[status]` | `字符串` | 检查套件中所有检查运行的摘要状态。 可以是 `requested`、`in_progress` 或 `completed`。 | -| `check_suite[conclusion]` | `字符串` | 检查套件中所有检查运行的摘要结论。 可以是以下项之一：`success`、`failure`、`neutral`、`cancelled`、`timed_out`、{% ifversion fpt or ghes or ghae or ghec %}`action_required` 或 `stale`{% else %}或 `action_required`{% endif %}。 此值将为 `null`，直到检查运行 `completed`。 | -| `check_suite[url]` | `字符串` | 指向检查套件 API 资源的 URL。 | -| `check_suite[pull_requests]` | `数组` | 匹配此检查套件的拉取请求数组。 如果拉取请求具有相同的 `head_branch`，则它们与检查套件匹配。

**注意：**
  • 如果随后推送到 PR 中，则检查套件的“head_sha”可能与拉取请求的“sha”不同。
  • 当检查套件的“head_branch”位于复刻的存储库中时，它将为“null”，而“pull_requests”数组将为空。
| +| 键 | 类型 | 描述 | +| ---------------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------- | +| `action` | `字符串` | 执行的操作。 可以是：
  • `completed` - 检查套件中的所有检查运行已完成。
  • `requested` - 新代码被推送到应用程序的仓库时发生。 收到 `requested` 操作事件时，您需要[创建新的检查运行](/rest/reference/checks#create-a-check-run)。
  • `rerequested` - 有人请求从拉取请求 UI 重新运行整个检查套件时发生。 收到 `rerequested` 操作事件时，您需要[创建新的检查运行](/rest/reference/checks#create-a-check-run)。 有关 GitHub UI 的更多信息，请参阅“关于状态检查](/articles/about-status-checks#checks)”。
| +| `check_suite` | `对象` | [check_suite](/rest/reference/checks#suites)。 | +| `check_suite[head_branch]` | `字符串` | 更改所在的头部分支的名称。 | +| `check_suite[head_sha]` | `字符串` | 此检查套件的最新提交的 SHA。 | +| `check_suite[status]` | `字符串` | 检查套件中所有检查运行的摘要状态。 可以是 `requested`、`in_progress` 或 `completed`。 | +| `check_suite[conclusion]` | `字符串` | 检查套件中所有检查运行的摘要结论。 可以是 `success`、`failure`、`neutral`、`cancelled`、`timed_out`、`action_required` 或 `stale` 之一。 此值将为 `null`，直到检查运行 `completed`。 | +| `check_suite[url]` | `字符串` | 指向检查套件 API 资源的 URL。 | +| `check_suite[pull_requests]` | `数组` | 匹配此检查套件的拉取请求数组。 如果拉取请求具有相同的 `head_branch`，则它们与检查套件匹配。

**注意：**
  • 如果随后推送到 PR 中，则检查套件的“head_sha”可能与拉取请求的“sha”不同。
  • 当检查套件的“head_branch”位于复刻的存储库中时，它将为“null”，而“pull_requests”数组将为空。
| diff --git a/translations/zh-CN/data/reusables/webhooks/installation_properties.md b/translations/zh-CN/data/reusables/webhooks/installation_properties.md index 731d16045a..3b74e29503 100644 --- a/translations/zh-CN/data/reusables/webhooks/installation_properties.md +++ b/translations/zh-CN/data/reusables/webhooks/installation_properties.md @@ -1,4 +1,4 @@ | 键 | 类型 | 描述 | | -------- | ----- | -------------------------------------------- | -| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：
  • `created` - 有人安装 {% data variables.product.prodname_github_app %}。
  • `deleted` - 有人卸载 {% data variables.product.prodname_github_app %}
    • {% ifversion fpt or ghes or ghae or ghec %}
  • `suspend` - 有人挂起 {% data variables.product.prodname_github_app %} 安装。
  • `unsuspend` - 有人取消挂起 {% data variables.product.prodname_github_app %} 安装。
    • {% endif %}
  • `new_permissions_accepted` - 有人接受 {% data variables.product.prodname_github_app %} 安装的新权限。 当 {% data variables.product.prodname_github_app %} 所有者请求新权限时，安装 {% data variables.product.prodname_github_app %} 的人必须接受新权限请求。
| +| `action` | `字符串` | 执行的操作内容. 可以是以下选项之一：
  • `created` - 有人安装 {% data variables.product.prodname_github_app %}。
  • `deleted` - 有人卸载 {% data variables.product.prodname_github_app %}
  • `suspend` - 有人挂起 {% data variables.product.prodname_github_app %} 安装。
  • `unsuspend` - 有人取消挂起 {% data variables.product.prodname_github_app %} 安装。
  • `new_permissions_accepted` - 有人接受 {% data variables.product.prodname_github_app %} 安装的新权限。 当 {% data variables.product.prodname_github_app %} 所有者请求新权限时，安装 {% data variables.product.prodname_github_app %} 的人必须接受新权限请求。
| | `仓库` | `数组` | 安装设施可访问的仓库对象数组。 | diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml index 8837c9488a..1eac9e9654 100644 --- a/translations/zh-CN/data/variables/product.yml +++ b/translations/zh-CN/data/variables/product.yml @@ -140,10 +140,14 @@ prodname_advisory_database: 'GitHub Advisory Database' prodname_codeql_workflow: 'CodeQL 分析工作流程' #Visual Studio prodname_vs: 'Visual Studio' +prodname_vscode_shortname: 'VS Code' prodname_vscode: 'Visual Studio Code' prodname_vss_ghe: '包含 GitHub Enterprise 的 Visual Studio 订阅' prodname_vss_admin_portal_with_url: '[Visual Studio 订阅的管理员门户](https://visualstudio.microsoft.com/subscriptions-administration/)' -prodname_vscode_command_palette: 'VS 代码命令面板' +prodname_vscode_command_palette_shortname: 'VS 代码命令面板' +prodname_vscode_command_palette: 'Visual Studio Code Command Palette' +prodname_vscode_marketplace: 'Visual Studio Code Marketplace' +prodname_vs_marketplace_shortname: 'VS Code Marketplace' #GitHub Dependabot prodname_dependabot: 'Dependabot' prodname_dependabot_alerts: 'Dependabot 警报'
- Especifique o escopo e o nome de um ou mais pacotes de consulta CodeQL para fazer o download usando uma lista separada por vírgulas. Opcionalmente, inclua a versão para fazer o download e descompactar. Por padrão, a versão mais recente deste pacote foi baixada. Optionally, include a path to a query, directory, or query suite to run. If no path is included, then run the default queries of this pack. + Especifique o escopo e o nome de um ou mais pacotes de consulta CodeQL para fazer o download usando uma lista separada por vírgulas. Opcionalmente, inclua a versão para fazer o download e descompactar. Por padrão, a versão mais recente deste pacote foi baixada. Opcionalmente, inclua um caminho para uma consulta, diretório ou conjunto de consultas para ser executado. Se nenhum caminho for incluído, execute as consultas padrão deste pacote.
setup-node
pip, pipenvpip, pipenv, poetry setup-python